Active Sync/naming convention

Hi Experts,

We are in the process of implementing single email address for all of our head office and branch office users, at present branch office users are using different email address and domain but we are planning to give branch office users with the head office email address, so that branch office user can use both internal and external email address as instead of

We are not migrating user mailbox from to not even consolidating active directory at this moment, rather planning to set forwarder and sharing the SMTP name space.

Could you please assist to clarify the followings:
1.      In terms of naming convention, management advised to keep firstname.lastname in this case, if there are potential email address conflicts, what is the standard that I can follow to avoid the e-mail address conflicts?
For example user: John Smith ( but if another user exists with the same name (john Smith) what would be the standard, please advice.

2.      How are Blackberries (and BES servers or other mobile systems) affected by the change to the email address?

At present branch office BES users are using profile created in the BES server. Since we are not changing AD authentication in that case do we still need to create new profile for them?

 According to my understanding, branch office BES users are getting authentication from their AD and with the new implementation, we are just sharing the SMTP name space for them, yes branch office users will have new SMTP address but their AD account is not changing at all for that intend to know if there are any potential impact to the BES/Active sync clients.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason CrawfordTransport NinjaCommented:
You'll want to create a new UPN suffix in Active Directory that matches, and assign that suffix to each user's UPN.  Matching the UPN to the user's email address allows them to authenticate with a username they already know (their email) instead of domain\alias or alias@domain.local.  You're basically replacing domain.local with in Active Directory:

I've never used the script contained in the URL above to add the suffix to user's once it's been added.  I wrote my own:

Get-ADUser -Filter * -SearchBase 'OU=Users,DC=headoffice,DC=local' | Select-Object samaccountname | % {Set-ADUser $_.samaccountname -UserPrincipalName "$($_.SamAccountName)"}

Open in new window

You'll want to replace the OU and suffix at the end with your own.  If you find yourself in a situation where more than one user is assigned the (for instance) just add in a middle initial or some other unique character.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ipsec600Author Commented:
Excellent, Thank you Keyser Soze, and apology for replying late since I was away..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.