Exchange Address List Upgrade For Exchange 2010

During a recent migration for a customer we were following the article for decommissioning legacy Exchange 2007 servers [http://technet.microsoft.com/en-us/library/bb288905(exchg.80).aspx].  One of the steps invloves updating the email address policies to make them compatible with the new version of Exchange.  One way to do this is a one liner you can run in PowerShell:

Get-EmailAddressPolicy | where {$_.RecipientFilterType -eq “Legacy”} | Set-EmailAddressPolicy -IncludedRecipients AllRecipients

However, the upgrade did not work and we were left with the error messages you see in the screenshot below:

After, doing a bit of research we realized that the previous upgrade to Exchange 2007 from Exchange 2003 had not been done cleanly.  One of the steps in the “How to Remove the Last Legacy Exchange Server from an Organization” ,article mentioned above, is that  “Mailbox Manager Settings” needs to be removed from the Email Address Policies.  Apparently they had not been removed.  In our case we had no Exchange 2003 server or tools to work with.  The only way to remove the attributes is to use ADSIEdit.  We used these two articles for details on this process:

http://bizsupport1.austin.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=1840527&prodTypeId=18964&objectID=c02452399

http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010—part-ii/

Using ADSIEdit as described above, we removed the references to Managed Mailbox Policies.

Once fixed we re-ran the update script and you will see this for each policy you are updating:

Confirm To save changes on object “Default Policy”, the object must be upgraded to the current Exchange version. After the upgrade, this object cannot be managed by an earlier version of the Exchange Management Tools. Do you want to continue to upgrade and save the object? [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is “Y”): a

Now all the policies are up to date and they can be edited from Exchange 2010.