Multi-provider template distribution

When you create a template, it is normally managed by a single VDI provider, which is the same provider to which the source virtual machine belongs. Clones are deployed from the template and run on the same VDI provider, which was used to create the template. Cloned guest VMs are usually stored on a centrally shared storage, such as Storage Area Network (SAN).

Beginning with Parallels RAS 18, admins have the ability to create a template and distribute it to multiple Microsoft Hyper-V hosts. As a result, the template configuration, as seen in the Parallels RAS Console, is shared among multiple Microsoft Hyper-V hosts, while each host has its own copy of the template residing on its local storage. This makes it possible to deploy clones not only to a centrally shared storage, but also to local disks of multiple independent Microsoft Hyper-V hosts. Scaling out is easily carried out by adding as many Microsoft Hyper-V hosts to the template distribution list as necessary.

Template distribution is configured on the Distribution page of the Create Parallels Template Wizard, which is described in the subsequent sections. If you are planning on using the template distribution functionality, please read the Prerequisites subsection below before running the wizard.

For more information about managing multi-provider distribution for a template, see also Managing multi-provider template distribution.

Prerequisites

• Template distribution is supported on a standalone Microsoft Hyper-V Server 2012R, 2016, 2019, 2022.
• All target VDI providers must have identical:

  - Provider type and subtype.

  - Folder path where guest VMs will reside.

  - Virtual switch name to which guest VMs are connected.

• Hyper-V hosts must be domain-joined. The current implementation uses a full VM copy of the template to distribute the template to other hosts (local storage) via the Hyper-V Live Migration mechanism.

  Note: Full clones can also be moved to other hosts via Live Migration, but the process is time-consuming (equal to the first copying of the template).

• The Microsoft Hyper-V server hosting the source VM may also be used as a target host.
• Always ensure that enough storage space is available prior to choosing target hosts to which the template will be distributed and on which clones will be created.
• Hyper-V settings must have Kerberos authentication enabled and appropriate delegations configured in AD:

  - Go to Hyper-V settings for the host machines and enable Live Migration using Kerberos.

  - Go to Active Directory Users and Computers and for each Hyper-V host server enable delegation for "cifs" and "Microsoft Virtual System Migration Service" for all servers you want to migrate To and From.

Note: If authentication isn't working, try changing the "Use any authentication protocol" option.