Hey everyone, I'm in a bit of a bind. I've been tasked with changing our local Windows Domain name from XXXXXXdev.internal to XXXsupport.internal. Everything else will stay the same, and I'm just focusing on updating the 'friendly name'. I'm getting mixed advice online though. Can I simply change the name on the Domain Controllers (the IPs will remain unchanged), or is there a lot more involved in this process? I want to avoid causing any disruptions, so any advice would be greatly appreciated!
6 Answers
We did a similar switch a while back, and while it was a pain, it wasn't unmanageable. Just keep in mind you’ll need to reboot your clients and check all configurations with the FQDN of your remote services—it can be a bit annoying but doable!
Honestly, whoever suggested this must not be thinking straight. You're just creating unnecessary work and risks. It sounds like there are more pressing IT issues that need attention. Push back on this if you can!
I totally hear you. Sometimes decisions get made without considering the actual impact. I might bring it up, but the pressure is real in this environment.
If you're determined to rename the AD domain, I’d suggest switching to a routable domain rather than keeping a .internal or .local suffix. If you have Exchange Server, think twice about this change—it can complicate things significantly. Instead, consider registering a new UPN suffix and managing FQDN aliases. It'll make life easier in the long run!
I appreciate the suggestion! Switching to a routable domain isn’t feasible for us right now. I’ll definitely look into registering a UPN suffix though.
If I were you, I'd recommend creating a new domain and migrating users and resources instead. Renaming a domain can be quite the hassle and it's often safer to just set up a new one. Test it in a controlled environment first if you can! Good luck!
Thanks for the heads up! I’ll definitely consider setting up a test environment before making any big changes.
Renaming a domain usually leads to a lot of headaches, and often it's simpler to start a new domain and migrate everything. Depending on your organization’s size, this can take a lot of planning and coordination. Be prepared for a big undertaking.
That sounds like a big deal. We have around 420 devices, so I get that it can be challenging. I’d rather avoid the drama if possible!
Seriously, just don't do it. It's more trouble than it's worth. Focus on proper maintenance of the current setup instead.
That sounds hopeful! We use remote tools like SCCM and PowerShell, so rebooting them all shouldn’t be too big of an issue as long as they come back up!