You will want to add the registry key to your ldappl3.template file so it is scanned.
I found the registry information at
Use the following doc: http://community.landesk.com/support/docs/DOC-1089
Not sure that will work since it is in HKCU. The only time it will get inserted is if the user manually runs the inventory scan or you use something creative like startasuser. Also, if you do get it to work, if you have more than one user login to the machine the value will get overwritten for each user.
A cleverer / easier way may be to copy those registry keys during your login script into a dedicated area of your registry (Say - "HKLM\Software\LANDesk\MyCustomStuff\" ) and have the attributes be related to the uesrs.
... and the values to match ... that way, even if several users log on to a single machine, they won't overwrite each other, and all you need to do is read this stuff out via the LDAPPL3 for instance. Probably custom data is the least difficult way to do this, as HKCU stuff is a pain to get otherwise.
Hope this helps (Not ENTIRELY sure the above will work, I've just woken up after all) :).
LANDesk EMEA Technical Lead.
I am trying to set up a querie to list machines that are going through out old proxy server, any ideas welcomed!!
Cheers for that, so I will have to reconfigure the scanner to do this, sort of hoped for a quick fix. Thanks anyway.
ldms_client takes longer to explain than it does to install Send out the ldms_client_node_install.exe, run the core-side program and paste your string into one of the HKCU fields, and you're done.
You do need to initiate a scan to get data back -- I usually modify the Manage Scripts > inventory scanner script. Remove /NOCD (this is custom data, we want it), and add /F /SYNC for luck.
Thansk for this, I have managed to configure this to get the info I want but even though I have selected n reboot in the delivery method around 30% of machines get the familiar LANDesk count down to reboot. Why is this?