2003 R2 Hangs on "Securing RemoteRegistry" during demotion

[fxlite]

A server we're trying to demote is hanging on the Securing RemoteRegistry part of dcpromo.

 

A new 2012 R2 server was set up, all replicated fine, FSMO roles transferred successfully and all logs seemed fine.

 

Any ideas?

[3s-gtech]

How long has it been left trying for? Is it still running any other roles? If it won't demote properly, you can always nuke it and clean up AD so long as it's no longer needed at all.

[fxlite]

It's been stuck on the RemoteRegistry bit for around 40 minutes...nothing seems to be happening in task manager.

 

If we decide to "nuke it" (what would this involve?) wouldn't it still be picked up in AD somewhere?

 

Thanks.

[3s-gtech]

I'd give it much longer than 40 minutes, good couple of hours at least. May be working through the demotion process.

 

Yes, it'd be picked up in AD but new versions of Windows Server have much better and easier tools for cleaning up old DC entries - even right clicking on a DC and selecting Delete will remove most references automatically. You'll still need to check DNS etc, but nothing too tricky.

[fxlite]

I'd give it much longer than 40 minutes, good couple of hours at least. May be working through the demotion process. Yes, it'd be picked up in AD but new versions of Windows Server have much better and easier tools for cleaning up old DC entries - even right clicking on a DC and selecting Delete will remove most references automatically. You'll still need to check DNS etc, but nothing too tricky.

Thanks for your help - turns out you were completely right and I was being too impatient...demoted gracefully in the end (did take a good 1.5 hours though). I should really show these 8 year old servers some sympathy