Link to home
Start Free TrialLog in
Avatar of claudiamcse
claudiamcse

asked on

Email policy Exchange 2010 and 2003

Hello,
I have a question regarding email policies. So we have Exchange 2010 SP3 which is Hybrid server for Office 365 and we have Exchange 2003 servers.

On Exchange 2003 servers with have at least 5 emails policies that actually don’t really work except one policy for domainA.com which works if you select the option "Automatically select email address based in the email policy” So, for the users that need to have other domain as PRIMARY email address they have this checkbox unchecked “Automatically select email address based in the email policy” so that they can have another domain set as a primary! If you check that checkbox “Automatically select email address based in the email policy”, users primary email changes to a different domain which is a problem because users won’t be able to receive emails.

So, For Office 365 migration, it is really important that I add onmicrosoft.com email address through the email policy and I need to somehow figure out how to make additional policies work so for the users that need to have a different domain set as a primary, they will use a different email policy.
What are the suggestions and safe way doing it without causing issues for all the users? Do we need to upgrade email policies on the Exchange 2010 first and then modify and apply them? What are the risks?
From Exchange 2010, I can only open the Default policy. What happens if I upgrade all legacy policies with this command below? I assume it won’t change anything? But, my guess, I will still need to have a plan how to create/modify other policies so that users in different domains have different primary smpt email addresses. Please be as specific as possible and let me know how to do it and the risks of doing it?
Update email policies
http://supertekboy.wordpress.com/tag/the-specified-e-mail-address-policy-couldnt-be-edited-e-mail-address-policies-created-with-legacy-versions-of-exchange-must-be-upgraded-using-the-set-emailaddresspolicy-tas/
Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} | Set-EmailAddressPolicy –IncludedRecipients AllRecipients
Avatar of Mahesh
Mahesh
Flag of India image

In Microsoft Exchange Server 2003 and earlier versions, LDAP filtering syntax is used when customizing the default e-mail address policy. However, in Exchange Server 2010, the OPATH filtering syntax replaces the LDAP filtering syntax.
If you want to modify those legacy polices, you must upgrade the to exchange 2010 format.

There is no risk involved in the upgrade. Also, the upgrade does not apply the policy by default so existing users will not be affected. At this point of the migration, you should be creating new mailboxes on Exchange 2010 as opposed to Exchange 2003.

http://technet.microsoft.com/en-us/library/cc164375.aspx
Above link will provide you information regarding "which policies require upgrading" and how based on below categories.
Default objects   Default objects are the default e-mail address policies and address lists created when Exchange is installed.
Custom objects   Custom objects are custom LDAP filters created by an Exchange administrator in Exchange 2003 or an earlier version.
Hope that helps

Mahesh
Avatar of claudiamcse
claudiamcse

ASKER

Oh. Thank you so much. So, is this  the right command that will upgrade all the 5 legacy policies without affecting anyone?

Get-EmailAddressPolicy | where {$_.RecipientFilterType –eq “Legacy”} | Set-EmailAddressPolicy –IncludedRecipients AllRecipients
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thank you!