Exchange Migration Failure

I have a client that we are migrating from a 2003 domain/Exchange 2003 to 2008 R2 / Exchange 2010. AD moved over, and all FSMO roles are pointing to new 2008 R2 DC. Exchange is showing the old 2003 DC as the DC it's using when I look under System Settings in EMC. I turned off the old 2003 dc and now Exchange will not come online. Keeps giving me an error when EMC is starting stating that the WinRM client received an HTTP server error status (500), but the remote service did not include any other info. When I look at services, the Edge Sync service is not started and will not start. It gives Error: 1053: The service did not respond to the start or control request in a timely fashion. These are all virtual servers, so I've even attempted to create a new Exchange server, but with no luck. Any assistance would be greatly appreciated.
LamboOKAsked:
Who is Participating?
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.

Leon FesterSenior Solutions ArchitectCommented:
Sounds like your Exchange server is pointing to the OLD DC through a static entry.
Remember in Exchange 2003 you could specify a preferred Domain Controller.

While you can set a static domain controller in Exchange 2010, it is recommended that you use autodiscovery options since the Exchange server topology could mean that the Exchange Services are running from different sites.

Firstly, check if there is a preferred DC configured using the Powershell command:
 Get-ExchangeServer -Status
If there is a preferred DC, then follow the instructions to remove the static domain controller entries on Exchange.
http://support.microsoft.com/kb/2619379

You would need to re-start the microsoft exchange active directory topology service(MSExchangeADTopology) or wait for it to re-sync in order to discover the Domain Controller that is best suited to servicing that Exchange Server.
0

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
hecgomrecCommented:
If you still have the old 2003 around, turn it on.

In a normal migration you should introduce your 2008 to the AD and then install your exchange 2010, migrate your exchange first, make sure your 2010 is in charge of everything, remove exchange 2003 then transfer all DHCP, DNS, etc. to the 2008, finally demote the 2003.

If you try to do it different you will have to deal a lot with the ADSI tool.
0
LamboOKAuthor Commented:
The old Exchange 2003 lost two disks in one day last week. So, it's not available anymore. I'm looking into the link submitted by Leon. I'll post my findings. I appreciate your input.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

LamboOKAuthor Commented:
Ok, when I run the -GetExchangeServer -Status, the results are as follows:

Warning: An error occurred while accessing the registery on the server "old_ExchangeServer_name.ourdomain.com". The error that occurred is: "The network path was not found.

Warning: An error occurred while accessing the Active Directory topology service on the specified server "new_ExchangeServer_name.ourdomain.com". The error message: The Microsoft Exchange Active Directory Topology service on server new_ExchangeServer_name.ourdomain.com did not return any suitable domain controllers.

So, it's still trying to find the old Exchange 2003 server, but that server is dead. Any thoughts on what my next step should be?
0
hecgomrecCommented:
Do you have any other DC, GC on the organization?

Open your 2010 and locate Organization Configuration in the EMC, open properties and type you DC there to see if that helps.
0
LamboOKAuthor Commented:
There are two old 2003 DC's that their DNS was turned off and SimpleDNS was deployed, (this was done by the admin before me). I was able to migrate the domain over to a 2008R2 server and all FSMO roles are pointed to the 2008 R2 DC. The two old 2003 DC's are turned off at the moment. I am unable to open EMC on the 2010 server, it keeps erroring out.
0
torns tenkristenIT AdministratorCommented:
In addition to above suggestions, I would recommend you to take a tour of Exchange server deployment assistant also that is available from Microsoft and can be a good start-up to achieve the migration goal more accurately as it provides step-wise instructions for the same. Please take a look at : http://technet.microsoft.com/en-us/office/dn756393.aspx
0
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
Microsoft Server Apps

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.