Renaming Server
Demote the old server as a DC using dcpromo. Remove the old server from the domain and if possible, disable it NIC. leave it running as fail back. build your new server, add it to the domain and ensue DNS is updated. Ensure it has the same printer and files shares as your old server. run dcpromo to enable it as a backup DC just like your old one. Once you are happy everything is running smoothly, retire the old server MCITP: Enterprise Administrator Windows Server 2008 MCTS: Windows 7, Active Directory, Network Infrastructure, Applications Infrastructure, Exchange 2007 ITIL V3 Certified
November 25th, 2011 7:27am

Hello, You can proceed like that: Add a new DC and make it a GC and DNS server Transfer FSMO roles to the new DC Make sure that AD replication was made correctly using dcdiag command and demote the old DC Note that it is recommended to have at least two DC / DNS / GC servers per domain you have. Once you followed what I mentioned, rename the DC and change its IP address like you want. To rename a DC: http://technet.microsoft.com/en-us/library/cc782761(WS.10).aspx For printers change, you can make the new DC a printer server. If you want to apply changes then you can use group policies. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2011 10:00am

thanks
December 25th, 2011 6:42am

Thanks again, this all makes sense.
Free Windows Admin Tool Kit Click here and download it now
December 25th, 2011 7:47am

Re reading MrX pointer to a MS article about renaming a DC. I dont think this is the right article for me. This article is for renaming a server to a different name. I want to build a new computer and name it the previous old name. eg the command netdom computername CurrentComputerName/add:NewComputerName seems to indicate a different name. Am I wrong? Or do I .. Make new computer say called new1 then use the command in the following way. to rename the new1 server to the old server name. netdom computername New1/add:Oldprintserver Im not sure?? And I asume that I would demote the old server first before renaming the new server the old name. thanks
December 25th, 2011 8:59am

If this is simply a member server, then keeping the same name will enable clients to use existing mapped drives for example, and shared printers. You must make sure the share names are the same on your new server.([string](0..9|%{[char][int](32+("39826578846355658268").substring(($_*2),2))})).replace(' ','')
Free Windows Admin Tool Kit Click here and download it now
December 25th, 2011 12:50pm

Hello, Since it's a DC, you will need to demote it and remove it from the domain before decommissioning it as several people already mentioned. As Big Teddy mentioned, printers and file shares will work as long as the UNC paths are the same. Check your printers and file shares to see if they are conneting back to th server using IP addresses or Netbios Names. If using IP addresses, it does not matter what you name the server since the shares and printers will connect based on the server's IP address. If you are using NetBios then naming the server the same and keeping the print and file shares path identical will insure conenctivity without having to change everything around.Miguel Fra / Falcon IT Services Computer & Network Support, Miami, FL Visit our Knowledgebase and Support Sharepoint Site
December 25th, 2011 1:54pm

I have a server that was windows NT. Then it was upgraded to 2003. It is a printserver, backup domain controller, file server. Its very old hardware and slow now. Im wondering if I make a new server and call it the same name, is that going to cause any problems. In particular Im wondering if the printers that are connected to it by the old name will they connect to the new server if it has the same name. Im interested in doing this so I dont have to go around and reinstall all the computers to the new print server/printers. (this is for a windows 2003 domain)
Free Windows Admin Tool Kit Click here and download it now
December 25th, 2011 9:25pm

Hi, if you can take a image of the current server and restore into the new server this will help you to reduce the impact.
December 25th, 2011 10:58pm

Demote the old server as a DC using dcpromo. Remove the old server from the domain and if possible, disable it NIC. leave it running as fail back. build your new server, add it to the domain and ensue DNS is updated. Ensure it has the same printer and files shares as your old server. run dcpromo to enable it as a backup DC just like your old one. Once you are happy everything is running smoothly, retire the old server MCITP: Enterprise Administrator Windows Server 2008 MCTS: Windows 7, Active Directory, Network Infrastructure, Applications Infrastructure, Exchange 2007 ITIL V3 Certified
Free Windows Admin Tool Kit Click here and download it now
December 25th, 2011 11:18pm

Hello, You can proceed like that: Add a new DC and make it a GC and DNS server Transfer FSMO roles to the new DC Make sure that AD replication was made correctly using dcdiag command and demote the old DC Note that it is recommended to have at least two DC / DNS / GC servers per domain you have. Once you followed what I mentioned, rename the DC and change its IP address like you want. To rename a DC: http://technet.microsoft.com/en-us/library/cc782761(WS.10).aspx For printers change, you can make the new DC a printer server. If you want to apply changes then you can use group policies. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer
December 26th, 2011 1:51am

Thanks all for the helpfull advice and processes. It all helps. So the simple answer is yes i can name it the same thing. To comment on the first poster who said to image the machine. The reason I dont want to do that is because basically this is an older install of NT to Win2003, frankly Im sure there are all sorts of unneccesary files and programs and orphaned things on it and I would like to start with a fresh machine and install of just 2003. Thanks a lot.
Free Windows Admin Tool Kit Click here and download it now
December 26th, 2011 6:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics