SBS2003 Migration to Server 2012/Exchange 2010

Like so many here, we are migrating all our customers to Server 2012 and newer versions of Exchange.  For this particular customer we built the new server using 2012, installed AD and merged AD with the SBS domain.  All went relatively smoothly but Exchange 2013 wouldn't install in the same environment as Exchange 2003, so we installed Exchange 2010, migrated the users, mailboxes, etc.  It has been operational for about 30 days, we left the old server running until a few 32 bit apps could be converted.  Last week we attempted to move the FSMO to the new server to de-commission the old.  Everything went well until Exchange dropped b/c it couldn't find the old GC.  I moved the FSMO back to the old server, restarted the new server and everything came back up - I looked in Exchange and it is pointing to the old server for GC.  We need to get rid of the dependency for the old server and install Exchange 2013 soon - did we miss a step somewhere and how can we fix it
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jian An LimSolutions ArchitectCommented:
Exchange 2010 using 1 GC?

can you confirm your new AD on 2012 have GC?

one of the easier way (but not 100% accurate) to find out is to browse to \\newserver\netlogon \\newserver\sysvol

Again, FSMO role has nothing to do with GC if all your DC servers are GC.
Sounds like your new DC may not be working properly. @limjianan is correct that moving the FSMO roles should matter, although I would note that the SBS is meant to hold all 5 FSMO roles and will complain/partially shut down if they are moved.
(check event viewer on the SBS for any licensing events to see if this has occurred)

I recommend checking your new DC is working OK before worrying. Check DFS/FRS & Directory services section of event viewer and basic checks with dcdiag would be a good start.
infosysnolaAuthor Commented:
The GC in 2010 Exchange points to the old server.  There is a GC on the old and new server.  Can I just point Exchange to GC on the new server
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Jian An LimSolutions ArchitectCommented:
in exchange powershell
$AdminSessionADSettings OR

tell me what do you see, do you see one server only? (look for any prefered or default)
infosysnolaAuthor Commented:
Under PreferredDomainControllers it shows <>
Under RecipientViewRoot is shows lawfirm.local
Jian An LimSolutions ArchitectCommented:
so when you pull the old server out, what is the error message you getting ?
like application event logs and etc
infosysnolaAuthor Commented:
None of the Exchange services start and the event log says it can't find the GC.  I went back into the schema and reactivated the old GC and all the services started again.  Then I went in the EMC and found that the Exchange 2010 has the old server listed as the GC.  Can I just change this to the new server.
No. its not that simple as exchange discovers GC automatically. If one isn't working it should use another by design. you shouldn't have to manually set one.
You need to look at the new DC urgently and fid out whats going on as it looks like you may have issues.
Jian An LimSolutions ArchitectCommented:
EMC and found that the Exchange 2010 has the old server listed as the GC <-- can you give me a screenshot so i can understand where it goes wrong?
infosysnolaAuthor Commented:
the sysvol folders wasn't setup as a network share on the new server.  The migration didn't work properly.  Once I fixed that and moved the FSMO over the new server restarted and all the exchange services came up.

I couldn't install Exchange 2013 on the server in the presence of Exchange 2003, so I installed a trial of Exchange 2010.  Now that the old server is gone I need to install Exchange 2013 on the new server.  Do I have to uninstall 2010 first.  Thanks for everyone's help on the first issue.
Great news. glad you've sorted the root issue. As suspected, the problem was with your DC, not exchange.

Probably best to create a new question for the exchange 2013 migration, but as a quick response:
Is exchange in use? If yes you cannot simply uninstall and reinstall the new one. you need to migrate from the existing exch 20102 to a new exch 2013 installation on a different server.
Did you 'properly' uninstall Exchange 2003 or just turn off the old SBS box? it must be properly removed from your AD before proceeding with exch 2013 install.
Any update or is all OK now?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.