I just finished an SBS2003-to-Windows2012/Exchange2010 migration. I went through all the steps to migrate Exchange, await/verify replication, etc, seize the FSMO roles to the W2012 server, and finally removed the SBS2003 server from the domain and shut it down. Everything is working fine with just Exchange 2010 with one small exception. One thing somehow got leftover: the Exchange administrative group containing only the old server. The only evidence is the event log here:
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 [Old Server FQDN] in Routing Group blah, blah, blah.
Everything I have looked up on the subject explains how to remove problematic/obsolete routing group connectors; however, Get-RoutingGroupConnector returns nothing, and ADSIEdit reveals the problem: there a routing group containing just the old server left over from the migration.
Configuration -> Services -> Microsoft Exchange -> [Exchange domain] -> Administrative Groups. The next level is where I see the problem. There are two administrative groups:
- The new administrative group containing only the new Exchange 2010 server under CN=Servers
- The original "first administrative group"containing only the old Exchange 2003 server under CN=Servers
I do see one disturbing thing that might indicate I missed a step in migration: the new administrative group is missing CN=Hierarchies that is present in the old/defunct administrative group. The new one has these:
- Advanced Security
- Arrays
- Database Availability Groups
- Databases
- Routing Groups
- Servers
Each of those contains references only to objects that exist and are functional in Exchange 2010. The old administrative group contains these:
- Advanced Security (looks the same as the new one above)
- Folder Hierarchies (one entry for Public Folders, Clas msExchPFTree)
- Routing Groups (with nothing under first routing group -> Connections)
- Servers (and only the old server listed)
So my questions are two:
- Do I need to (and can I) move the Folder Hierarchies to the other administrative group? Or do I need to create one manually there?
- If so, and when done, can I simply delete the obsolete/defunct "first administrative group" via ADSIEdit?