什么 ldap 查询返回现在从活动目录中删除的用户对象？
是否有一个 ldap 查询将返回或列出已从活动目录系统中删除的用户对象？ 您是否必须跟踪当前活动目录中的所有用户对象，并维护“最后一次看到”标记，以便告知用户对象何时已从活动目录中删除？
Is there a ldap query that will return or list user objects that have been removed from the active-directory system? Must you track all the user objects currently in the active-directory, and maintain a "last seen" stamp in order to tell when a user object has been removed from the active-directory?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我真的不相信这些信息是可以获得的。 在下一版本的操作系统 (Windows 2008 R2) 中，Microsoft 引入了通过为 Active Directory 对象实现类似于回收站的功能来实现此目的的功能。 请参阅这些文章以获取更多信息：
http://blogs.technet.com/niraj_kumar/archive/2009/02/03/new-feature-active-directory-recycle-bin-in-windows-2008-r2.aspx
http://technet.microsoft.com/en-us/library/dd392261。 aspx
但您可能会看到，这是指对象本身的删除，并且它不提供有关对象属性何时更改的任何信息。 您可以查看最后修改的属性，但即使如此，您也无法知道哪个属性发生了更改（很可能是最后一次登录），因此您再次没有任何帮助。 如果您尝试跟踪正在发生的可以重新创建的问题，我建议创建某种脚本/代码，以给定的时间间隔记录特定用户的属性，然后在从一个步骤移动时继续运行它另一个是问题的重现。
I really don't believe that this information is obtainable. In the next version of the OS (Windows 2008 R2), Microsoft is introducing the ability to do this by implementing a recycle bin like functionality for and Active Directory object. Please see these write ups for more info:
http://blogs.technet.com/niraj_kumar/archive/2009/02/03/new-feature-active-directory-recycle-bin-in-windows-2008-r2.aspx
http://technet.microsoft.com/en-us/library/dd392261.aspx
But you may see that this is in reference to the deletion of the object itself, and that it doesn't provide any information about when a property of the object changes. You can look at the last modified property but even then you have no way of knowing which property changed (more then likely it will be the last logon), so again your left with no help. If your trying to track a issue that is occurring which you can recreate, I recommend that create some sort of script/code which record the properties of a specific user at a given interval, and then just keep running it as you move from one step to the other i the recreation of the problem.