Joe's - lastKnownParent populated only during (group) object's-parent-deletion coinciding with (group) object's-move into deleted (& same) parent ... operations originated against individual DCs.
Dean's - lastKnownParent also populated during 2K3 DC's decision (when resolving conflict) to move (group) object into LostAndFound container due to absent parent ... lastKnownParent was populated as a result of conflict-resolution's 'move to LostAndFound' operation. -- Dean Wells MSEtechnology * Email: [EMAIL PROTECTED] http://msetechnology.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hunter, Laura E. Sent: Tuesday, June 14, 2005 9:20 PM To: [email protected] Subject: RE: [ActiveDir] Lost and found Hmmmm, this last bit just piqued my interest: [joe] I think lastKnownParent is only available on objects deleted on a K3 DC. I.E. If an object hasn't been deleted and if that deletion didn't occur on a K3 DC, it wouldn't be populated. [Dean] Not quite, your statement is true ... but only to a point. Assuming the origin of the move operation was a 2K3 DC, the lastKnownParent will indeed be populated ... the attribute serves a greater purpose than most documentation will elude to. *stares* Okay, what's the difference between what the two of you just said? It would appear that there's a subtlety I'm missing, since it reads the same to me. - Laura List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
