Deploying agents to non-persistent VDI images
When deploying agents to non-persistent virtual desktop interface (VDI) disk images, there are a few extra steps you must take.
The agent configuration process adds unique ID and logon history tracking registry entries for that device. In a non-persistent environment, this data will be lost when the image resets.
If you want to make sure Management Suite tracks each machine in the VDI pool individually, you must delete these registry keys from the base image. Doing this allows the registry keys to be recreated when each machine in the VDI pool boots the first time and the agents load.
These are the UniqueID and logon tracking registry keys you must delete from the VDI base image.
For 64-bit VDI images:
For 32-bit VDI images:
If you're using software usage monitoring, you must also set a UNC path where software monitor data files will be stored. If you don't set a path, software license monitoring will store monitoring data in the registry. In a non-persistent environment, this data will be lost when the image resets.
To record software usage statistics to a network location
- Click Tools > Agent configuration.
- Double-click the agent configuration that you will use on your VDI image.
- Click Standard LANDESK agent > Software usage monitoring.
- Select Use software monitor.
- Select Record software usage statistics to a network location.
- Enter the UNC path information and the credentials the agents on the VDI image should use to access that UNC path.
- Save your changes.
- Deploy the agent configuration to your VDI base image.
- Delete the UniqueID and logon tracking registry keys mentioned earlier in this section.
- Save the changes to your VDI base image.
Was this article useful?
The topic was:
Not what I expected
Copyright © 2016, LANDESK. All rights reserved.