Sorry, I wasn't paying attention. I would only do this for member servers and workstations. Messing with a DC is a whole 'nuther ball game.
I'd go with Chris's suggestion and follow the MS article. Thanks, Jake Gardner TTC Network Administrator Ext. 246 -----Original Message----- From: John Hornbuckle [mailto:[email protected]] Sent: Wednesday, January 07, 2009 9:56 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall This sounds easiest. But can anyone confirm if it actually works? -----Original Message----- From: Jake Gardner [mailto:[email protected]] Sent: Wednesday, January 07, 2009 9:37 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall I believe you can use the Network ID instead of Join Domain after your install and select/choose the old name from AD Thanks, Jake Gardner TTC Network Administrator Ext. 246 -----Original Message----- From: John Hornbuckle [mailto:[email protected]] Sent: Wednesday, January 07, 2009 9:18 AM To: NT System Admin Issues Subject: Server OS Reinstall I've got a server (Server 2003 R2) that conked out on me over the Christmas holidays. I'm not quite sure what went wrong--the hardware seems to be okay. But there was some sort of corruption in the RAID array and the OS gives a stop 0x00000024 every time it goes to boot. A fresh OS install won't be too painful, because this server was only a DC/DHCP/DNS server. But my question is this... When I reinstall, should I give the server the same name it had before? Or will that confuse Active Directory? And if I give it a different name, how do I remove all references to the old server name from AD? Just wondering what best practices are. Amazingly, I've never had to do this before in my years as a sysadmin. Just lucky, I guess! John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. ******************************************************************* ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
