Does anyone else have an issue with Full scans running every time a new VDI is started? In our environment, we have non-persistent VDI, every time a user logs in, a new VM is created from a master and they get a brand new machine. When this happens with the LANDesk agent installed, it wants to run an initial full inventory scan when each machine is started. This becomes an issue when 300+ people are are logging in at the same time and every VM is running a full scan. Our backend IO spikes, everything comes to a screeching halt. If we throttle the scan CPU utilization, now we have a persistent scan running for hours taking up (albeit a small amount ~2%) CPU usage.
My question is, if we have a master image with the Agent installed, we run a full scan on that master, delete the DeviceID keys in the registry and create the VDI environment, how can we have LANDesk see that even though it is a new DeviceID, we have already ran a full scan? One thought we had is that the inventory file "invdelta.dat" contains a DeviceID that matches the master, could we run a script that searches the machines new unique ID and inject that into the file?
Any suggestions would be helpful. We already brought our entire VDI environment down because of the LANDesk initial full scans.