Exchange 2010: Troubleshooting 'Public Folder Replication fails due to empty legacy administrative group' using ADSI Edit tool

Some times you may find that when you try to replicate public folder content to Exchange 2010, it willn’t replicate. Looking at app log, you may find an event like (see pic). “This happens because if a Servers container exists, there’ll be a System Attendant object somewhere inside it. However, in an environment where Exchange […]

Some times you may find that when you try to replicate public folder content to Exchange 2010, it willn’t replicate. Looking at app log, you may find an event like (see pic). “This happens because if a Servers container exists, there’ll be a System Attendant object somewhere inside it. However, in an environment where Exchange 2000 or 2003 previously existed, and all those servers have been removed, you probably have First Administrative Group or some other Administrative Group still hanging around with a Servers container, but no servers inside it. When Exchange 2010 Store Driver stumbles across this empty Servers container, this error is the result,” explains Microsoft. A fix is scheduled in upcoming rollups for Exchange 2010. In the meantime, you can get rid of empty Servers container by deleting it using ADSI Edit tool (Start ADSI Edit (Start, Run, adsiedit.msc). This tool is part of Windows 2000 and later Support Tools so make sure you’ve these tools installed).

More info: documentation on TechNet

[Source]