We help IT Professionals succeed at work.

Migrating exchange 2003 to exchange 2010 and having issues decommissioning old server

bcameron70 asked
Hey there, I am trying to decommission an exchange 2003 server after I have followed the process for proper migration (I guess I missed something though)

migrating from Exchange 2003 on Small Business server to Exchange 2010.  All mailboxes moved and public folders replicated.  Trying to decomission old exchange server.  While attempting to remove public folders, i get an error that i cannot delete because it contains replicas.  When I try to move replicas to the new server, I get an error: Your PRofile cannot be configured.  An unexpected error has occured. microsoft exchange server information store.  ID no: 8004011c-0521-00000000. ID no: c1050000 Exchange System manager

I was able to get rid of the mailbox store on the old exchange, it's just the public folders giving me issues now.

any assistance is appreciated
Watch Question

There are a number of things you need to do, firstly you need to move all replicas to exchange 2010 using the following commands.

Addreplicatopfrecursive.ps1 which ensures folders are replicated properly

Moveallreplicas.ps1 which moves all pf data from the old server to the new one.


You then have to make sure that your databases on exchange 2010 are using the public folder mounted on exchange 2010 the command get-publicfolderstatisticts can help you establish the replication process.

You can do this with the set-mailboxdatabase command


You will need to ensure the RUS is assigned to exchange 2010, also the offline address book gen process.

Bear in mind that once you remove exchange 2003 you won't be able to restore mailboxes that were backed up from exchange 2003.


Do I download powershell to the 2003 box to perform these commands, or run on the 2010 box?

The error you get when trying to move the  replicas is because your PF database is dismounted
You stated that all mailbox are moved and all public folders are replicated. If you are sure about that and you followed the sbs migration wizard, then you can delete the Public Folder Database object with ADSIedit and uninstall the sbs2003 through add-remove programs,
If you do remove the public folder store from ADSI edit then this will probably break the default site public folder and also more likely the public folder hierachy.

I forgot to mention the importance of Updating the public folder hierachy


Only delete the default folder in Adsiedit if you have no option, I've had to do it several times.

This article detailed the steps to fix the default site store.