Domain Naming

Hello - I work for a company that is a consolidation of three other companies. After consolidation, the name changed. The original company's AD domain has all of the network resources, so the other company's AD domains were moved into its domain. Now, though, I need to figure out how to remove the original AD domain name which matched the original company name. When users login, they wrinkle their noses when they see the AD domain name wondering why it has remained.

I've researched a domain rename and that's out of the question. I have Exchange 2013 in a hybrid with O365, System Center, a couple of Forest Trusts, etc. I have setup a UPN suffix for the new AD domain and I can login users with that, but a few questions still remain.

1. How do I prevent users from seeing the NETBIOS name of the original AD domain? I have them login with the UPN of the new AD domain, but they still see the old domain at login.
2. Can I join computers to the new AD domain? I think this would help solve some of those problems. When they login or if they are logging back onto an active session, they see the domain they are authenticating to. I assume that's from the domain the computer has joined.
LVL 33
digitapAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Will SzymkowskiConnect With a Mentor Senior Solution ArchitectCommented:
How do I prevent users from seeing the NETBIOS name of the original AD domain
This cannot be changed unless you rename your domain (which i would not recommend, it will break Exchange)

You can modify the DNS Suffix search order from the network adapter settings or the registry, but this is simply appending the FQDN's you want in order when you are pinging the machine.

Does it really matter what your internal domain is? You could create a new domain > create a forest trust > use ADMT to migrate your AD objects to the new domain etc. You will then also need to migrate the Exchange environment as well a long with all of the mailbox etc.

Seems like a lot of work to have a different internal domain name.

Will.
0
 
digitapAuthor Commented:
It does but it doesn't. The old company is gone and is no longer being referenced. This a Methodist Conference and three prior Methodist Conferences merged to make one. It was a ton of work and there was a strong push to create unity through the new Conference. Folks have been urged to look forward and not back. Users seeing the old domain here and there is a little bothersome. Since I'm new to 2012 R2, I'm not up on many new features. I guess I was hoping there was something I could do to EASILY get rid of the old domain.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Unfortunately not. Usually if there is a consolidation of 3 or more companies into 1 where they want to change the name a new Forest Root domain is required and you will have to do a migration using the ADMT tools. If you could convince them to just ignore the internal domain and the external domain is actually what represents the company and it more important, that would be the best approach.

If not then you will have a lot of work ahead of you migrating the AD Objects.

Will.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
digitapAuthor Commented:
Would Exchange really be the only concern? If Exchange isn't hosting any mailboxes, do you think that makes a difference?
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Exchange is just one of the things I point out because it is an enterprise application which a lot of companies use. There could many more elements of your domain that may have side effects from a domain rename.

Below is an Exchange specific link for side effects that will happen if you rename your domain.
Exchange effects on Domain rename

You are really the only one that knows everything in your environment so i can't contest for other specific custom apps etc.

Will.
0
 
digitapAuthor Commented:
I appreciate Will's feedback concerning this issue. I was hoping for a different answer, but he confirmed my fears. I'll leave my AD domain as is. Users will just have to get over the fact that the name isn't what they are expecting.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.