EDIT 10/18/2010: Removed the reference to upcoming fix (no fix current planned). Some customers are finding that when they try to replicate their public folder content to Exchange 2010, it will n...
Updated Jul 01, 2019
Version 2.0
Blog Post
Sometimes I wonder if it's a subtle nudge to get us off Public Folders ;).
I'm 4/4 Of 2010 migrations where the empty servers container causing routing issue has emerged, so I'm VERY glad that there is now a somewhat official link i can reference future clients to assure them I'm not randomly hacking around with ADSIedit and that this is a MS acknowledged problem and fix (though a KB article would be wonderful, even if you dont provide a hotfix)
It does introduce its own problem, however:
The BPA for 2010 will report a configuration error if it can't find the servers container for the legacy group, despite this being the recommended fix. Combine that with the already existing false positive of the schema extension being an unknown revision and the BPA tool is quickly becoming unreliable. Along with regular rollups, Exchange 2010 is in desperate need of some new BPA definitions.
Finally, one parting shot: please stop pressing the de-emphasis of public folders until you have a suitable replacement built-into exchange? It's tough to tell people they now have to purchase and deploy a whole new platform just to use a functionality they currently enjoy for free. I get the replication model blows. I get that it's dated and obsolete. Let it die. But not before you have an Exchange native answer. It hurts those of us consultants who are trying to sell this otherwise fantastic platform.
OK parting shot taken ... keeping pressing forward on what is clearly the best Exchagne release to date .... and Ill promise to ride you less on the rough edges ;)
I'm 4/4 Of 2010 migrations where the empty servers container causing routing issue has emerged, so I'm VERY glad that there is now a somewhat official link i can reference future clients to assure them I'm not randomly hacking around with ADSIedit and that this is a MS acknowledged problem and fix (though a KB article would be wonderful, even if you dont provide a hotfix)
It does introduce its own problem, however:
The BPA for 2010 will report a configuration error if it can't find the servers container for the legacy group, despite this being the recommended fix. Combine that with the already existing false positive of the schema extension being an unknown revision and the BPA tool is quickly becoming unreliable. Along with regular rollups, Exchange 2010 is in desperate need of some new BPA definitions.
Finally, one parting shot: please stop pressing the de-emphasis of public folders until you have a suitable replacement built-into exchange? It's tough to tell people they now have to purchase and deploy a whole new platform just to use a functionality they currently enjoy for free. I get the replication model blows. I get that it's dated and obsolete. Let it die. But not before you have an Exchange native answer. It hurts those of us consultants who are trying to sell this otherwise fantastic platform.
OK parting shot taken ... keeping pressing forward on what is clearly the best Exchagne release to date .... and Ill promise to ride you less on the rough edges ;)