VDI Blueprints

Define the template from which your virtual desktops are built: provider, desktop type, golden image and settings.


Access: verified_user Admin Area > desktop_windows VDI > VDI Blueprints.


A VDI Blueprint holds everything that is common to a set of desktops: where they run, whether they are dedicated or pooled, the golden image they are cloned from, and their settings. Only instance administrators manage blueprints.

Note

A blueprint is a template. Desktops are created from a VDI profile in an organization, after you add the blueprint to that organization.

Lock a setting to stop the VDI profiles built on the blueprint from overriding it. Unlocked settings can be changed in each profile.

Create a VDI Blueprint

  1. Open verified_user Admin Area > desktop_windows VDI > VDI Blueprints, then click the button that creates a blueprint.

  2. In the Desktops step, name the blueprint, choose its provider, desktop type and image source, then click Next.

  3. In the Image step, choose the operating system, the ISO and the image options, then click Next.

  4. In the Settings and Session policies steps, set up the desktops, then click Next.

  5. Check the Review step, then click Create.

Once the blueprint is created, no desktop exists yet. Build and capture the first version of the golden image, then add the blueprint to your organizations.

Build the First Version of the Image

With the image source Build it in Reemo, Reemo installs Windows from your ISO on a build virtual machine. You add your apps on it, then capture it as version 1 of the image.

  1. Open the blueprint, then the Image tab. Reemo installs the build virtual machine: the Installing Windows stage is in progress.

  2. Click Connect to follow the installation and open the desktop of the virtual machine.

  3. At the Customize stage, install your apps and updates.

  4. On the virtual machine desktop, run Seal Image.

  5. Capture version 1 of the image (Capture stage).

Click Refresh to follow the session. Finish or cancel a session before you start another.

Warning

On some providers, Windows stops at the setup screen. Connect and press Ctrl+Shift+F3 to restart in Audit Mode. Do not complete the setup screens: the account they create would be captured into every desktop.

Sealing re-applies the optimizations of the image and removes per-user Store apps. Run Show Optimizations on the virtual machine desktop to see what will be reverted.

Update the Image

  1. Open the blueprint, then the Image tab, and click the button that updates the image.

  2. Choose how to update: build from an ISO, or add an existing image.

  3. Click Connect, install the updates or apps, run Seal Image, then capture the new version.

The update session goes through three stages: Deploying, Patch and install, Capture. The button is named Build from ISO as long as no version exists. It is greyed out during a session.

The versions table lists each version with its status (for example Building), its origin, the number of desktops built from it and its creation date. Click Details to open a version. The page states which version new desktops are built from.

Roll Back to a Previous Version

Click Roll back on the line of a version in the table to build new desktops from that version again.

Add a Blueprint to an Organization

A Private blueprint is only usable by the organizations you add to it. Add it from the page of the organization, in its VDI Blueprints tab, so that its administrators can create a VDI profile from it. The capacity (maximum and ready desktops) is then set on each VDI profile.

Form Fields

Fixed or Editable

The review step of the wizard separates what you can no longer change from what stays editable.

  • Fixed after creation: the VDI provider, the desktop type, the image source, the operating system, the Windows edition, the product key and the disk size. To change them, create a new blueprint.

  • First image version: the ISO, the optimizations and the Windows policy settings. Later versions can change them, from the Image tab of the blueprint.

  • Editable later: the name, the visibility, the display language, the keyboard layout, the time zone, the local accounts, the size (vCPU and RAM) and the session policies.

Desktops

  • Blueprint name: name of the blueprint, for example Office desktops - Paris.

  • VDI provider: the provider where the desktops run. It cannot be changed after creation.

  • Visibility: Private (only the organizations you add can use the blueprint) or Public.

  • Icon (SVG) - Optional: SVG icon shown to users next to their desktop. Without one, users see the operating system logo. You can lock it.

  • Desktop type (fixed): Dedicated (persistent, each person keeps their own desktop with files, apps and settings) or Pooled (non-persistent, a ready desktop from a shared pool, deleted after each person leaves).

  • Image source (fixed):

    • Build it in Reemo (recommended): you add your apps on a build VM, and update the image in Reemo later.

    • Use my own template: a sysprepped template with the Reemo agent. You update it by registering a new one.

    • Install every desktop: no image, each new desktop runs a full install from your ISO, which is slow. This source is not offered for the Pooled type, because each replacement desktop would be a full install.

Image

  • Type and Windows version (fixed): the operating system (Windows) and its version (Windows 11). The version decides which optimizations are offered.

  • ISO: the OS installation ISO available on the provider, for the first version of the image.

  • Windows edition (fixed): must match an edition inside the selected ISO exactly. A mismatch stops Setup at the edition picker. Windows 11 Pro is the default edition.

  • Product key (fixed): when empty, Windows uses Microsoft’s generic key and is not activated. The field is pre-filled with this generic key.

  • Build VM name: names the build VM only.

  • VirtIO ISO: the VirtIO driver ISO, required for Windows guests. On Nutanix, leave it empty to use the stock Nutanix-VirtIO image.

  • Advanced provider settings: click Expand to set the network, the storage and the rest. Left empty, the provider’s own defaults apply. On Proxmox:

    • Disk storage: the storage that hosts the disk of the VM.

    • Network bridge: the bridge the network card of the build VM is attached to.

  • Optimize this image for virtual desktops: applies Reemo’s recommended set (62 optimizations) while the image is built. Desktops cloned from it inherit the result. Four optimizations have visible side effects:

    • Windows Update for Business reports stop working on Enterprise and Education;

    • window animations, shadows and transparency are off;

    • only the personal Teams chat app is removed, not a managed Teams install;

    • no kernel memory dump is produced on a bugcheck, so a blue screen cannot be analyzed afterwards.

Click Review and customize to show the optimizations by category (for example Telemetry and diagnostics or Background services) with the number of enabled optimizations, and to search for one. Click Hide the list to close it.

Settings

The badges tell when a setting applies: New desktops (to the desktops created afterwards), First version (to the first version of the image), Profile default (copied into each new VDI profile) and Fixed.

  • Join a domain (Active Directory): desktops join the domain during provisioning and use directory accounts.

  • Windows policy settings: Reemo, in the image or Group Policy or Intune. The former are written into the registry of the image, so they are not shown in gpresult. Your Group Policy or Intune overrides them. The choice is pre-set when the desktops of the blueprint join no domain.

  • Administrator account name and Administrator password: the local administrator created on each desktop (at least 8 characters for the password).

  • Standard user account name and Standard user password: the account a person signs in with when the desktop joins no domain (at least 8 characters for the password).

  • Display language: the Windows UI language (English en-US by default). It requires the matching language pack in the installation media.

  • Keyboard layout: defaults to the display language. Set it separately for an English desktop with an AZERTY keyboard.

  • Time zone: a Windows time-zone ID, not an IANA name (UTC by default).

  • vCPU Cores and RAM (MB): the size of the desktops (2 vCPU and 4096 MB by default), copied into each new VDI profile. Each one can be locked.

  • Golden image disk size (GB) (fixed): every desktop gets this disk, and Reemo never resizes it. Leave room to grow.

Session Policies

Customize only what the blueprint must enforce: each policy takes the value of the instance by default (Instance defaults badge). Click Expand to set a group, and lock a policy to enforce it in every profile.

  • Clipboard: Clipboard Read and Clipboard Write (control whether users can read or write the clipboard of remote devices).

  • Collaboration: controls whether the participants of a session can use the collaboration tools (see Collaboration tools).

  • File Transfer: allows file transfer with the remote devices.

  • Sessions: Auto disconnect idle sessions, after a period of inactivity.

  • Printer: allows printing (Windows only, requires a RAW TCP printer on port 9100).

View a Blueprint

Click the name of a blueprint to open its page. The card at the top gives its provider, operating system, creation date, visibility and VM creation method (From golden image). Two badges next to the name tell its state (for example Building) and whether its desktops have problems. The Edit button changes the editable settings.

Available Tabs

  • Image: the golden image, its build or update session and its versions.

  • Configuration: the settings of the blueprint.

  • VDI Profiles: the profiles built on the blueprint.

  • Delete: deletes the blueprint.

See also

VDI — How VDI is organized and which desktop type to choose.

VDI Providers — Connect the hypervisor that hosts the desktops.