Correct, you can not wildcard that type of attribute like you can't wildcard DNs.
If you want everything from June 1, 2003 on you can do something like Whenchanged>=20030601000000.0Z joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, December 19, 2003 5:05 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Search filter for createTimestamp search with LDP Thanks Jerry, I was missing the proper date format, specifically the final .0Z. I guess the *(any) does not work there. This time format works in both the whencreated/whenmodified attributes and the createtimestamp/modifytimestamp. According to something I stumbled over in my search for this answer, createtimestamp and modifytimestamp are the recommended attributes to use as they are replicated to all DCs. -----Original Message----- From: Jerry Welch [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:53 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] Search filter for createTimestamp search with LDP David, Try (whenChanged>=20020608131321.0Z) with the appropriate data and time. Jerry Jerry Welch CPS Systems SimpleSync US/Canada: 888-666-0277 International: +1 703 827 0919 (-6 GMT) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Friday, December 19, 2003 2:03 PM To: [EMAIL PROTECTED] Subject: [ActiveDir] Search filter for createTimestamp search with LDP I need to search for user objects created or modified after a specific date. The createTimeStamp and modifyTimeStamp Attributes appear hold this information for each object. The problem I have is that I cannot get the correct LADP search filter to return any matches. Assuming BASE DN is correct and Sub tree is selected, If I set the filter to (createTimeStamp=*) I get a list of all the objects in the sub tree. Other searches (i.e. (samaccountname=doe*)) also behave as suspected. When I attempt to set the filter as either of the following; (createTimeStamp>=12/11/2003*) (createTimeStamp>=20031211*) it fails. If I look up a user with LDP and retrieve the exact value of their createTimeStamp and use it in the filter, it also fails. I suspect there is a matching rule or syntax issue for UTC Coded Time, but I cannot seem to get the right combination. Any ideas? David Frost Directory Engineering, Messaging, Directories and PKI Engineering Services Industry Canada List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
