Wednesday, 9 September 2015

The Microsoft Exchange administrator has made a change | Exchange 2007 to 2013 migration

Interesting issue today where we decommissioned an Exchange 2007 server and Outlook clients prompted with the all too familiar "The Microsoft Exchange administrator has made a change that requires you quit and restart Outlook".

This is often seen when mailboxes are moved between servers or in a DAG/CAS array failover but this was not the case this time. The only changes made were deletion of the public folder database on Exchange 2007 and decommission of the Exchange 2007 server. 

In the Exchange 2007-2010 days, you'd set the default public folder database for each mailbox database by using Set-MailboxDatabase so I checked to see what this setting was on Exchange 2013 and found that it referenced the deleted public folder database:

You cannot use either of the below commands to remove the setting: 
Set-MailboxDatabase -PublicFolderDatabase $null
Set-MailboxDatabase -PublicFolderDatabase ""

To remove the setting from the mailbox databases, you need to use ADSIEdit. To do this, open up ADSIEdit and connect to the configuration naming context:

Browse to CN=Services > CN=Microsoft Exchange > CN=Organization Name > CN=Administrative Groups > CN=Exchange Administrative Group (FYDIBOHF23SPDLT) > CN=Databases. 

For each database open properties and clear the value for the msExchHomePublicMDB attribute:

This should resolve the issue.


  1. Thank you, this really helped me!

  2. No problem Andy - glad it helped!

  3. Great article, thanks for sharing the helpful information,It discusses step-by-step migration from Exchange 2007 to Exchange 2013 , I also found related information from that helps to execute hassle-free migration from Exchange 2007 to Exchange 2013

  4. I have been dealing with similar issue for a while with a customer and tried so many things until I saw your article which was right on. Several users been complaining about this popup and wasn't able to identify the cause. Thank you for taking the time to write and share your experience. It helped me resolve my issue.

  5. Suddenly starting getting this error POST 2008 to 2016 exchange migration almost a year after the actual switch over.

    Located this key, cleared, rebooted and error gone.

    Resolved the error on my Exchange 2016 stand alone mail server.