> We have 8 DC running DNS. And for this tread, i'm trying to gather info on
> the DC that is having hard drive issue. I don't understand how i can get into
[quoted text clipped - 58 lines]
>>> Thanks in Advance,
>>> Donna

Signature
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
> If all you want it to demote it gracefully, don't bother. Force a demotion
> and do a cleanup.
Those articles will show you how to do a clean up. You may be in a position
where trying to demote it gracefully is not an option and tinkering around
with trying to gracefully demote it might be doing more harm to your AD
domain than it's worth.
hth
DDS
>> We have 8 DC running DNS. And for this tread, i'm trying to gather info
>> on the DC that is having hard drive issue. I don't understand how i can
[quoted text clipped - 67 lines]
> If all you want it to demote it gracefully, don't bother. Force a demotion
> and do a cleanup.
DonnaJ@abbe-lib.org - 31 Jul 2008 03:21 GMT
I would like keep it on the network as as file server, with DHCP and DNS
running on it.
Anyway, I ordered two new hard drives today. I'm going to try to replace the
drives and see if that will take care of it or at lease get it up. I'm going
to phyically remove it from the network while I replace them. If it goes bad.
I'll keep it off till I get it fixed and force a demotion. Any advice on
replacing the drives? They are hot swap. So I should be able to just replace
and rebuild, but since it appears I've got trouble with two of them, I'm not
sure. Does it matter which one I try first? The DC is at a remote location,
so I have only trouble shooted it from a distance.
Thx,
Donna
> > If all you want it to demote it gracefully, don't bother. Force a demotion
> > and do a cleanup.
[quoted text clipped - 78 lines]
> > If all you want it to demote it gracefully, don't bother. Force a demotion
> > and do a cleanup.