Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Email policy Exchange 2010 and 2003

Posted on 2013-11-21
4
Medium Priority
?
687 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 37

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 37

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

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

705 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