We used to have two routing groups and three Exchange 2003 servers. We have consolidated and are now down to just one Exchange 2003 server. We have moved all the mailboxes from servers and decommissioned them using: http://support.microsoft.com/kb/822931 and everything is peachy. We want to remove one of the administrative group and have removed everything from the administrative group and now we want to delete it. But looking at the public folders they are somehow located in that group. Looking at the properties of the Public Store I can see it listed as “Associated public folder tree: Old-Site-To-Be-Removed/Public Folders. And looking in ESM I can see that the public folder tree is in the administrative group that we want to remove. I belive that if I delete the Old-Site-To-Be-Removed administrative group I will toss all my public folders, or make them orphaned or something like that. So what to do?

In this case, the association appears to be with a "munged" public folder tree.For example, in the public storage group properties, the associated public folder tree appears as follows: First Administrative Group0 CNF:fb604902-1287-443e-9595-62a39efe3cf3/PublicFolders Also, in ESM, there is a First Administrative Group with the same "munged"name. Customer indicated there was an error during the installation of Exchange. It appears that when they reinstalled, it may have introduced some conflict in the AD as indicated by the "CNF" in the folder names. - Remove Exchange 2000 to see if it will clear up the munged First AG - If the remove doesn't take care of the munged AG, then remove the corrupt AGentry using ADSI edit - Reinstall ExchangeGood Luck!Best Regards!