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.

--
Dean Wells
MSEtechnology
* Email: dwells@msetechnology.com

http://msetechnology.com

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Tuesday, June 14, 2005 8:34 PM
To: [email protected]
Subject: RE: [ActiveDir] Lost and found

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.
 
I agree with Dean though, unless the parent of the object was deleted, the object shouldn't hit the lost & found. Basically things go to lost and found if someone makes a change to an object in a container that is no longer existent but hasn't replicated to the DC where the object has been changed yet. I am not sure if a DN name change of the container would impact this. I would look to Eric for that info.
 
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean Wells
Sent: Tuesday, June 14, 2005 7:36 PM
To: Send - AD mailing list
Subject: RE: [ActiveDir] Lost and found

I'm uncertain since I've never tried, have you attempted to read the attribute to determine what it currently contains?

--
Dean Wells
MSEtechnology
* Email: dwells@msetechnology.com

http://msetechnology.com

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kern, Tom
Sent: Tuesday, June 14, 2005 7:18 PM
To: [email protected]
Subject: RE: [ActiveDir] Lost and found

Unfortunately, an admin moved the group back to its ou already.
is there anything i can do from here?
thanks
-----Original Message-----
From: Dean Wells [mailto:[EMAIL PROTECTED]
Sent: Tue 6/14/2005 6:12 PM
To: Send - AD mailing list
Cc:
Subject: RE: [ActiveDir] Lost and found

 

Reply via email to