Exchange 2007 decom after Exchange 2013 installation

Afternoon,

We have installed exchange 2013 and it has been running successfully for a while. We are at the point where we would like to decommission the exchange 2007 environment, but I am having issues.

When I run the setup.com /mode:uninstall /removecms /cmsname:xxxx i get an error about the public folder replicas.

When I try to run the moveallreplicas.ps1 i get another message

'There is no existing 

 Publicfolder that matches the following: '\'

It seems that this is a product of being having both 2007 and 2013 in the environment. The organisation has not used public folders for years so getting rid of them is not a problem.

What is the best way forward as I need to decommission the old Environment ASAP!

Thanks for any assistance!!

September 7th, 2015 9:50am

If you are not using public folders then eliminate them.

https://technet.microsoft.com/en-us/library/aa998329%28v=exchg.80%29.aspx

You will need to delete the public folders that exist in there first, then you will be able to drop the public folder database. The uninstall should be successful then.

Simon.

Free Windows Admin Tool Kit Click here and download it now
September 7th, 2015 10:12am

As a workaround try this from Exchange 2007 shell command run commands:

Get-PublicFolder -Server <your server name>  "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server ex2007 -Recurse -ErrorAction:SilentlyContinue

Get-PublicFolder -Server <your server name>  "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server EX2007 -Recurse -ErrorAction:SilentlyContinue

Disable-Mailbox  all mail box in last Exchange 2007 & Remove your Exchange 2007 from add/remove

You may also take help from below given informative resources that might helps you:

Removing Exchange 2007 Error with Public Folder Replicas: http://www.telnetport25.com/2008/12/removing-exchange-2007-error-with-public-folder-replicas/

Migrate from Exchange 2007 to 2013 & Decommissioning Exchange Server 2007: http://mstechtalk.com/step-by-step-guide-to-migrate-from-exchange-server-2007-to-exchange-server-2013/

Hope it helps you!
September 8th, 2015 2:48am

Hi,

Besides, we need move all mailbox, content, public folder, OAB generate server and mail flow to new server before decommission legacy Exchange server. For your reference: https://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx

If you get same error after complete the suggestion as Philip mentioned, we might need modify the public folder items in ADSI Edit. More details please refer to below thread: https://social.technet.microsoft.com/Forums/office/en-US/f81731a0-3ffc-4a53-acef-9e6379d9fffd/decommission-exchange-2007-server?forum=exchangesvrgenerallegacy

"Open ADSI Edit and then navigate to:
Configuration > Configuration -> Services > Microsoft Exchange > Exchange organization > Administrative Groups > Exchange 2007 administrative group > Servers > server holding the PF store that you wish to delete > Information Store > the storage group containing the store that you want to delete

Right-click on the PF store and select Delete in the context menu and voila the server can be uninstalled"

Free Windows Admin Tool Kit Click here and download it now
September 8th, 2015 3:44am

I had the same issue just a few days ago and used ADSIEDIT to remove the public folder database from Exchange 2007 then could decommission without issues. 

Thanks.

September 9th, 2015 9:33am

Agree with Mark,

we also had to use ADSIEDIT to remove Public folder. None Powershell command works.

So if the other guides fail, please remove from ADSIEDIT and uninstall Exchange server as normal for final step of decom.

Free Windows Admin Tool Kit Click here and download it now
September 9th, 2015 9:43am

I ran into an issue where Outlook continuously prompts for a restart when the Exchange 2007 server was decommissioned and I think it's due to deleting the public folder database using ADSIEdit and not the Exchange tools. It's easy to resolve though. See here: http://markgossa.blogspot.co.uk/2015/09/exchange-2013-migration-microsoft.html.

Anyways, deleting the public folder through ADSIEdit then going through the steps in the link above to prevent outlook issues should answer your question. 

September 10th, 2015 5:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics