I'm in the process of replacing public folder servers, I want to be sure replication is complete before removing old servers. Anyone know of a tool that will automate this? Maybe a script that will produce a report showing all folders that are not equal in items. I have 50k folders, this will take months of checking manually. Would also be good to be able to force replication globally. If I were confident of this I might be okay, way it is now about 1 out of 10 folders didn't replicate to the new server. I can update changes and make it happen - but again 51k folders that is a lot, even if it is only 1 out of 10, still a lot of time.

Hi, pls have a look on this.. it may help you.. http://social.technet.microsoft.com/Forums/en/exchange2010/thread/8fd335e6-05dd-4922-87eb-754f8f170a30Kottees : My Blog : Please mark it as an answer if it really helps you.

Thanks. Some good information but doesn't apply to what I'm looking for. These pf servers are e2k3 and I'm wanting to report on replication globally. Out of 51k folders, if 1 isn't fully replicated and I remove Exchange, then that folder is lost. I figured someone had seen a tool or a way to use pfdavadmin to get a global report.

Use pfdavadmin, there an option there to export all replicas so you know all folders have a replica and you can export item count too.Sukh

get-publicfolderstatistics with 2010. pfdavadmin with 2003: http://blogs.technet.com/b/exchange/archive/2007/04/24/3402074.aspx Its a little harder with 2003 in the mix versus 2007 and 2010, but if take that csv exported from pfdavadmin and then pipe the results of get-publicfolderstatistics to another csv you should be able to compare using excel Another option is : http://gallery.technet.microsoft.com/scriptcenter/2c17e612-c2c0-48e8-9451-2abc7c7bc46d Though I have to admit, I never liked using this when it first came out so many years ago because it involved permission changes.

Use pfdavadmin, there an option there to export all replicas so you know all folders have a replica and you can export item count too.Sukh

get-publicfolderstatistics with 2010. pfdavadmin with 2003: http://blogs.technet.com/b/exchange/archive/2007/04/24/3402074.aspx Its a little harder with 2003 in the mix versus 2007 and 2010, but if take that csv exported from pfdavadmin and then pipe the results of get-publicfolderstatistics to another csv you should be able to compare using excel Another option is : http://gallery.technet.microsoft.com/scriptcenter/2c17e612-c2c0-48e8-9451-2abc7c7bc46d Though I have to admit, I never liked using this when it first came out so many years ago because it involved permission changes.

I have no 2007 or 2010, only 2003 public folders. I thought pfdavadmin would do this but the replica report only shows No, I guess for in-sync. This doesn't help, even if it pulls the info from the replication tab in ESM, this doesn't help. I've looked through the properties in Export Properties, I can export the number of items for the specific server I'm connected to. I don't see a way to export items for all replicas so I can compare the number of items. Looking at the link from A_D - thanks.

So, I've gotten pfdavadmin going. Export each server to compare item numbers to the original. Is there no way to force a heirarchy to resend changes? This is 2003 sp2. I have easily 50 folders each have 100 to 1000 subfolders, some are in synch some aren't. I believe this is all backfill, the servers think they are in sync in most cases. Yeah, eventually, they would sync up but I need to remove the orignal server, so I need to force this as much as possible. Is there no way to force everything in the heirarchy to resend changes?

IN 2003 SP2, you can issue a resend changes command that will manually update. I typically choose 9999 days or something Another trick is to use pfdavadmin to check item level permissions and recurse through the tree. That will touch each folder and hopefully kick something off.

On Fri, 30 Mar 2012 14:32:23 +0000, A_D_ wrote: > > >IN 2003 SP2, you can issue a resend changes command that will manually update. I typically choose 9999 days or something > >Another trick is to use pfdavadmin to check item level permissions and recurse through the tree. That will touch each folder and hopefully kick something off. I think you have to tell it to *remove* item-level permissions for it to actually 'touch' the items in the folders. I don't think that does anything for the folders though, just the folder contents. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP