Upgrade the default Email Address Policy to Exchange Server 2007 OPath format using this Exchange Management Shell command.
[PS] C:\> Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipients
If you have any additional custom EAPs you can upgrade them by following the advice at the Set-EmailAddressPolicy Technet page.
In organisations with only the default Email Address Policy, Address Lists, and Global Address List, you can complete the Exchange upgrade with a script instead of running each command manually.
Download the Exchange Transition Script.
Can I feed a txt file with all the user details so it applies to those users only?
No, Email Address Policies use queries not static lists.
Hello,
Attempting to migrate from 2003 to 2007 using this command. Set-EmailAddressPolicy “Default Policy” -includedrecipients allrecipients. Error The recipient policy “Default Policy” with mailbox manager settings cannot be managed by the current version of Exchange management Console. Please use a management console with the same version as the object at Line:1 char:23
Any ideas?
Yes. You’ll need to disable the mailbox manager settings in that policy before it can be upgraded.
Hi Paul
some additional information, what if there are multiple (say around 30) email address policies will this command change the users reply address? I was thinking of running either of the 2 commands below, are these the same as the one mentioned above?
update-emailaddresspolicy – Identity ‘Default Policy’
or
Set-EmailAddressPolicy -Identity ‘default policy’ -IncludedRecipients ‘AllRecipients’ -ForceUpgrade ‘True’
Thanks
James
Hi Paul
I was wondering, I’m getting this This email address policy is corrupted or was created in an earlier version of Exchange. Use the Exchange Management Shell to change the filter. will this command solve this? If I run this, will there be any potential issues I might encounter? Thanks
James
Yes, that warning should go away when you update it from the shell. Shouldn’t cause any issues that I’m aware of. I usually do this step after removing all legacy servers from the organization.