You can use ntdsutil command from command prompt to clean it. I have worked with it several time and there would be no problem. This article about working with ntdsutil for this subject can help you.

 

http://support.microsoft.com/default.aspx?scid=kb;en-us;216498

 

hope this helps

roseta.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Za Vue
Sent: Friday, December 17, 2004 10:29 PM
To: [email protected]
Subject: RE: [ActiveDir] Domain Controller Removed - but it's still there...

 

I meant ADSI.MMC.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Za Vue
Sent: Friday, December 17, 2004 1:54 PM
To: [email protected]
Subject: RE: [ActiveDir] Domain Controller Removed - but it's still there...

Residue of old server still exist in AD. Use ADSI.MSC to clean it up.

 

Z.V.

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John R. Tomawski
Sent: Friday, December 17, 2004 1:46 PM
To: [email protected]
Subject: [ActiveDir] Domain Controller Removed - but it's still there...

Here’s what hopefully is a simple question.

 

I am receiving errors in the system log reporting replication failures from a domain controller. I realize this is probably a question for the AD lists, but I’ll try anyways.

 

“The File Replication Service is having trouble enabling replication from Backup-DC to Primary-DC for c:\winnt\sysvol\domain using the DNS name Backup-DC.DOMAIN.com. FRS will keep retrying.”

 

Note, the names have been substituted.

 

My problem is, this Backup-DC was removed before I started working at that job site (It’s not physically there anymore), so there’s no way to “join” it and “unjoin” it. Is there another way to remove it?

 

Thanks,

 

John R. Tomawski
Network Administrator

Reply via email to