The agents in 9.5 SP1 allow you to store the Software Usage Monitoring data to a network shared folder location instead of the Registry so that it doesn't get wiped out when the user logs off. We opted to turn it off rather than using another connection to a server. Our main focus is customer support and allowing the support technicians to provide remote support.
In the VDI template we erase the Device ID from the registry and set the device to run a hardware scan only on the next boot. When the non-persistent VDI device gets created from the template, it runs the hardware scan. If this is the first time ever, and the device doesn't exist in LANDesk yet, it will pick up a new Device ID and populate in LANDesk. If the device already exists (from a previous scan the same non-peristent device), it will repopulate the old Device ID. In that case only a quick hardware inventory scan is performed. (We tried this with a mini-scan, but it did not populate the old device ID.) If this is first time for that VDI, there is no software information in LANDesk yet.
The software scan times are set in the Agent configuration. They haven't migrated to the Agent Settings yet. You can set the Date that they will start scanning. Our are set to the year 2113.
We have a query, that detects if the Last Software Scan Date does not exist or if it more than 30 days old.("Computer"."Last Software Scan Date" < "GetDate()-30"). This query is assigned to policy task which will run a full inventory scan. The policy restarts once per month in the wee hours. Brand new devices in a pool will show up in the query when its gets refreshed (every two hours) and they will run the full scan at their next policy sync (every 5 hours). After that they won't show back up in the query until next month.