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

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 245
  • Last Modified:

Exchange 2010 - The right way to add John Doe Jr

Why did Microsoft automatically add a '2' to my primary SMTP address? What is this called and where is it documented? Even after I fixed the problem why did OWA have temporary permissions problems on the mailbox:

"The Active Directory resource couldn't be accessed. This may be because the Active Directory object doesn't exist or the object has become corrupted, or because you don't have the correct permissions."?

I created my own fix, but I'd like to throw this out for the experts.

John Doe has been working for Acme Consulting for several years.  He has a domain account on acme.local and a mailbox in Exchange 2010. John's son, John Doe Jr., does some contract work and eventually earns full employment. On John Doe Jr's first day as a full-time employee I get a request to provide him with an Exchange mailbox.

I right-click the existing John Doe and rename to "John Doe Sr." I also change the full name field.  I do not change first or last.

I right-click John Doe Sr and copy the account permissions to a new account. The new AD account is acme\jdoejr. The new first name is John, and the new last name is Doe, just like his dad, but the full name is different than dad, "John Doe Jr".

At this point I satisfied all of my needs, but I will trigger some artificial intelligence from Microsoft. When I add the mailbox, the Exchange 2010 wizard fails to tell me that my primary SMTP address is jdoejr2@acme.local instead of jdoejr@acme.local.  I start using the OWA account to send test messages.

The test messages reveal this very unattractive primary SMTP address. Okay, okay, okay, this needs to be fixed. I delete the mailbox from Exchange, which also kills the AD object.  Junior is now out of the system, but his mailbox is orphaned.

In my next attempt I  reduce the first name to "J".  Now I don't have to worry about Microsoft artificial intelligence adding an extra '2' to my primary SMTP address.

My new J Doe Jr looks good in AD. I switch to the Exchange Management Console and I attached the orphaned mailbox. The wizard claims success.

Unfortunately when I use jdoejr@acme.local authenticate with OWA I get this message, "The Active Directory resource couldn't be accessed. This may be because the Active Directory object doesn't exist or
the object has become corrupted, or because you don't have the correct permissions."  After 15 minutes there was no change.

I had more important things to do for a few hours. When I returned the AD permissions had somehow propagated correctly and everything was fine. AD is running on the Exchange server and one other DC.

In summary....
Can I turn off the automatic '2' on the SMTP address?
Why did OWA have to wait to get the proper permissions?

Thanks in advance!
-K
0
kengreg
Asked:
kengreg
1 Solution
 
suriyaehnopCommented:
I think the "2" due to the existing of jdoejr@acme.local. You may check the older Joh  Doe, what is the email addressess assign to him (primary/scondary SMTP).

The reason why OWA need wait because Exchange is depending on Active Directory. Normally, Exchange will refresh the cache permission (Active Directory permission) every 2 hours.
0
 
Premkumar YogeswaranAnalyst II - System AdministratorCommented:
As suriyaehnop said, this would happen if any other user having the same smtp address in primary or secondary addresses.

Use any of the below commands to find the user having the smtp address.

Get-Mailbox jdoejr@acme.local

Open in new window


Get-Mailbox –Filter {Emailaddresses –Like "jdoejr@acme.local"} | Select Name, Emailaddresses

Open in new window

0
 
Simon Butler (Sembee)ConsultantCommented:
The Exchange wizard doesn't tell you anything about email addresses. The email address is applied later via the email address policy.
Exchange caches permissions - therefore it can take two hours or more for a change to be fully seen by the internet.
You can't stop the 2 from being applied if the email address clashes. The mistake was setting the same surname - you should have put the Jr bit in there and Exchange would have done the rest.

Simon.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
kengregAuthor Commented:
Suriyaehnop and Premkumar,
I looked for the existence of jdoejr on the father's mailbox.  He was simply jdoe@acme.local.

I'm convinced that Exchange added the 2 based only on first & last, and not because there was a conflicting SMTP address.

My solution was alter the first name. Simon's solution is alter the last name. I think it's one or the other.

I'm still looking around.
-K
0
 
Simon Butler (Sembee)ConsultantCommented:
"I'm convinced that Exchange added the 2 based only on first & last, and not because there was a conflicting SMTP address."

That is what Exchange works on for building the email address. The display name is just that - a display name. Therefore if you put the same first and surname in, then Exchange would treat that as a conflict and add the 2 to the address. That behaviour cannot be changed, other than by ensuring you don't conflict.

Simon.
0
 
kengregAuthor Commented:
Exchange considers the first name and last name fields when looking for conflicts.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now