This post is to explain on how to resolve Public folder replication issues between databases in different locations across data centers. Lately in my organization we faced a problem where public folder in One site was not getting replicated to other site after the transition from Exchange 2003. The newly folders added /deleted were only seen in the Data Center hosting the public folder database.
For this example I would take Public folder residing in UK replicating to US and viceversa.
To Start off and see what’s going on I enabled the Advance Diagnostic Logging for the exchange Management console.
Open Exchange Management Console, Expand and select Server Configuration.
On the right you will find all the servers, Select the Exchange Server where public Folder Database is residing.
Right click on the Server and select Manage Diagnostic Logging.
Expand to reach MSexchangeIS-> Public and then set the components Replication AD Updates, Replication Incoming Messages, Replication Outgoing Messages, Non-Delivery Reports, Replication Backfill, Replication General to expert and then click Configure. Do this on both the Public Folders.
This would enable Advance level diagnostics and would raise event in Event viewer when you try to replicate the Public folder Database Manually by doing an Update hierarchy in Exchange management Public folder toolbox.
Although when you’d a update hierarchy manually the best way would be to Open Log Viewer in Exchange management Console and look for failed events as shown below. In the below example it clearly shows that the folder content fails upon receiving changes from the Public folder hosted on the other Site.
We have to check if the registry key replication flags was set to disabled in registry. As per Microsoft this was a result of 2003 Exchange public folder database not being migrated correctly.
Changed the registry key value “Replication Flags” to 1 in –HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchnageIS\Exchange Server Name\Public-8fecc579-fd3e-48e5-b3d1-191c39df28d5 on Exchange Server Name.
Note : Exchange server name has to be your server hosting the Public folder database. Make the Above change also to the Exchange server where public folder is replicating to
Open adsitedit.msc and connect to Configuration
Expand CN=Services CN= Microsoft Exchange—CN= Organization name (replace it with your Organization name listed) CN=Administrative Groups——Legacy Exchange Server Names.
Remove server objects from within the Old legacy 2003 attributes. In Below Example under my case it was London and North America.
After this change dismount and remount the public folder databases and Try to make a Test folder by going to Exchange Management console and Public Folder Console.
Update the hierarchy manually and wait for 10-15 minutes for having it replicated on the US node.
Also you can open log viewer and see the events that are been logged after doing an update hierarchy.
As you can the Public folders are now replicating and delivers the changes correctly to the other site in US.
Feel free to post up questions and comments.