I am doing a migration from SBS 2003 to SBS 2011 for a customer. The Exchange portion of the migration follows standard exchange migration procedures. So far everything is going as planned except Public Folder replication. They seem to be 'stuck'. I have tried issuing the commands from both servers with no effect.
From the 2003 server I have done the "Move all replicas" method from ESM. In ESM I can still see the Public Folder Instances is populated which tells me they have not move yet. Replication Status shows all folders as having 2 replicas and their status is "In Sync". There are no error in the event log though I just turned up diagnostic logging on all the Public folder options just now so we will see if there are any more today. I checked the replication schedule yesterday and found the Replication Limits were empty. I set the defaults but have seen no change since.
On the 2010 server it as if the Public folders from the 2003 server do not exist. They are not listed in the public folder management (only the default 2 folders). I used the AddReplicaToPFRecursive.ps1 & MoveAllReplicas.ps1 scripts and Update-PublicFolderHierarchy command from the 2010 server yet still when I run Get-PublicFolder or Get-PublicFolderStatistics the only folders reported on are the two defaults and system folders.
I thought if replication is going to work I would do it manually. So I restored the public folders from backup to a PST and using Outlook (as a user whose mailbox has been moved to the new server) I copied them all to the new server. The Exch2010 server can see and manage them but when I try to mail enable them and assign the address they had before, it complains that the address is in use.
Some other details:
The Exchange 2010 server was at RTM when I started the replication. I have since updated to SP3 and all other server updates.
Outlook clients whose mailbox is still on the 2003 server can see the folders but none of the content. The get a “Cannot access the specified location” error
Firewall is off for Domain networks
I am not seeing any other problems of communication between the servers in other areas of the replication (AD, file shares, etc)