What I know is:
 
If you disjoin a computer you will get the credentials box asking for credentials to DELETE the computer account.
If you just click OK without giving credentials the computer account is disabled and will remain in the container or OU it resides in
If you give credentials with permissions to delete the computer account the computer account will be deleted
 
Cheers,
Jorge


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Ferguson
Sent: Wednesday, August 17, 2005 21:02
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] Joining computers to a 2K3 domain

I am very perplexed by this behavior, so my hope is that some of the more knowledgeable on this list can shed light.  In our Windows 2K3 functional forest (with a root placeholder domain and two child domains), when a machine is disjoined from the domain (one of the child domains) it is not removed from the OU it occupied in AD.  Its object is set to disabled, but the computer just stays there (even after weeks of sitting to see if maybe replication would clear up the object).  If we then rejoin that computer to the domain, its object is re-enabled and the same SID is given to the object.  This has presented many problems, as you can imagine.  In another job I worked, when the computer was disjoined, it dropped out of AD and then when you rejoined the computer, it dropped into the built-in Computers OU (as I expected).  Is the first behavior I described normal?  If not, what is the remedy to fix this?  I have searched high and low and nobody seems to know what I am talking about. 

 

Any help appreciated.

 

-Doug



This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

Reply via email to