Question

Locked

Renaming a domain controller and domain?

By lionheart1982 ·
We recently had an outsourced IT provider configure us a new domain controller to replace an aging Windows 2000 Server box. The new DC runs Server 2003. However, they didn't give it the name I specified, nor did they use the domain name I asked for.

We spent the better part of the day reconnecting each workstation to the domain, and renaming profiles so everyone's desktop was the same. However, I really want to standardize on my own naming standard for the server and domain... the desktops I would like to rename as well (they all use factory standard names so its something like COMPAQ-343143B) but it will probably break a lot of things so I can ignore it.

Is there a way to rename the server and the domain without having to reconfigure every desktop again?

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Rename domain

by Nimmo In reply to Renaming a domain control ...

If you rename either your domain controller or domain your workstations will need to be re-joined to the network.

If you really want to do this you will neeed to make sure you know what services you have running otherwise you will get a **** of alot of problems.

http://www.petri.co.il/windows_2003_domain_controller_rename.htm

http://technet.microsoft.com/en-us/windowsserver/bb405948.aspx

Collapse -

Damn

by lionheart1982 In reply to Rename domain

Okay, I won't worry about it then. It's not worth rejoining all my workstations. I just wish that our provider had followed my instructions for the domain name, but I guess I can live with it.

Collapse -

Well there might be a way but it's a pain.

by bart777 In reply to Damn

You COULD take another box and make it a DC in you current domain.
Transfer all of the FSMO roles and give it a little while to settle. Once the new server is solid you demote the original box, remove it from the domain and rename it.

Next you create a new domain on the original server and configure it as you like\need.

Then you use the ADMT tool to migrate the users and computer to the new domain.

The process may not work on 100% of the computers but it will get the bulk of them. There is always at least 1 problem child machine around.

So you CAN get to where you want to be, it's just going to take you some time. Set aside a weekend for the move and you'll be fine.

Once you've done all of this you go find that consultant and slap the $&%* out of them for not listening to the customers request.

Best of luck.

Back to Networks Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums