Computing.Net > Forums > Windows 2000 > Removing NT DC from AD

Removing NT DC from AD

Reply to Message Icon

Original Message
Name: Sam
Date: June 10, 2002 at 08:26:46 Pacific
Subject: Removing NT DC from AD
Comment:

I am trying to remove an old NT 4.0 PDC from active directory. When I try to use Ntdsutil the server does not appear when I list servers. It only lists the the 2 new windows 2000 domain controllers. I can probaly live with it showing up there if it won't cause problems when I move to native mode. Any ideas would be appreciated.



Report Offensive Message For Removal


Response Number 1
Name: Chaz
Date: June 10, 2002 at 10:31:19 Pacific
Subject: Removing NT DC from AD
Reply: (edit)

If you dont need the NT DC then going to native mode will not affect anything. Native mode, among other things, disables the PDC emulator.

As far as the computer object in AD, Look in AD users and computers under the Domain Controller container and delete the object there.

-Chaz


Report Offensive Follow Up For Removal

Response Number 2
Name: Curt R
Date: June 10, 2002 at 11:59:30 Pacific
Subject: Removing NT DC from AD
Reply: (edit)

I hate to argue with you Chaz but it's my understanding that the PDC emulation FSMO role is not disabled in a native mode 2000 domain.

Here's a quick bit of info I just found:

http://www.microsoft.com/windows2000/techinfo/reskit/en/distrib/dsbl_fsm_WESD.htm

I have more available in my 2000 Server Resource Kit but I'm not about to start scanning the book when the same info is available on the MS online Res Kit. If you want to learn more on this and other FSMO roles, I recommend going there and reading it.

The PDC emulation FSMO also provides other services like time sync....so disabling it could be problematic.

As to your problem Sam. You should never have an NT PDC running in a 2000 domain. Only BDC's, thus the PDC emulation role. Trying to run a PDC will cause problems and you won't get proper replication from the 2000 DC's and your PDC. If you've physically removed the server and it's "ghost" (for lack of a better term) is still appearing in AD, well, good luck getting rid of it. In fact, if you figure out a way to do this, please let me know as I've encountered this problem on several occasions and have yet to find a resolution. This problem affects domains created then removed as well as servers, clients and other resources listed in the GC in AD. While the ghost shouldn't affect anything adversely (in my experience so far, there have been no adverse side effects from ghosts) it can be annoying and lead to users asking why they can no longer access the now physically removed resource.


Report Offensive Follow Up For Removal

Response Number 3
Name: Chaz
Date: June 11, 2002 at 04:32:11 Pacific
Subject: Removing NT DC from AD
Reply: (edit)

Curt,
A forum is an exchange of ideas for the edification of all. Thanks for the correction.

-Chaz


Report Offensive Follow Up For Removal

Response Number 4
Name: Curt R
Date: June 11, 2002 at 05:38:21 Pacific
Subject: Removing NT DC from AD
Reply: (edit)

I don't know it all, not by a long shot, and the biggest reason I hang in forums is to learn...and I do a lot of that...always a pleasure to help out. :)


Report Offensive Follow Up For Removal

Response Number 5
Name: Sam
Date: June 11, 2002 at 14:48:52 Pacific
Subject: Removing NT DC from AD
Reply: (edit)

Thanks for you're help guys.


Report Offensive Follow Up For Removal







Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Removing NT DC from AD

Comments:

 


  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 
Data Recovery Software