Removing a Phantom Exchange 2003 Server AND IP6 Issues
I have two anomolies that I need help with.
1. I recently migrated users from a dying 2003 Exchange server. All users and public folders and connectors were successfully moved to the 2010 server. While uninstalling the 2003 server, I ran into problems and was unable to do the standard uninstall. I ended up doing the "brute force" uninstall using this KB - http://support.microsoft.com/kb/833396
Now the 2010 server still "sees" the 2003 server. I was able to remove the connectors to the 2010 server in 2003 prior to uninstall.
How do I remove the reference to the 2003 server from 2010? Should I use ADSI Edit? If so, what is the best process.
2. IP6. Is it required? This is a single server DC/GC/Exchange Server. When IP6 is enabled NSLOOKUP fails and the transport service shuts down. In the event log, I'm receiving this error:
"Process MAD.EXE (PID=2596). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers."
And:
"Process STORE.EXE (PID=8496). All Domain Controller Servers in use are not responding: "
As I researched these errors, it seems the solution is to turn IP6 back on. I spoke yesterday to a good friend of mine who is an Exchange engineer at MSFT. He told me that IP6 is not required for a single server.
Any help on these issues are greatly appreciated.
Thanks!
Ted
1. I recently migrated users from a dying 2003 Exchange server. All users and public folders and connectors were successfully moved to the 2010 server. While uninstalling the 2003 server, I ran into problems and was unable to do the standard uninstall. I ended up doing the "brute force" uninstall using this KB - http://support.microsoft.com/kb/833396
Now the 2010 server still "sees" the 2003 server. I was able to remove the connectors to the 2010 server in 2003 prior to uninstall.
How do I remove the reference to the 2003 server from 2010? Should I use ADSI Edit? If so, what is the best process.
2. IP6. Is it required? This is a single server DC/GC/Exchange Server. When IP6 is enabled NSLOOKUP fails and the transport service shuts down. In the event log, I'm receiving this error:
"Process MAD.EXE (PID=2596). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers."
And:
"Process STORE.EXE (PID=8496). All Domain Controller Servers in use are not responding: "
As I researched these errors, it seems the solution is to turn IP6 back on. I spoke yesterday to a good friend of mine who is an Exchange engineer at MSFT. He told me that IP6 is not required for a single server.
Any help on these issues are greatly appreciated.
Thanks!
Ted
ASKER
That article only talks about using ADSI edit to remove RUS. There are a lot of other references to the olde server in ADSI edit. I don't want to start removing things from there that I'm not sure about. I'll try BPA. IP6 was turned off yesterday.
you just want to remove the server under administrative group in the same area
ASKER
Should I also delete the 2003 "First Administrative Group" from ADSI? After I deleted the server and ran BPA, I'm still getting errors in BPA. The error is:
The site-wide public folder database for administrative group 'First Administrative Group' has been deleted. Current public folder store: 'CN=Public Folder Store (LAWSERV2)\0ADEL:5d9dc726-
lawserv2 is the old server.
There is no "Find" in ADSI edit, but should I remove every reference?
When I removed the connectors in Exchange 2003 when it was operational, I made sure the connectors were severed on both ends.
Is there a shell command to completely eradicate any connections to the old server?
The site-wide public folder database for administrative group 'First Administrative Group' has been deleted. Current public folder store: 'CN=Public Folder Store (LAWSERV2)\0ADEL:5d9dc726-
lawserv2 is the old server.
There is no "Find" in ADSI edit, but should I remove every reference?
When I removed the connectors in Exchange 2003 when it was operational, I made sure the connectors were severed on both ends.
Is there a shell command to completely eradicate any connections to the old server?
no do not delete the First Administrative Group" at all
I would try to follow as much of the removing the last legacy server as you can. Until where the uninstall is.
If you have the 2003 system manager tools somewhere you can delete the server from there.
Here is a reference for fixing the site folder error.
https://www.experts-exchange.com/questions/21474290/Best-Practice-Analyzer-Tool-Critical-Issue-the-site-wide-public-folder-database-for-administrative-group-has-been-deleted.html
I would try to follow as much of the removing the last legacy server as you can. Until where the uninstall is.
If you have the 2003 system manager tools somewhere you can delete the server from there.
Here is a reference for fixing the site folder error.
https://www.experts-exchange.com/questions/21474290/Best-Practice-Analyzer-Tool-Critical-Issue-the-site-wide-public-folder-database-for-administrative-group-has-been-deleted.html
ASKER
The old Exchange server is offline and unavailable. I don't believe I can run 2003 System Manager on the 64 bit server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This article explains shows where the patch of the 2003 server will be in ADSI edit. http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
2 IPV6 is supported but not required I would disable it in your enviorment.
After all this run the BPA sometimes when you brute force you may need to do some other cleanups that the BPA will flush out