VDI

Deliver virtual desktops to your users from your own hypervisors, and control how they are built and assigned.


Access: verified_user Admin Area > desktop_windows VDI.


VDI (Virtual Desktop Infrastructure) gives each user a Windows virtual machine, called a virtual desktop, that runs on a hypervisor you operate. Reemo connects to the hypervisor, creates and deletes the virtual machines, and users connect to their desktop through Reemo. A virtual desktop contains a full operating system, whereas a container is much lighter: the two uses are very different.

Note

VDI is currently available for On-Premises deployments only.

How VDI Is Organized

VDI relies on four building blocks, from the hypervisor to the desktop your users open:

  • VDI Provider: the connection to your hypervisor. Reemo supports Proxmox, Nutanix, AWS and Vates (Xen). An instance administrator creates it from verified_user Admin Area > desktop_windows VDI > VDI Providers. See VDI Providers.

  • VDI Blueprint: the template from which desktops are built. It holds the golden image (the operating system and the software installed on it) and the settings that apply to every desktop. Only instance administrators manage blueprints, from verified_user Admin Area > desktop_windows VDI > VDI Blueprints. See VDI Blueprints.

  • VDI Profile: the link between the users of an organization and a blueprint. A profile inherits the settings of its blueprint, can override those the blueprint leaves unlocked, and sets the capacity of the organization. Organization administrators manage it from inventory_2 Inventory > VDI Profiles.

  • Virtual desktop: a virtual machine cloned from the golden image of the blueprint, on the hypervisor of the provider.

Set Up VDI

Follow these steps in order. The first four are done by an instance administrator, the last one by an organization administrator.

1. Prepare
checklist

Enable VDI and prepare the hypervisor.

VDI Prerequisites
2. Connect
dns

Create a provider and test the connection.

VDI Providers
3. Build
construction

Create a blueprint and capture the golden image.

VDI Blueprints
4. Make available
share

Add the blueprint to organizations.

VDI Blueprints
5. Use
play_circle

Create a VDI profile: users connect.

  1. Prepare: enable VDI and prepare the hypervisor (ISO, network, credentials). See VDI Prerequisites.

  2. Connect: create a VDI provider and test the connection. See VDI Providers.

  3. Build: create a VDI blueprint, build the golden image and capture its first version. No desktop can be created before this capture. See VDI Blueprints.

  4. Make available: add the blueprint to the relevant organizations, from the VDI Blueprints tab of each organization.

  5. Use: in the organization, create a VDI profile from the blueprint and set its capacity (maximum and ready desktops). Users then connect to their desktop.

Choose a Desktop Type

The desktop type is set when you create a blueprint and cannot be changed afterwards. These are also called persistent and non-persistent desktops.

  • Dedicated (persistent): each person keeps their own desktop. Files, apps and settings stay between sessions.

  • Pooled (non-persistent): each person gets a ready desktop from a shared pool, and the desktop is deleted after the person leaves.

For example, with a dedicated desktop, a person who signs in on Monday, Tuesday and Wednesday gets the same desktop each time, with their files and apps.

With a pool, the same person can get a new desktop each time, without the files of the day before.

In a pool, a session goes through three states: the desktop is in use, then reserved for a while after the person disconnects, then deleted. Pooled desktops are prepared in advance according to the capacity of the profile (hot pool and cold pool).

Hypervisor Terminology

Reemo keeps the vocabulary of each hypervisor in the interface instead of replacing it with a common term. The machines that host the desktops are named differently depending on the type of provider:

  • Proxmox: nodes.

  • Nutanix: clusters.

  • Vates (Xen): hosts.

Before You Start

Enable the feature and prepare your hypervisor before you create your first provider. See VDI Prerequisites.

Learn More

  • VDI Prerequisites: enable VDI, give Reemo access to the hypervisor, and prepare the ISO files, networks and licenses.

  • VDI Providers: connect a hypervisor to Reemo and check its state.

  • VDI Blueprints: define the template of the desktops, build and update the golden image.