VDI Installation Considerations

  • Optimize the default session policy on the VDI test pool to assure stable session spawning when the VDI is recompiled.
  • Every new VDI creation will start with the initial policy as configured on the golden image. When the golden image is active and communicating with the ESM Server, test the policy on the VDI test pool and push it to the VDI Traps agents. Then fine tune the policy.
  • Issues on restricted non-persistent sessions are harder to investigate because there is no forensic data after the session closes. Consider the following options to ensure forensic data is available:
    • Configure an agent setting rule on all non-persistent hostnames to enable the Traps agent to Send the memory dumps automatically.
    • Reproduce the issue on a persistent session to collect logs and memory dumps and allow additional troubleshooting.
  • Set a fixed number of session hostnames (not random) as licenses are issued by the ESM according to hostname. All naming conventions are supported.
  • The ESM Server automatically revokes a license when an agent logs off of a VDI session. In cases where the VDI session is not properly closed, the ESM server waits for a timeout before automatically revoking the license to make it available for other agents. If another VDI session needs to use the license before the license revocation period expires, use the ESM Console to forcefully Remove an Endpoint from the ESM Console. This action returns the license to the license pool and removes the VDI session from the ESM Console.
  • For non-persistent VDI mode, after you upgrade the Traps agent on the golden image from Traps 3.4 or earlier releases, you must mark the golden image as a VDI using the Traps VDI Tool (see Configure the Golden Image for Non-Persistent VDI).

Related Documentation