RE: Server OS Reinstall
I never reuse a DC name, even if I removed it gracefully. That may be a bit overkill, but I would strongly advise against reusing a name on a failed DC. You can clean it out of AD, and you will need to but I still wouldn't reuse the name. I have always done a manual removal with the info in this article: http://www.petri.co.il/delete_failed_dcs_from_ad.htm -Original Message- From: John Hornbuckle [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 0x0024 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/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
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: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 0x0024 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/ ~
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 0x0024 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/ ~
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 0x0024 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/ ~
RE: Server OS Reinstall
This looks promising. Although I'm worried about the warning: The administrator must also make sure that replication has occurred since the demotion before manually removing the NTDS Settings object for any server. Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality. There was no demotion, though, since the server went down unexpectedly. Does that matter? You just do the 20 steps listed under ntdsutil? -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 0x0024 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/ ~
RE: Server OS Reinstall
This sounds easiest. But can anyone confirm if it actually works? -Original Message- From: Jake Gardner [mailto:jgard...@ttcdas.com] 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: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 0x0024 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/ ~
RE: Server OS Reinstall
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 0x0024 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/ ~
RE: Server OS Reinstall
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:john.hornbuc...@taylor.k12.fl.us] 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:jgard...@ttcdas.com] 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: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 0x0024 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/ ~
RE: Server OS Reinstall
Hey Z what is this tape thing you speak of??? TVK -Original Message- From: Ziots, Edward [mailto:ezi...@lifespan.org] Sent: Wednesday, January 07, 2009 8: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 0x0024 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/ ~
RE: Server OS Reinstall
I reuse DC names every time I do HW refresh and have renamed newly promoted DC's back to the name of the one that was removed when I had to run a site in parallel during HW refresh. The thing you need to insure is that the metadata is cleaned up no matter and said cleanup is replicated whether you are doing it forcefully or gracefully, KB216498 explains the process in detail. You also need to take into consideration other services that may have been running on the failed DC, FSMO roles etc. http://support.microsoft.com/kb/216498/ -Original Message- From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Wednesday, January 07, 2009 6:31 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall I never reuse a DC name, even if I removed it gracefully. That may be a bit overkill, but I would strongly advise against reusing a name on a failed DC. You can clean it out of AD, and you will need to but I still wouldn't reuse the name. I have always done a manual removal with the info in this article: http://www.petri.co.il/delete_failed_dcs_from_ad.htm -Original Message- From: John Hornbuckle [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 0x0024 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/ ~ ~ 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/ ~
RE: Server OS Reinstall
Good point... This server was also a GC. Not sure if that affects the cleanup process in any way... -Original Message- From: Free, Bob [mailto:r...@pge.com] Sent: Wednesday, January 07, 2009 10:40 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall I reuse DC names every time I do HW refresh and have renamed newly promoted DC's back to the name of the one that was removed when I had to run a site in parallel during HW refresh. The thing you need to insure is that the metadata is cleaned up no matter and said cleanup is replicated whether you are doing it forcefully or gracefully, KB216498 explains the process in detail. You also need to take into consideration other services that may have been running on the failed DC, FSMO roles etc. http://support.microsoft.com/kb/216498/ -Original Message- From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Wednesday, January 07, 2009 6:31 AM To: NT System Admin Issues Subject: RE: Server OS Reinstall I never reuse a DC name, even if I removed it gracefully. That may be a bit overkill, but I would strongly advise against reusing a name on a failed DC. You can clean it out of AD, and you will need to but I still wouldn't reuse the name. I have always done a manual removal with the info in this article: http://www.petri.co.il/delete_failed_dcs_from_ad.htm -Original Message- From: John Hornbuckle [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 0x0024 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/ ~ ~ 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/ ~
RE: Server OS Reinstall
Have you tried a repair from the cd?? -Original Message- From: John Hornbuckle [mailto:john.hornbuc...@taylor.k12.fl.us] Sent: Wednesday, January 07, 2009 10: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 0x0024 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/ ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/ ~
