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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
If not then you will have a lot of work ahead of you migrating the AD Objects.
Will.
ASKER
Would Exchange really be the only concern? If Exchange isn't hosting any mailboxes, do you think that makes a difference?
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.
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.
ASKER
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.
ASKER