Migrating Public Folders from (SBS) Exchange 2003 to (SBS) Exchange 2011 never completes

We are doing a migration from Exchange 2003 (SBS 2003) to Exchange 2011 (SBS 2011) and everything has gone swimmingly other than migrating the public folders.

We went into the admin console and set the public folder to move to the Exchange 2011 box.

The public folder instance directory is still showing objects in there on the Exchange 2003 box, meaning the migration didn't occur.

We're at a loss at why since there are no errors. It's been about 10 days, so plenty of time for the migration (which we know can be slow). These aren't huge public folders.
puryear-itAsked:
Who is Participating?
 
Alan HardistyCo-OwnerCommented:
Check the Replication Message Priority for Each Public Folder:

Exchange System Manager> Administrative Groups> First Administrative Group> Folders> Public Folders> Folder Name

Right click on each Public Folder and choose Properties.

Click on the Replication Tab and make sure the Bottom Drop Down option is set to URGENT and the 'Public Folder replication interval' option is set to Always Run.

Check the other Public Folders and repeat until you have checked them all.

Then try requesting the PF move again and check the Public Folder Instances folder (under First Storage Group> Public Folder Store> Public Folder Instances - the folders should start to disappear with any luck, but allow the server a little bit of time before you consider nothing is happening, worst case overnight.

Then you can hopefully finish the migration before the 21 day limit starts to cause you problems!!
0
 
dreamraghuCommented:
IF you have lot fo public folders to migrate it to Exchange 2010, it not suggestable to do a moveallreplicas, because you will see a huge mail strom that effect your e-mail flow and etc...
The best thing is that, add the replica for few folders and once those are replicate, you can add different set of folders(stage by stage) and also set the replication type to URGENT and pf replication interval option to ALWAYS RUN.
0
 
Alan HardistyCo-OwnerCommented:
@dreamraghu - Have you done many SBS 03 to SBS 2011 mirations?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
dreamraghuCommented:
Yes, i did.

The procedure will applications for all exchange verions, whether it is SBS exchange or exchange servers.
0
 
Alan HardistyCo-OwnerCommented:
Okay - so why are you suggesting to not use moveallreplicas which is recommended in the MS migration article and then and then repeating comments that I have already made?
0
 
dreamraghuCommented:
Yes, Thats the recomended step, but if we have lot fo public folders then when you use the moveallreplicas, you will see a huge mail strom that effect your e-mail flow and etc...

The best way is to add the replica of the new server and do a replication.
0
 
Alan HardistyCo-OwnerCommented:
Well - it's never caused a problem for me and I have migrated dozens of SBS 03 to SBS 11 servers with hundreds of Public Folders on them :)
0
 
dreamraghuCommented:
I mean, if you have lot of public folders with huge size then we will have that issues. If it small database size and soem public folders, there will not be any issues.

Mine is just a recomendations if you have public folder database with huge size.
0
 
Malli BoppeCommented:
I haven't done any SBS migration but
This is what I did to migrate from e2k3 to e2010
Add public folder replicates
go to each public folder and force the replication.
0
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.