I have 4 copies of a public folder store, two copies in different AD sites residing on 2010 servers (being accessed from 2013)

I'm using Exfolders (the new PFDAVADMIN) for debugging the widespread replication issue.

In exfolders, I've gone to each copy of the public folder (on each server) and did a bulk edit of 

* Replicas (to merge and add all 4 servers) 
* Sync time (always)

But on one server, I was still getting "no replica available" when I expanded a folder.  As a result I went to each server and selected "propagate replica list".  That force-fixed the replicas.. but still I'm getting not matching contents as illustrated in the image below:

 

Note the scroll bar length is different for each.  

**Question**

How can I force all copies of all folders to be up to date -without risking losing data?

What might have caused this to be in this state?

Cross post from ServerFault http://serverfault.com/q/715854/51457  

  [1]: http://i.stack.imgur.com/sJpwr.png

You have posted in an Exchange 2013 forum.  The Exchange previous versions forums are here:  http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegac

This kind of problem is very hard to diagnose because public folder replication is a black box.  I would follow this general procedure.

1. Force replication (Update-PublicFolder).  It appears you've already done that.

2. Remove the incomplete replica, wait a while for it to disappear on that server, add the replica again and see if it replicates fully.

3. If that doesn't work, create another folder with a slightly different name, copy the content from the bad folder to the new one, create all the replicas, then delete the bad folder.

You can also enable diagnostic logging for public folder replication:

'ExchangeServerName\MSExchangeIS\9001 Public\Background Cleanup' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\General' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Replication Backfill' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Replication Conflicts' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Replication Errors' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Replication Incoming Messages' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Replication Outgoing Messages' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Transport Delivering' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Transport General' | Set-EventLogLevel -Level 'High'
'ExchangeServerName\MSExchangeIS\9001 Public\Transport Sending' | Set-EventLogLevel -Level 'High'

Message tracking logs can also be helpful here because Exchange 2010 will send the public folder data by email. You'll be able to see if emails are bouncing back.

I know you're not using Exchange 2003 but this post provides more information about what the message types mean: http://www.msexchange.org/articles-tutorials/exchange-server-2003/management-administration/Public-Folder-Replication-Troubleshooting.html 

The final thing is that public folder replication takes time and sometimes you just need to wait a few days and see.

Thanks.