I've got two MBX servers, each with its own public folder store. We have data on one store and i need to get it moved over to the other server before the first one can be decommissioned. If i run "get-publicfolder -Identity "\DataToBeMoved" -Recurse | fl name,Replicas", it shows replicas existing on all the MBX servers in the org, including the one i want to rehome them to. However, if i open PFAdmin and connect to the new server, it shows zero items and zero kilobytes. When i use PFAdmin to connect to the old server, it shows the correct number of items and kilobytes. I verified this again by changing the client settings on the user database to point to each public store. First i pointed it to the public folder store on the old server and all the data was there when viewed in Outlook. When i changed it to the public folder store on the new server, there was nothing in the public folders when viewed through Outlook. How is it that a replica supposedly exists on the new server but nothing is there? More importantly, how can i get the data over to the new server? I tried running MoveAllReplicas.ps1 but nothing changed. Exchange 2007 SP2, native mode.

Are there any replication messages in the SMTP queues? How long have you waited since creating the replicas? Public folder replication does take time. Also check the replication schedule on the empty store and make sure it's not set to never.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "blinkyjesus" wrote in message news:f45974ed-3e61-4db2-8662-63bc69ea81ac... I've got two MBX servers, each with its own public folder store. We have data on one store and i need to get it moved over to the other server before the first one can be decommissioned. If i run "get-publicfolder -Identity "\DataToBeMoved" -Recurse | fl name,Replicas", it shows replicas existing on all the MBX servers in the org, including the one i want to rehome them to. However, if i open PFAdmin and connect to the new server, it shows zero items and zero kilobytes. When i use PFAdmin to connect to the old server, it shows the correct number of items and kilobytes. I verified this again by changing the client settings on the user database to point to each public store. First i pointed it to the public folder store on the old server and all the data was there when viewed in Outlook. When i changed it to the public folder store on the new server, there was nothing in the public folders when viewed through Outlook. How is it that a replica supposedly exists on the new server but nothing is there? More importantly, how can i get the data over to the new server? I tried running MoveAllReplicas.ps1 but nothing changed. Exchange 2007 SP2, native mode. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi,Public Folder replication contains of Hierarchy replication and Content Replication. Hierarchy replication happens automatically and cannot be stopped. Content replication is not automatically replicated.Thus, you need to replicate the data manually from one server to another. Below article is for your reference:http://technet.microsoft.com/en-us/library/bb691120.aspxAdditionally, please check the replication message in the Event log.ThanksAllen

Hi, As others said The replication u r talking about is PF Hierarchy replication. It doesnt replicate the data. For data replication you will have to use "Update-PublicFolder" comamnad like This example starts content replication of the public folder "\Root\PF" from the server "PFServer" to all of the servers on the replication list for Public Folder "\Root\PF" . Update-PublicFolder "\Root\PF" -Server "PFServer" Regards, Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

just to be clear, the solutions suggested *should* be the right ones, however they were not. ..that's why i asked the question here, because the microsoft prescribed solutions didn't work. i ended up having to hack AD with adsiedit to resolve the problem.

Hi blinkyjesus,What exactly do you mean by hack AD to resolve.....Could you little elaborate what were the steps taken? Regards, Pushkal MishrA

After i confirmed that the folders had indeed replicated (despite what Exchange uninstall was saying), i followed these steps..http://msexchangetips.blogspot.com/2006/07/exchange-cannot-delete-public-folder.htmlIt was ugly and i hated doing it, but it worked.