Link to home
Start Free TrialLog in
Avatar of LamboOK
LamboOKFlag for United States of America

asked on

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.
ASKER CERTIFIED SOLUTION
Avatar of Leon Fester
Leon Fester
Flag of South Africa image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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.
Avatar of LamboOK

ASKER

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.
Avatar of LamboOK

ASKER

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?
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.
Avatar of LamboOK

ASKER

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.
Avatar of torns tenkristen
torns tenkristen

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