RE: [ActiveDir] which GC answers?

[joe]

> “Originating DC” is also the “owner” of the object, right?    Originating DC is simply the DC that the originating write occurred on, contrast with a replicate write. What DSA was the attribute for the object modified on.     > But, if the “owner” is no longer around, the object is garbage   Nope because it isn't an owner. If this were the case you could have a lot of garbage everytime you lost or dcpromoed a DC.     > My question is this – why are lingeringobjects such a “bear” to clean out?   Because no one has made it easy yet and because I haven't personally run into a huge issue with them yet. :)     > existence of a “replfix” tool   Haven't heard of it.     > it would really be helpful to include examples within the repadmin help   Hehehe. The help is some of the most organized and easily readable parts of that program. ;o)       -- O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm      From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thommes, Michael M. Sent: Wednesday, May 03, 2006 11:28 AM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] which GC answers? Hi Jorge,     I don’t mean to hijack this thread but I have also been having an issue with lingeringobjects.  I ran your repadmin command shown below on one of the lingering objects I have.  For the lingering object I specified, the output lists a GUID (“Originating DC”) that doesn’t exist any more.  An “Originating DC” is also the “owner” of the object, right?   The member DC/GCs) of the domain that once hosted this “Originating DC” produce a different output from the repadmin /showobjmeta command than the other GCs – namely “Directory Object not found”.  If a DC is demoted, the object would be “owned” by one of the remaining DCs.  But, if the “owner” is no longer around, the object is garbage.  Right?   My question is this – why are lingeringobjects such a “bear” to clean out?  It seems to me an admin should be able to use a “repadmin /removelingeringobjects GC: <DN of lingering object>” –type of syntax to take care of all of the GCs at the same time.  My TAM has indicated the existence of a “replfix” tool, but I’m not sure how it works.  Thoughts/comments?   Mike Thommes   Ps. For any MS folks out there, it would really be helpful to include examples within the repadmin help considering how powerful this command can be. Pps.  I think “lingeringobjects” are synonymous with “headache”.   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Almeida Pinto, Jorge de Sent: Wednesday, May 03, 2006 9:21 AM To: ActiveDir@mail.activedir.org Subject: RE: [ActiveDir] which GC answers?   a way to check this is:   REPADMIN /SHOWOBJMETA GC: <DN of lingering object> > OUTPUT.TXT   GC: targets ALL GCs in the forest   For each GC: * you get the metadata of the object if it exists on the GC OR * you get "Directory object not found" if the object does not exist   in addition to this you can wrap a script around this that takes away some manual stuff you must do.   Met vriendelijke groeten / Kind regards, Ing. Jorge de Almeida Pinto Senior Infrastructure Consultant MVP Windows Server - Directory Services   LogicaCMG Nederland B.V. (BU RTINC Eindhoven) (         Tel     : +31-(0)40-29.57.777 (    Mobile     : +31-(0)6-26.26.62.80 *   E-mail     : <see sender address>   From: [EMAIL PROTECTED] on behalf of [EMAIL PROTECTED] Sent: Wed 2006-05-03 14:44 To: ActiveDir@mail.activedir.org Subject: [ActiveDir] which GC answers? When I use ldp and I found a user (lingering) how can I know which GC of many of them has that copy of the object? I use ADSIEDT, but I have many GC´s. is there a easier way to discover in which of them it is? Thanks Adrião F Ramos