I was trying to filter LDAP import based upon LDPA ipPhone value. Filtering empty ipPhone is working with:
<?xml version="1.0" encoding="UTF-8" ?> - <!-- DTD generated by XMLSPY v5 rel. 4 U (http://www.xmlspy.com) --> <!DOCTYPE data (View Source for full doctype...)> - <data> <sql query="select * from ldapfilter where tkldapserver=1" /> <sql update="update ldapfilter set filter ='(&(objectclass=user)(!(objectclass=Computer))(!(UserAccountControl:1.2.840.113522.214.171.1243:=2))(ipPhone=*))' where tkldapserver=1" /> <sql query="select * from ldapfilter where tkldapserver=1" /> </data>
What I was to trying to do it was filtering ( for example ipPhone>1000 ) with no success: i filter still not empty field, also restarting Tomcat and Dirsync
Yeah... I've tried doing it as well and it doesn't work.
best thing to do is get access to the 'AD Users and Computers' MMC, and then run custom searches with your intended filter. Test it to death before trying to put it in CCM.
What I found was:
>= works OK for text comparisons (e.g. >=Bob) but not brilliantly... and doesn't work well at all for numeric comparisons.
ipPhone=1* works, so you can do multiple of those e.g. put something like this in your filter string for anythign starting 1 or 2:
I guess since the contents of ipPhone and other fields such a telephoneNumber are actually strings, not integers, it doesn't work the way you would expect; it's comparing dictionary order rather than numeric.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Yes, i found out what You wrote. Comparing text will works ( =23* or =1* and so on ). Maight be converting ascii string in Hex i can use > or >, but I'm not a programmer so.... it's ok like this, with some "or" operator is ok.
You have to re-sync, did you perform a manual sync? If so it should take several minutes depending on how many users are in your LDAP, and then all users that are no longer matched will be changed to INACTIVE state, they will be completly gone at 3 AM or so next day.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...