locked
Email Address Policies RRS feed

  • Question

  • I'm confused by Exchange 2010 Email Address Policies and would appreciate a little guidance.

    I'm in the middle of migrating from 2003 to 2010, so right now all I have are the 2003 recipient policies.

    I want to create a new policy so that any mailboxes I create (rather than migrate) on the 2010 server get first.last@domain.com as their default email address on the new mailbox (migrated mailboxes carry over their existing addresses it seems).

    However, I'm cautious/paranoid that if I do it incorrectly everyone in my organisation may have their email address changed - which is obviously not good (to put it mildly).

    What's the best way to go about this please?  Still pretty new to 2010 so if it can be done via the EMC that would be good.


    Tuesday, June 21, 2011 8:41 AM

Answers

  • Paul, you'll have to create an accepted domain and to create a policy name.surname@company.com.

    If this will be the primary SMTP, you'll have to specify that.

    Also remember that you can convert the Exchange 2003 policies to use them in Exchange 2010

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

    It's important to have good policies because EVERY time you modify a mail object, the address policies will be applied, so also the "migrated" users are subkect to them.

    lowercases or uppercases it's not important, I don't know if there is a way to "force" lowercases :-)

     


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    • Proposed as answer by Fabrizio Volpe Tuesday, June 21, 2011 9:19 AM
    • Marked as answer by Gen Lin Monday, June 27, 2011 2:35 AM
    Tuesday, June 21, 2011 9:19 AM
  • It seems to me that a default addressing policy with first.last@domain.com it's enough.

    If you create a policy that works for one user, it'll work for everyone, don't worry :-)


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    Tuesday, June 21, 2011 9:32 AM

All replies

  • Paul, you can have more than one policy, so the worst thing that could happen it's to have a wrong "primary" SMTP address (the one you're writing from).

    If you have more than one mail domain, you can configure a policy for every alias.

    Of course, the suggestion is to migrate few users, see if the result is the one you desire, and then go on :-)


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    Tuesday, June 21, 2011 8:51 AM
  • Thanks Fabrizio, right now I have a few dozen users on the new server.

    I can go through the wizard and see how to create a new policy.  Where I'm unsure is on the schedule tab where I can choose to apply it?

    All of my mailboxes have the "Automatically update e-mail addresses based on e-mail address policy" option checked on the E-Mail Addresses tab.

    Like I said my concern is existing mailboxes (especially the few hundred still on the 2003 server) and any impact on those, plus of course the few dozen on 2010 - I don't want their email addresses to change from what they are now.

    Tuesday, June 21, 2011 8:56 AM
  • The "schedule" tab for the policies it's only to avoid a performance degrade during working hours if you change a lot of mailboxes in the same time.

    In this situation you'll schedule the change for night time (for example).

    In your scenario you've two choices : remove the flag (but then you'll have to manually manage every single user) o to create a set of policies that creates the same situation you have actually.

    It's the safest way, also because any new mailbox will be "consistent" with your Exchange organization, taking the policies you created :-)


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    Tuesday, June 21, 2011 9:02 AM
  • OK thank you.  So let's say that right now, all my 2003 users have their email as joe.bloggs@company.com as the default.

    When I migrate them to the 2010 server the existing email addresses remain and no additional ones are added.

    So, if I create a new policy of first.last@company.com and choose NOT to apply it or schedule it, will it only apply to newly created mailboxes?

    One thing too, is there a way of forcing the local part of the email address to be all lower case as it seems to default to First.Last if we use "Joe Bloggs" as the user name.

    Sorry, I'm just not clear what determines when a policy is applied to existing users.

    Thanks,

    Paul

    Tuesday, June 21, 2011 9:10 AM
  • Paul, you'll have to create an accepted domain and to create a policy name.surname@company.com.

    If this will be the primary SMTP, you'll have to specify that.

    Also remember that you can convert the Exchange 2003 policies to use them in Exchange 2010

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

    It's important to have good policies because EVERY time you modify a mail object, the address policies will be applied, so also the "migrated" users are subkect to them.

    lowercases or uppercases it's not important, I don't know if there is a way to "force" lowercases :-)

     


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    • Proposed as answer by Fabrizio Volpe Tuesday, June 21, 2011 9:19 AM
    • Marked as answer by Gen Lin Monday, June 27, 2011 2:35 AM
    Tuesday, June 21, 2011 9:19 AM
  • We only need a single automatically generated email address, which is first.last@domain.com.

    Right now I'm thinking there seems little benefit in converting the existing 2003 policies as they don't actually do much, and it seems I could simply specify a single 2010 Email Address Policy that would do what we want - then when my users are all migrated I'd remove the old 2003 policies?

    I can't see how to actually get at the default email address policy in 2010 as simply changing that from alias@domain.com to first.last@domain.com would probably suffice?

    Again, my concern isn't new users, it's that I set something on 2010 and it goes off and sets all of my 2003 email address to something different.

    Tuesday, June 21, 2011 9:29 AM
  • It seems to me that a default addressing policy with first.last@domain.com it's enough.

    If you create a policy that works for one user, it'll work for everyone, don't worry :-)


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    Tuesday, June 21, 2011 9:32 AM
  • OK so last question (I swear :-)) - how do I set the default addressing policy as right now the only policies I have showing in EMC are the 2003 Recipient Policies which are, of course, all grayed out.
    Tuesday, June 21, 2011 9:47 AM
  • So you have a "default policy" grayed out ?

    Anyway, create a policy with higher priority, apply that to all users and so you have your "dafault policy"

    http://answers.oreilly.com/topic/1240-how-to-create-and-manage-exchange-server-2010-e-mail-address-policies/


    Fabrizio Volpe
    MVP Directory Services
    MCSE (NT4)(2000)(2003) - MCSA (2003)
    MCTS (SQL 2005)(Exchange 2007)(Windows 2008)
    Fortinet Certified Network Security Professional (FCNSP)
    Fabrizio[_dot_]Volpe[_at_]GMX[_dot_]com
    Tuesday, June 21, 2011 9:54 AM
  • It's greyed out simply because it's the 2003 Recipient Policy so hasn't yet been upgraded.

    I just looked at the default policy in Exchange 2003 and the SMTP was set to @domain.com so I've updated that to first.last@domain.com so I'll see what happens when I create a new account in a little while when it's replicated.

    Tuesday, June 21, 2011 10:02 AM
  • OK that seems to have done the trick.  I think over the years of moving from 5.5 to 2003 we'd acquired various recipient policies that applied to specific sites/admin groups in Exchange so the first.last@domain.com was defined on those but not on the default, if that makes sense.

    Thanks,

    Paul

    Tuesday, June 21, 2011 10:37 AM