Any other ideas? Bueller? Bueller??
> On Jul 31, 2014, at 7:21, "Daniel Chenault" <[email protected]> wrote: > > Hrm... no, can’t be. AD will not create an object with duplicate alias; it > refuses to go forward until that is fixed. > > From: mailto:[email protected] > Sent: Thursday, July 31, 2014 7:08 AM > To: mailto:[email protected] > Subject: RE: [Exchange] Address policy oddity > > Replication time, maybe? You did set it up where it complained the first > time, maybe the modification hadn’t had time to replicate out? > > From: [email protected] [mailto:[email protected]] > On Behalf Of Daniel Chenault > Sent: Wednesday, July 30, 2014 4:07 PM > To: [email protected] > Subject: [Exchange] Address policy oddity > > Been googling but maybe my fu is fading with age :) > > 1. create user in AD with alias of FirstinitialLast name (JDoe) > 2. AD complains user alias already exists (it does) so modify to use > FirstinitialMiddleinitialLastname and that goes through (JMDoe for Michael) > and this sets both alias and pre-2K alias > 3. Go in Exchange and create mailbox, use existing user, select new account > 4. When it is all done user has three addresses (have three policies) and all > end in "2" > > Address book policies: > %1g%s > %g.%s > %m <--default > > With the above description that comes out to: > jmdoe2@ > john.doe2@ > jmdoe2@ > > Now, I understand why the first two policies append a 2: to the policy it > does indeed look like a duplicate. But the third policy using alias (%m) > should not happen as that has already been modified during the AD account > creation and guaranteed unique (or AD would not have allowed creation). > > Any ideas?
