It's weird... I had tried booting from a Windows CD to do a repair, but setup said it couldn't recognize the C: partition and wanted to format it. This is strange for two reasons:
1. Setup could recognize the D: partition just fine (and both C: and D: are partitions in the same hardware RAID 5 array). 2. The C: partition can't be totally FUBAR, because the system will boot off of it and Windows will load about 75% before getting the blue screen. -----Original Message----- From: Ziots, Edward [mailto:ezi...@lifespan.org] Sent: Wednesday, January 07, 2009 9:52 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall Usually the C24 Stop error is registry corruption, I have seen this a few times, if you have a backup of your Software Hive you can problem boot to a new partition and replace the old one, with the backup and point back to affected system and boot successful. If you don't want to go through that pain. Do a standard build, don't add to domain and then restore from tape accordingly. Z Edward E. Ziots Network Engineer Lifespan Organization Email: ezi...@lifespan.org Phone: 401-639-3505 MCSE, MCP+I, ME, CCA, Security +, Network + -----Original Message----- From: Christopher Bodnar [mailto:christopher_bod...@glic.com] Sent: Wednesday, January 07, 2009 9:43 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall I have done this many times with no ill affects. Here is the MS documentation on the process: http://support.microsoft.com/kb/216498 I personally have never had an issue with using this procedure and using the same name. YMMV Chris Bodnar, MCSE Sr. Systems Engineer Distributed Systems Service Delivery - Intel Services Guardian Life Insurance Company of America Email: christopher_bod...@glic.com Phone: 610-807-6459 Fax: 610-807-6003 -----Original Message----- From: john.hornbuc...@taylor.k12.fl.us [mailto:john.hornbuc...@taylor.k12.fl.us] 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/> ~ ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. 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/> ~