Two years ago, I posted a three-part series on troubleshooting public folder replication. Part 1 discussed the replication of new data, Part 2 discussed the replication of existing data, and Part...
Updated Jun 05, 2020
Version 3.0
Blog Post
6 MIN READ
Public Folder Replication Troubleshooting - Part 4: Exchange Server 2007/2010 tips
Hey Ian,
As the Exchange team pointed out, if the problem is caused by a bug in our software, then you are refunded the cost of the incident. Of course, we don't know ahead of time whether it will be a bug or not. In the previous cases I found, that particular error was being caused by third-party products modifying or creating content in strange ways rather than by a bug in Exchange.
If you'd rather not open a case, your best bet is probably the PST route.
As the Exchange team pointed out, if the problem is caused by a bug in our software, then you are refunded the cost of the incident. Of course, we don't know ahead of time whether it will be a bug or not. In the previous cases I found, that particular error was being caused by third-party products modifying or creating content in strange ways rather than by a bug in Exchange.
If you'd rather not open a case, your best bet is probably the PST route.