Admin Users may want to set up the Desktop App in a VDI environment. There are two main types of VDI environments:

  • Environments where users work with dedicated VMs that are provisioned from a master image. In these environments, each user has their own dedicated VM and virtualized system resources. See our guide on deployments with cloned images for more information on how to configure the Desktop App to work in such deployments.
  • Environments where multiple users can simultaneously connect to a single server, VM, or group of VMs. In these environments, multiple users can share physical or virtualized resources for a single VM or server. Follow this guide for more information on how to configure the Desktop App to work in these environments.

Configure the VDI Solution

  1. Ensure that you only install in environments that meet the minimum system requirements for the Desktop App.

    Note: The minimum suggested requirements assume a single active user on the machine, so allow for more system resources (in terms of memory and CPU) based on the number of anticipated concurrent users.

  2. Install the Desktop App with any desired install parameters.

    Note: Users will need to sign in upon first launching the Desktop App but, if configured correctly, this should only be a one-time step. To remove friction in the drive set up process, see our mass deployment article for install parameters and post-install configuration options that make use of a command-line tool.

  3. If your environment is one in which a user may connect to any one of multiple VMs / servers, ensure the DeviceID key from the following location in the registry is consistent across all the VMs or servers: HKEY_LOCAL_MACHINE\SOFTWARE\Egnyte\Egnyte Drive

    Most environments should already handle this by cloning a master VM image to create multiple VMs*.

  4. Configure your environment to ensure that the following registry and hard drive locations are preserved and restored when a user logs out and logs back in. Doing this will ensure that users don't need to add a drive and sign in to Egnyte upon starting a session. It also prevents loss of any files which did not upload in the previous session:

    In the registry: HKEY_CURRENT_USER\SOFTWARE\Egnyte
    On the hard drive: %localappdata%\EgnyteDrive

*Consistency in HKEY_LOCAL_MACHINE\SOFTWARE\Egnyte\Egnyte Drive will ensure that each user connecting to the environment only has a single entry in the devices dashboard.