I just did your Option 1 a couple of weeks ago for a customer when I had to rebuild both of their unstable DCs. Option 1 works. I did the most unstable DC first which was the one that had the 5 FSMO roles.
Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.com > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Monday, September 19, 2011 11:42 AM > To: NT System Admin Issues > Subject: RE: 2008 DC problem - uh oh > > That's the direction we're leaning. Your reasons why? > > Original Message: > ----------------- > From: Brian Desmond [email protected] > Date: Mon, 19 Sep 2011 16:40:12 +0000 > To: [email protected] > Subject: RE: 2008 DC problem - uh oh > > > Please use option 1. > > Thanks, > Brian Desmond > [email protected] > > w - 312.625.1438 | c - 312.731.3132 > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Monday, September 19, 2011 11:24 AM > To: NT System Admin Issues > Subject: 2008 DC problem - uh oh > > > > Have a situation where my main 2008 DC is no longer working properly. It's > not processing logon requests anymore and is really hosed. I have several > other 2008 DCs that are operating fine still. I am considering two options: > > 1. Boot into AD Restore Mode, and run DCPROMO /forceremoval. Then > from > another 2008 DC, delete that computer object, seize FMSO roles, clean up > DNS, etc. Then bring the demoted DC back into AD using DCPROMO. > > 2. Boot into AD Restore Mode and restore the system state backup from > Backup Exec from Friday night. (will the server sync up with the changes > in AD since Friday night on the other DCs properly?) > > Any option seem preferable to you? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
