How Guest VMs Are Created From a Template

After a RAS Template is created, Parallels RAS begins creating guest VMs from it, one virtual machine at a time. The number of VMs created at this time is determined by the Number of guest VMs deployed on the wizard completion property (all property names here and later refer to the Create Parallels RAS Template Wizard described earlier).

The number of VMs available at any time will never go below the number specified in the Keep available buffer property. To comply with this rule, a new VM is automatically created when needed. At the same time, the total number of VMs will never exceed the number specified in the Maximum guest VMs property.

Please note that creating a new guest VM from a template takes some time, especially when a template is configured to create full clones (linked clones are created much faster). If a guest VM is in the middle of being created, and no other VMs are available, a user (or users) who need it will have to wait until the VM is ready.

If a guest VM encounters a problem during the preparation stage, it will remain on the server in unusable state. You can identify such VMs in the Guest VM List dialog (described in the section that follows this one) by the "Failed to create" value in the Status column. Unless a VM like this is repaired or recreated, it will be automatically removed after the time period specified in the Auto remove guest VMs which failed preparation after field on the VDI > RAS Templates tab page. For more information on how to recreate a guest VM, please see the RAS Template Maintenance section .

Auto-deletion of guest VMs

A guest VM is automatically deleted when it is unassigned from the group and stays unassigned for the time period specified in the Delete unused guest VMs after field. The unassignment can happen in one of the following cases:

• A guest VM is removed manually from the group settings.
• A guest VM is removed automatically when the group workload is below the value configured in the group settings. Specifically, the least loaded RD Session Host is put into drain mode after all users are logged off and is then unassigned from the group.