1 of 1 people found this helpful
you need a regular policy rather than a PSP, and you need it to refresh on a regular basis so that new matches to the query are caught. Also note the uninstall package association... probably not much real world utility unless you frequently move machines from OU to OU, but the kids on the curb at the Gas'n'Sip seem to think it's cool.
PSPs are for when you want to introduce a new policy, but you want to push to the majority of the targets right now instead of waiting for them to get around to asking.
Thanks! That clears things up for me a little. Now, how do I make sure that the query is always pulling the latest information from AD? I know the SCHEDQRY process by default runs every 60 minutes. Do I just have to change the default run time of that value or is there another way to ensure that LANDesk is receiving the most up to date AD information?
You are looking in the right place. increase the frequency and it will be more up to date. Realise though that it is set this way to reduce load on the AD that would be caused by constant re-evaluations. If you immediate updating once a machine is added, then the system isn't designed to do that so you need to handle the delay in some way.
I did see another post about NetworkD's adgroups program, that might also help you. It puts group memberships into the inventory so you can push to AD groups.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
Schema extension is not something I like to encourage. Use the Primary Owner field (for user) or LDAP location (for computer) to target inventory based AD queries. If you want ADSI driven queries, just use Directory Manager to build your targeting.