Public Folder Instances won't empty


I'm picking up finalizing an Exchange 2003 to Exchange 2010 migration months later after one of my peers dropped the ball on it.

The Exchange 2003 environment is a cluster...not sure if that plays a part or not.

There are a handful of public folder instances that won't finish replicating. I have to believe they were started to be replicated several months ago, so I feel like enough time should have passed.

Not sure where to do. I've tried a few things to try to push it along. These public folders (subfolders of parent folders) are tiny. The largest is 2MB.

I've verified that the Exchange server can communicate with the CAS server on port 25 using telnet, and the Exchange 2003 server is not using a smarthost.
Who is Participating?
RadweldConnect With a Mentor Commented:
The system folders will host your free busy information. As long as your clients are at least outlook 2007 then you no longer need to preserve them.
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
Are they system folders or regular folders that you can see in Public Folders through Outlook?
If the latter, then the method I have used is pretty simple.

1. On the new server add the old server back in the list of replicas, so you have both the old and new server listed.
2. Recreate the folder, move all permissions and email address (if mail enabled) to the new folder.
3. Delete the original.

Key here is that both servers are in the list of replicas, so the deletion is replicated.

RadweldConnect With a Mentor Commented:
In the %exchangeinstallpath% folder where exchange is installed there is a scripts folder. In there is a script to add the exchange 2010 server as a replica. It's worth while running this again to ensure all folders have the new server as a replica.


Other scripts for public folder management an be seen here.

Other methods to control public folder replication on a more granular scale can be found here.

If you find a situation where replication doesn't sync all objects you will need to troubleshoot this, the following blog is useful.

Hope this helps.
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tom-J-LaelAuthor Commented:
@simon ,

two of the folders appear to be system folders.
Simon Butler (Sembee)ConsultantCommented:
System Folders you don't need to really worry about. If you can get rid of the rest, then those can be removed another method.

Although once you have removed the others, do use the Move All Replicas command in ESM again. I have found that running it two or three times can poke things in to life.

Tom-J-LaelAuthor Commented:
Only 3 of the 9 calendar's in these PF's are actively used.

Currently I'm exporting the entire PF folder structure out to .PST, i'm going to configure each server to replicate to each other, then purge out the calendars that aren't in use.

For the 3 that are in use, I'm going to copy those into a different PF folder, and delete the original. Hopefully these deletions will propagate over to the Exch2003 server and those PF instances will empty out. I'll let you know...
Tom-J-LaelAuthor Commented: I'm down to just the system folders in the public folder instances. How do I deal with those?
Tom-J-LaelAuthor Commented:
I'm giving a B for everyone's effort. Ultimately the issue boils down to this client having their AD all jacked up. Their full time IT staff will need to address those unless they want to incur some expense having us do it.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.