We are in the process of migrating from E2K7 to E2K10 and had an issue replicating Public Folders to the new Public Folder Store on the new E2K10 server. After looking around for a resolution to the error the fixwas to delete the empty server container from an old Exchange 2003 First Administrative Group. So using adsiedit I found the suspect server container, made a back up , then deleted the empty container. Problem fixed. Here is a pic after deleted the server container from My question is this, why is an reference to exchange 2003 still there? What information is it still providing to the overall exchange configuration? Can it be deleted without harming the existing exchange environment? TIA Jim

Do not delete the First Administrative Group object. Its there because there is no process during the unistallation of Exchange 2003 to remove it ( Other than removing the org). Its cosmetic and no one sees it anywya. I would leave it as is - especially if the public folder hierarchy is still under that admin group. http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx Microsoft recommends that you do not remove the original Administrative groups from an organization. Typically, when an administrative group is removed and mail begins to back up in the System Attendant mailbox, this indicates that the Free/Busy folder from the old administrative group was not replicated correctly to one of the remaining administrative groups. On your Exchange 2003 or Exchange 2000 server, perform the following steps to move the public folder hierarchy from the Exchange 2003 or Exchange 2000 administrative group to the Exchange 2007 administrative group: In Exchange System Manager, expand Administrative Groups, right-click Exchange Administrative Group (FYDIBOHF23SPDLT), select New, and then select Public Folders Container. Expand the Exchange 2003 or Exchange 2000 administrative group that contains the public folder tree, expand Folders, and then drag Public Folders to Folders under the Exchange 2007 administrative group. Note: If you do not complete this step, the Exchange 2007 public folder database could fail to mount if you delete the Exchange 2003 or Exchange 2000 administrative group.

Andy has covered almost everything. the legacy administrative group is usefull in many free/busy troubleshooting issues if you run into any after migration There is no reason to delete this admin group anyways DhruvDhruv

Thanks guys. Just wanted to check. Jim