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+ FREE BUSY

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+ FREE BUSY Public Folder?
PlanarITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amit KumarCommented:
I think you should log a case in Microsoft and take help because it is very critical.

As you mentioned Exchange 2003 servers have not been uninstalled properly so they may have any stale entry in ADSIEdit. My recommendation is to work with MS on a ticket which at least may not lead you in any critical infrastructure issue.
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
You should not need to delete the entrie folder and it is recommended by Microsoft that you leave it if possible. However it can be deleted it needed. Also as long as you have your public folders replicated to your new Exchange environment then you can proceed. See the link below for ful steps.

https://support.microsoft.com/en-ca/kb/822931 

Will.
0
Scott CSenior Systems EnginerCommented:
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.
2
PlanarITAuthor Commented:
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.
0
PlanarITAuthor Commented:
Good common-sense advice.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.