Title: Locate and/or Remove Duplicate Computer Accounts in a W2K AD Enterprise.
A duplicate computer name in the same domain would result in a duped samaccountname attributes as well as duped SPN's. You should be seeing events in the error log that could help narrow that down.
 
I would be concerned how these dupes are being created.
 
If you get errors in the event log, then you can search for those specific machines pretty quickly and easily. If not, then you will have to use a script like what Jonathan has provided to find them. But again, this is a pretty big deal to be getting something like that.
 
  joe


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miller Carol L Contr DYN/ITS
Sent: Friday, March 11, 2005 12:20 PM
To: '[email protected]'
Subject: RE: [ActiveDir] Locate and/or Remove Duplicate Computer Accounts in a W2K AD Ente rprise.

No, I am finding duplicate "Computer Names" located in different OUs within our Domain.  I am trying to identify them, and after I have created a list of the duplicates, I want to confirm which of the "Computer Accounts" are Active/Current, and then remove the Unused/Duplicates to clean up our Active Directory domain.

 

Thanks!!!

 

Carol....

::::::::::::::::::::::::::::::::::::::::::
//SIGNED//
Mr. Carol L. Miller, MCP, Contractor
Vance Network Administrator
Analyst, System Administrator
DYN/ITS
Vance Support Division
DynCorp - A CSC Company
Vance AFB, OK
DSN: 448-7143, Com: (580) 213-7143
E-Mail: [EMAIL PROTECTED]
https://www.vance.af.mil/

 

********************************************************************************
                           Official Disclaimer Notice
********************************************************************************
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of
the mistake in delivery.  NOTE: Regardless of content, this e-mail
shall not operate to bind CSC to any order or other contract
unless pursuant to explicit written agreement or government
initiative expressly permitting the use of e-mail for such purpose.

-----Original Message-----
From: joe [mailto:[EMAIL PROTECTED]
Sent: Friday, March 11, 2005 9:15 AM
To: [email protected]
Subject: RE: [ActiveDir] Locate and/or Remove Duplicate Computer Accounts in a W2K AD Ente rprise.

 

Do you mean you are getting the duplicate SPN errors in the event log or ???

 

  joe

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Miller Carol L Contr DYN/ITS
Sent: Friday, March 11, 2005 9:03 AM
To: '[email protected]'
Subject: [ActiveDir] Locate and/or Remove Duplicate Computer Accounts in a W2K AD Ente rprise.

Has anyone found a good method of identifying Duplicate "Computer Account" objects in a Windows 2000 Active Directory Enterprise.  I have attempted to use the "DSQUERY" command from the "Windows 2003 Admin Pak" but I receive error messages indicating that the program is not compatible with the specified domain.

I would greatly appreciate any ideas that you may have regarding this topic.  I also, have confirmed that the duplicate "Computer Account" objects all appear to have unique SIDs.  I am still unclear how they are getting created, but I need to identify them, and remove the ones that are not in use..

Again, Thanks for any insight you may be able to share regarding this issue.

Thanks!!!

Carol....

::::::::::::::::::::::::::::::::::::::::::

//SIGNED//

Mr. Carol L. Miller, MCP, Contractor

Vance Network Administrator

Analyst, System Administrator

DYN/ITS

Vance Support Division

DynCorp - A CSC Company

Vance AFB, OK

DSN: 448-7143, Com: (580) 213-7143

E-Mail: [EMAIL PROTECTED]

https://www.vance.af.mil/

 

********************************************************************************

                           Official Disclaimer Notice

********************************************************************************

This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of
the mistake in delivery.  NOTE: Regardless of content, this e-mail
shall not operate to bind CSC to any order or other contract
unless pursuant to explicit written agreement or government
initiative expressly permitting the use of e-mail for such purpose.

 

Reply via email to