Go Premium for a chance to win a PS4. Enter to Win

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

How can I integrate a 2nd domain name to Active Directory and Exchange?

So I have a client that has their active directory domain name (A-Example.com) for their organization. They acquired the new domain name (Z-Example.com) that they want to integrate into their existing AD infrastructure. They don't mind using  (A-Example.com) for a while as user login. They want to be able to receive e-mail with either (tom@A-Example.com or tom@Z-Example.com) domain but send e-mail with the new domain  (tom@Z-Example.com).

The reasoning behind this is because  A-Example.com used to be the company and the brand now the company wants to differentiate itself (as Z-Example.com) from the brand (A-Example.com) and maybe add other brands down the road.

What would be the easier and more cost effective way of achieving the objectives above.
  • 3
  • 2
2 Solutions
Cliff GaliherCommented:
There is a big difference between an AD domain and an email domain. You cannot add additional domain names to AD. If the acquired company already has an AD domain, all you can do is create a trust and/or move accounts onto a single domain.

But for email purposes, exchange has long supported multiple domains. Adding an email domain is thoroughly documented on technet for each version of exchange, and the default send  domain address is also easily changeable. There is no correlation whatsoever between an email domain and an AD domain.

You also mentioned, in passing, logons. The namespace a user logs into is also customizable as an AD property and is also not inherently tied to the AD domain name, although the two are often the same by conventjon and convenience. Again, changing this is documented on TechNet.
As Cliff mentioned, adding the new domain to your e-mail server is well-documented, and relatively easy.

For the Windows domain, Microsoft Windows Server 2012 supports renaming an existing Active Directory domain, using the command "RenDom".  It's a relatively simple procedure, but I strongly recommend you read up on the details before making the change.

MS links:

Here are a few articles on the procedure:

Frederick, MD
Cliff GaliherCommented:
Rendom cannot be used in an exchange environment. As the question is asked, this is an exchange environment, making rendom not applicable.
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Cliff GaliherCommented:
I should say exchange 2010/2013. There was a procedure for 2003/2007.
While Exchange does not support renaming the domain, the (laborious) procedure of exporting all mailboxes, uninstalling Exchange, renaming the domain, and then reinstalling Exchange and re-importing the mailboxes is an accepted practice.

Many (possibly most) admins hold the opinion that it's easier to standup a new domain in parallel and use ADMT to migrate the users over.  However, either solution is viable.
ekitechAuthor Commented:
I needed to present options and you both gave me one.


Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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