mirojr Posted March 1, 2010 Posted March 1, 2010 Could I, Should I? Rename a domain controller? I just thought that it would save changing peoples home paths to a new DC and maybe other things.
FN-GM Posted March 1, 2010 Posted March 1, 2010 You can on 2008 i think. Do something better. In your DNS create an A record call it the name of your old server and then point it to the IP of the new one. So when a client runs to the name of your old one server it will connect to your new instead. If there are some records with the old server name in there bin them first. Z
powdarrmonkey Posted March 1, 2010 Posted March 1, 2010 Do something better. In your DNS create an A record call it the name of your old server and then point it to the IP of the new one. So when a client runs to the name of your old one server it will connect to your new instead. If there are some records with the old server name in there bin them first. This causes no end of problems with SMB and WINS.
mrmontymick Posted March 1, 2010 Posted March 1, 2010 This causes no end of problems with SMB and WINS. Funny enough I wondered if this might cause issues - possible with SPN's in the Active Directory as well. @OP - You can rename a domain controller using netdom though: Rename a domain controller: Active Directory
pete Posted March 1, 2010 Posted March 1, 2010 This causes no end of problems with SMB and WINS. You can make it work if you disable strict name checking, but I wouldn't put cnames for DCs on the "list of good ideas". Connecting to SMB share on a Windows 2000-based computer or a Windows Server 2003-based computer may not work with an alias name
cookie_monster Posted March 1, 2010 Posted March 1, 2010 Could I, Should I? Rename a domain controller? I just thought that it would save changing peoples home paths to a new DC and maybe other things. Are you replacing a server? Last time I needed to do something similar I demoted the DC and made it a fileserver I then replaced the DC with a new one. It seemed easier that renaming which can cause massive issues. If you mapped drives with logon scripts it should be very easy to change the paths or you can just select multiple users in AD and change it that way with the %username% variable. Assuming it's their home folder that you're changing.
srochford Posted March 1, 2010 Posted March 1, 2010 You can rename a DC - netdom is an option (but I've never used it with a DC) Assuming you've got more than one DC you can do it by moving FSMO roles to another DC, dcpromoing it down to a standalone server, renaming it and then dcpromoing it back up (leave about 15 minutes between each of the steps to allow the other DCs to catch up) What you might want to do is look at DFS Although the "D" stands for "distributed" you can use it on 1 server. This allows you to have home directories as \\\ rather than \\\ The next time you change server you just go into your DFS console, change the to be homed on the new server and magic happens :-)
mirojr Posted March 2, 2010 Author Posted March 2, 2010 Hi, For some autistic reason i would like my primary dc named dc1. I am running this in a lab environment but wanted to see how it went for wen/if i do it for real. I have tried netdom but get this: unable to add lab-server-dc1 as an alternate name for the computer The RPC server is unavailable (RPC is running in services though) I recently demoted dc1 after swapping roles and global catalogue. Seems to have worked after a few weird problems, like not being able to log in and not being able to demote.... but a few reboots later it seems to work. cant wait to upgrade my dc to server 2008 r2 and go through the process for real
mirojr Posted March 2, 2010 Author Posted March 2, 2010 What you might want to do is look at DFS Although the "D" stands for "distributed" you can use it on 1 server. This allows you to have home directories as \\\ rather than \\\ The next time you change server you just go into your DFS console, change the to be homed on the new server and magic happens :-) This sounds good. Hope it works on qnap 439
chazzy2501 Posted March 2, 2010 Posted March 2, 2010 To do this all you have todo is raise your domain functionality level to 2003 and go ahead. Remember that no 2000 or older clients would then be able to use the domain!
mb2k01 Posted March 2, 2010 Posted March 2, 2010 If it is just changing profile paths and other user stuff, don't do it! Far too messy. Use ADModify to make bulk changes to user properties. More info: Introduction to ADModify.net To download: ADModify.NET
sted Posted March 13, 2010 Posted March 13, 2010 To do this all you have todo is raise your domain functionality level to 2003 and go ahead. Remember that no 2000 or older clients would then be able to use the domain! yes they can you just cant have any 2000 dcs workstations are fine but yes you need 2003 functional domain level to allow renaming of dcs
IanT Posted March 13, 2010 Posted March 13, 2010 I've renamed a 2008 DC and had no problems, just check there are no references to the old name
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now