Deploying LANDesk agent to non-persistent VDI images
- Michael MacDonald
Deploying LANDesk 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:
- HKLM\SOFTWARE\Wow6432Node\Intel\LANDesk\CommonApi\UniqueID
- HKLM\SOFTWARE\Wow6432Node\LANDesk\CommonApi\UniqueID
- HKLM\SOFTWARE\Wow6432Node\LANDesk\Inventory\LogonHistory\Logons
For 32-bit VDI images:
- HKLM\SOFTWARE\Intel\LANDesk\CommonApi\UniqueID
- HKLM\SOFTWARE\LANDesk\CommonApi\UniqueID
- HKLM\SOFTWARE\LANDesk\Inventory\LogonHistory\Logons
Information on the Tufts IT Knowledgebase is intended for IT Professionals at Tufts.
If you have a question about a Tufts IT service or computer/account support, please contact your IT support group.