You should just delete everything in that ObjectMoveTable container as well as the other stuff related to Distributed Link Tracking. Search the KB for a script called dltpurge.vbs to clean it up.
Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: Mike Leone [mailto:[email protected]] Sent: Tuesday, August 10, 2010 11:06 AM To: NT System Admin Issues Subject: Re: Odd group name in AD - MORE On 8/10/2010 11:57 AM, Brian Desmond had this to say: > If there is no longer a conflicting object then rename it. If there is than > delete one of them. This happens when on two DCs you (within a single > replication cycle) create two objects with the same RDN which would not lead > to a consistent directory if AD didn't do something. Thanks. I found <http://support.microsoft.com/kb/218614> which shows how to use "search.vbs" to see all such conflicted replications. And I also found like 32 of them, all in the "ObjectMoveTable" attribute, in the SYSTEM section of AD U&C. For the moment, I will leave those there, as I am unfamiliar with those objects, and I don't want to screw anything (else) up. :-) I did remove the other CNF objects that were based on a group entry, tho. Which should solve the immediate problem of LDAP lookups returning funky results ... > > Thanks, > Brian Desmond > [email protected] > > c - 312.731.3132 > > -----Original Message----- > From: Mike Leone [mailto:[email protected]] > Sent: Tuesday, August 10, 2010 10:25 AM > To: NT System Admin Issues > Subject: Re: Odd group name in AD - MORE > > On 8/10/2010 11:11 AM, Mike Leone had this to say: >> As part of a Lotus upgrade project, the consultants have been making >> LDAP caalls to AD, to lookup users, and get the list of groups they >> belong to. And we've noticed a user with some groups that look like this: >> >> "CN=Remote Control >> Operators\0ACNF:ea55fc7c-26e5-4d90-8203-a9ef411402f6,CN=Users,DC=...." > > Well, I did find these groups in AD (in the Users folder), and we > *think* they were created by LANDesk upgrades over the years (or perhaps by > failed LANDesk upgrades). The members of these groups were the groups for > LANDesk Remote Control. > > So I removed the members (I was leery about removing the group completely, > without more info). So hopefully that should resolve the weird lookups. > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
