Mike Howard
asked on
Manually removing First Administrative Group from Exchange 2007 after migrating from 2003
Background:
We have a native Exchange 2007 deployment. We are currently undertaking a migration to 2013 and we're doing some housecleaning in anticipation of that.
Question:
When the environment was moved from 2003 to 2007 the last 2003 server was apparently not gracefully removed, and I think it has left some artifacts, specifically the First Administrative Group. I see this in two places:
1. In ADSIEdit under Services --> Microsoft Exchange --> %company% --> Administrative Groups
2. In Public Folder heirarchy under \NON_IPM_SUBTREE\SCHEDULE+
No servers are listed in that group in ADSIEdit, and all of the old Exchange 2003 servers have been long removed. I recall that the last 2003 server in the organization had issues during uninstall, and it eventually crashed and could not be revived. At that point the only thing it was being used for was as a connector for Lotus Notes, which was being phased out anyway.
At any rate, is there any downside to manually deleting the First Administrative Group from the Configuration container and from the \NON_IPM_SUBTREE\SCHEDULE+
We have a native Exchange 2007 deployment. We are currently undertaking a migration to 2013 and we're doing some housecleaning in anticipation of that.
Question:
When the environment was moved from 2003 to 2007 the last 2003 server was apparently not gracefully removed, and I think it has left some artifacts, specifically the First Administrative Group. I see this in two places:
1. In ADSIEdit under Services --> Microsoft Exchange --> %company% --> Administrative Groups
2. In Public Folder heirarchy under \NON_IPM_SUBTREE\SCHEDULE+
No servers are listed in that group in ADSIEdit, and all of the old Exchange 2003 servers have been long removed. I recall that the last 2003 server in the organization had issues during uninstall, and it eventually crashed and could not be revived. At that point the only thing it was being used for was as a connector for Lotus Notes, which was being phased out anyway.
At any rate, is there any downside to manually deleting the First Administrative Group from the Configuration container and from the \NON_IPM_SUBTREE\SCHEDULE+
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Another thing you can do to make sure the stale data won't stop the install is start a test install of Exchange 2013 but don't actually do it.
If Exchange 2013 even thinks there is a 2003 server in the environment it will stop at the beginning.
If Exchange 2013 even thinks there is a 2003 server in the environment it will stop at the beginning.
ASKER
We don't make use of Public Folders organizationally. So any Public Folders will be used exclusively by the system.
The KB isn't much help as the 2003 Exchange Server(s) are not accessible.
I have run forestprep and domainprep for Exchange 2013, and it only griped about the environment being 2007 SP1, not SP3. That's an expected error, though.
Another "Hmmmmm..." item is this: The Exchange BPA reports that First Administrative Group (not First Administrative Group (FYDIBOHF23SPDLT)) is the default administrative group, so I'm guessing that I should probably leave it alone for now.
We've gone through and sanitized AD as much as possible--deleting any reference to the older Exchange boxes--and we've had a couple of gold partners come through and do health checks for us and they didn't raise any issues. Event logs are pretty clean--no errors or warnings, just informational stuff.
Opening a case with MS looks like the best way forward at this point. We're mainly looking to avoid any unexpected nastiness once we are doing the 2013 deployment.
The KB isn't much help as the 2003 Exchange Server(s) are not accessible.
I have run forestprep and domainprep for Exchange 2013, and it only griped about the environment being 2007 SP1, not SP3. That's an expected error, though.
Another "Hmmmmm..." item is this: The Exchange BPA reports that First Administrative Group (not First Administrative Group (FYDIBOHF23SPDLT)) is the default administrative group, so I'm guessing that I should probably leave it alone for now.
We've gone through and sanitized AD as much as possible--deleting any reference to the older Exchange boxes--and we've had a couple of gold partners come through and do health checks for us and they didn't raise any issues. Event logs are pretty clean--no errors or warnings, just informational stuff.
Opening a case with MS looks like the best way forward at this point. We're mainly looking to avoid any unexpected nastiness once we are doing the 2013 deployment.
ASKER
Good common-sense advice.
https://support.microsoft.com/en-ca/kb/822931
Will.