Title: Removing ADAM from configuration set
Define "it doesn't work".
 
Also go chat with Snyder, he had a fun little tool called Whack-A-DC that was used for the lifeboats that you may be able to modify for this.
 
But yes, the ADAM tools aren't all polished yet, and may not be polished later. The idea behind ADAM was providing an LDAP directory for developers, not for Admins, or at least that is my opinion on the matter.
 
  joe
 
--
O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm 
 
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernier, Brandon (.)
Sent: Wednesday, May 17, 2006 5:20 PM
To: [email protected]
Subject: [ActiveDir] Removing ADAM from configuration set


I'm currently blowing away the server object and nTDSDSA object I wish to separate from CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,CN=GUID. Is there a better way to knock it out of the configuration set? I tried using DSMGMT.exe and treating it as a Decommed/Dead server and cleaning up Metadata, but it doesn't work (the separated instance is offline). Some of these ADAM tools need some polishing up IMO.

The reason I'm breaking it out is so when we do schema extensions if shit hits the fan we can uninstall ADAM on the other boxes and rejoin to this guy with minimal effort.

-Brandon

Reply via email to