Link to home
Start Free TrialLog in
Avatar of Racer1950
Racer1950Flag for United States of America

asked on

Can't connect to exchange after migrating sbs 2003 to sbs 2010 when stopping exchange services on source server

After migrating public folders mailboxes and oab from sbs 2003 exchange server 2003 to sbs 2011 exchange server 2010, when I stop exchange services on the source server, the outlook clients and web clients cannot connect to exchange.
Avatar of rick81
rick81

Avatar of Racer1950

ASKER

Yes, I followed the Microsoft document.
send some emails out and check the email headers when received.
sounds like sbs2011 is using the exchange roles on sbs2003.  checking the headers will confirm.
headers show the correct server
all the mailboxes migrated successfully?  they are all attached to the correct dbase and correct server?  check all the exchange services are running on sbs2011 ok.

any errors in event viewer.

i would stop the sbs2003 box and then look at event logs on sbs2011.  if its using sbs2003 for mail roles it should start throwing some errors and pin pointing what is going on.
I stopped each exchange 2003 service 1 at a time, each time sending and receiveing. Mail flow stayed on and outlook client stayed connected. Everything looks ok except in the 2010 management console, it still shows 2 exchange servers, 1 2003 and 1 2010 in Organizational Health after I ran a collect data.

I can't take a chance and power off the 2003 box at this time.
When I select manage servers from the management console organization health it only goes to the new box entry in server configuration.
No event errors
is there a decommision process for the sbs2003.  ie uninstalling exchange2003, removing from the domain, deleting the 2003 exchange from 2010.
ASKER CERTIFIED SOLUTION
Avatar of rick81
rick81

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
I haven't uninstalled exchange server 2003. I will accept your solution.
Thanks
there must be some steps missing. i've found with migrations (i try to avoid them) missing one step can fail the whole migration.
I was spoiled by the last one I did. It went extremely well and quick. This one was with sick source server.
Thanks