Back online long enough to get demoted http://www.ideaspace.net/users/wkearney/archives/entries/000482.html This has been the Summer from Hell for machines around here. From drive failures to electric brownouts, it's been rough.... wkearney 2003-09-15T14:36:03-05:00 http://www.ideaspace.net/users/wkearney/archives/entries/000482.html en-us Geek Microsoft This has been the Summer from Hell for machines around here. From drive failures to electric brownouts, it's been rough.... 2003-09-15T14:36:03-05:00 This has been the Summer from Hell for machines around here. From drive failures to electric brownouts, it's been rough. One box had to come offline for more than a month. Being it was a Windows Active Directory controller made for some interesting problems. Fortunately easy to solve.

]]> This has been the Summer from Hell for machines around here. From drive failures to electric brownouts, it's been rough.... The machine in question blew out it's power supply. I'm sure Pepco's crappy level of service around here is to blame. It would boot for a while and then just shut down. It wasn't even reliable enough to perform a proper disconnect from the domain. The remaining parts of the network survived just fine. That was just a matter of telling one of the other domain controllers to seize the FSMO roles. But when I brough the old machine back to life it didn't want to play along. The current machines had gotten themselves far ahead in their replication and didn't want to play nice with the old box.

All I needed to do was run dcpromo to demote the box. But it threw an error message about not being able to logon to the existing domain. That and a netdom /query fsmo showed it to be still using the old (pre failure) domain roles.

After the usual go-rounds searching within Technet, I stumbled across a message indicating the use of Directory Recovery safe mode. So I rebooted the pesky machine, pressed F8 and started it up into that mode. A quick set of ntdsutil commands, a reboot and voila, it's back online.

Long enough to demote it from being a domain controller, of course. I only needed to rejoin so that I could properly remove it from the domain.

There's some deep mojo about machines and their particpation in the Active Directory that you dare not screw around with without exercising a lot of caution.

It's been my experience that it 'doing it the right way' instead of just whacking it out of the AD is important. May the Lord have mercy on your soul if you ever try manually editing the schema... It's not for the faint of heart.

Now to scrounge up my RedHat 9 CDs and take a crack at getting linux installed on it...

]]> 482 481 483