Managing guest VMsThere are two basic types of guest VMs when using Parallels RAS VDI: template-based and non-template based. This topic describes management tasks for both guest VM types, indicating whether a task applies to a particular guest VM type. Viewing guest VM list To view the list of non-template based guest VMs, select Farm > <Site> > VDI > Desktops. If you have a filter applied to the list, remove it by click the magnifying glass icon. Without the filter, the list shows all desktops available in this RAS Farm, including guest VMs (both template-based and non-template based), guest VMs from a pool (RAS or native), and pool-based Remote PCs. Therefore, the Desktops tab is a location where you can view all of your desktops in one place. Here you can perform all of the standard desktop management tasks accessible from the Tasks menu, including Recreate, Delete, Assign, Unassign, Start, Stop, Restart, Suspend, Reset, Show sessions, and others.The Restart operation (graceful) has a 10 min timeout. If not completed during this time, the Reset operation (forced) will be used. To view the list of guest VMs created from a template, select Farm > <Site> > VDI > Templates. Select a template and click Tasks > Show guest VMs. You will be switched to the Desktops tab where the list of desktops will be filtered to include only those that belong to the template. As was mentioned above, you can perform all of the standard desktop management operations on this tab, including power operations, which are described in detail later in this section. For the list to include only the guest VMs from a particular pool, select a pool in the Pools tab and click Tasks > Show guest VMs in Pool. The filter in the Desktop tab can also be applied manually by clicking the magnifying glass icon and entering the filter criteria in the fields that appear at the top of the list. Site defaults Guest VMs created from a template inherit the template settings. To view the settings, note on which template a guest VM is based and then view properties of that template, specifically the Settings and Security tabs. For more information, see Site defaults. Note that you a template can inherit Site default settings or you can specify your own custom settings for it. Non-template based guest VMs have their own settings, some of which (specifically Settings and Security) are inherited from Site defaults. To see settings for a non template-based VM, navigate to Farm > <Site> > VDI > Desktops. A guest VM that doesn't belong to a template is identified by an empty value in the Template column. Right-click a template and choose Properties (note that template-based guest VMs do not have this menu option). Checking the RAS Guest Agent status A guest VM must have the RAS Guest Agent installed and the agent must match the Parallels RAS version. The agent is installed by default when a guest VM is created from a template. If a guest VM was created using the native hypervisor tools, it may not have the agent installed in it. In such a case, the guest VM will be able to serve only the remote desktop. To enable it to server applications or documents, you'll need to install the agent yourself. Note: Guest VMs based on an RD Session Host template must also have the RAS RD Session Host Agent installed. The functionality described here does not verify if this agent is installed. If needed, you can use Tasks > Check Agent on the template itself. To check if the RAS Guest Agent is installed in a guest VM and is up to date:
Deleting a guest VM To delete a template-based guest VM, select it and then click the Tasks > Delete. Important: You should delete a guest VM only from the RAS Console. You should not try to delete a guest VM using the hypervisor's native client or web interface. If you do, it may delete not only the VM but its parent template as well (which will also invalidate all other guest VMs created as linked clones from this template). The reason for this is some native hypervisor clients treat linked clones as standalone VMs. Parallels RAS treats linked clones as clones, not as standalone VMs. Managing guest VMs that failed preparation If a template-based guest VM encounters a problem during the preparation stage, it remains on the server but cannot be used. You can identify such VMs by the "Failed to create" value in the Guest VM State column. Unless a VM like this is repaired, it will be automatically removed after the time period specified in the Site defaults. To see Site defaults:
Recreating a guest VM If something happens to a template-based guest VM and it becomes unusable, you don't have to delete it and create a new one. Instead, you can recreate it keeping its name and MAC address (to guarantee that VM will get the same IP address from the DHCP server). This way none of the other Site settings, which may rely on a broken guest VM, will be affected. Another reason for recreating a guest VM is to apply changes made to the template (when you exit from maintenance without executing the Recreate command). Please note that keeping the MAC address is supported on ESXi, vCenter, Hyper-v and Hyper-v Failover Cluster only. Note: If a guest VM was created from an RD Session Host template and was already assigned to an RD Session Host group, it cannot be recreated. To recreate one or more guest VMs:
When you recreate a guest VM:
|
||||
|