Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Email policy Exchange 2010 and 2003

Posted on 2013-11-21
4
Medium Priority
?
697 Views
Last Modified: 2013-12-06
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
0
Comment
Question by:claudiamcse
  • 2
  • 2
4 Comments
 
LVL 39

Expert Comment

by:Mahesh
ID: 39667271
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
0
 

Author Comment

by:claudiamcse
ID: 39667803
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
0
 
LVL 39

Accepted Solution

by:
Mahesh earned 2000 total points
ID: 39668295
The command syntax is perfect.
You require more complex syntax for polices having custom LDAP filters.
1st identify polices having custom LDAP filters with above link.
I suggest you to check this section Upgrade Custom objects in above technet article

Also you may find below links useful..
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/
http://careexchange.in/upgrading-email-address-policies-and-address-lists-from-exchange-2003-to-exchange-2010/

Thanks
Mahesh
0
 

Author Closing Comment

by:claudiamcse
ID: 39701760
Thank you!
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
In this article, I will demonstrate that how to do a PST migration from Exchange Server to Office 365. This method allows importing one single PST, or multiple PST's at once.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question