chezbrgrs
asked on
Errors in Exchange Best Practices Analyzer after Server Retired
Hello Experts -
We recently added an Exchange 2010 server to our domain to coexist temporarily with an Exchange 2003 server. I was able to successfully move all mailboxes to the 2010 server from the 2003 server and was in the process of decommissioning the 2003 server when it had a hardware failure (RAID degraded and corrupted).
I had already moved the Offline Address Book and everything seems to be working perfect but when running the Exchange Best Practices Analyzer, several errors are reported.
1. Unrecognized Exchange signature: From what I've found online, this is a bug in the ExBPA because I'm running DomainPrep version 12639 which is the correct version for Exchange 2010.
2. Routing master has been deleted
3. Cannot connect to port 25 of the routing group master
4. Cannot connect to port 691 of the routing group master
I need help with #2, #3 and #4. They are all referencing the First Routing Group on the old server. We're not planning on using Exchange 2003 again and I understand Exchange 2010 doesn't use routing groups in this way but the errors are troubling. How can I remove references to this routing group from Active Directory or point them to the new Exchange 2010 server?
Any advice is appreciated. Thanks for your help.
We recently added an Exchange 2010 server to our domain to coexist temporarily with an Exchange 2003 server. I was able to successfully move all mailboxes to the 2010 server from the 2003 server and was in the process of decommissioning the 2003 server when it had a hardware failure (RAID degraded and corrupted).
I had already moved the Offline Address Book and everything seems to be working perfect but when running the Exchange Best Practices Analyzer, several errors are reported.
1. Unrecognized Exchange signature: From what I've found online, this is a bug in the ExBPA because I'm running DomainPrep version 12639 which is the correct version for Exchange 2010.
2. Routing master has been deleted
3. Cannot connect to port 25 of the routing group master
4. Cannot connect to port 691 of the routing group master
I need help with #2, #3 and #4. They are all referencing the First Routing Group on the old server. We're not planning on using Exchange 2003 again and I understand Exchange 2010 doesn't use routing groups in this way but the errors are troubling. How can I remove references to this routing group from Active Directory or point them to the new Exchange 2010 server?
Any advice is appreciated. Thanks for your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also refer this:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/4374201e-d5cd-45f4-91fd-c5cd504cce85
Note: Do take the backup of the System State before doing any changes.
http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/4374201e-d5cd-45f4-91fd-c5cd504cce85
Note: Do take the backup of the System State before doing any changes.
It seems like traces of Exchange 2003 are still there on your domain. I ran into a similar issue and here is what I did to resolve the issue. https://www.experts-exchange.com/questions/24701018/Remove-traces-of-old-Exchange-2003-from-SBS-2008-after-migration.html?sfQueryTermInfo=1+2003+exchang+remov+trace
Best of luck.
Best of luck.
ASKER
Thanks everyone for your help.
Just to be clear, I was in the process of removing Exchange 2003 properly when a hardware failure occurred. The only thing that seems to have not been removed properly were the routing groups - offline address list, free/busy, etc was already migrated.
Just to be clear, I was in the process of removing Exchange 2003 properly when a hardware failure occurred. The only thing that seems to have not been removed properly were the routing groups - offline address list, free/busy, etc was already migrated.
Have you simply shutdown the exchange 2003 server to decommission it? If yes, then it is not the proper method.
Refer this article for the same:
http://technet.microsoft.com/en-us/library/bb288905%28EXCHG.80%29.aspx
After that all the issues will be fixed.
Hope this helps,
Shree