Managing virtual machines



Virtual machines (VMs) are software emulated computer systems that allow you to run operating systems and applications in a contained, isolated, and secure environment, behaving like an independent computer.

Virtual machines run on physical servers called hosts. Depending on a host's resources, it can run one or multiple virtual machines simultaneously.

When creating a workspace, your desktop and application hosts are esentially virtual machines running on Neverfail infrastructure.

The Virtual Machines section shows you the status of the virtual machines running across all your workspaces, aggregated into one page.


You can see the following VM-specific details:

  1. Name: the virtual machine name that you can use to identify it in your infrastructure.
  2. Role: the role a VM fulfills in a workspace:
    • Broker: a VM that fulfills the role of a Remote Desktop Connection Broker (RD Connection Broker). This machine ensures the following operations:
      • Allows organization users to connect to App and Desktop session hosts.
      • Keeps track of active Remote Desktop sessions.
      • Ensures business continuity upon accidental or intentional session disconnection.
    • Active Directory: a VM running Windows Server with the Active Directory Domain Services installed. It manages active users and other machines joined in the domain.
    • App Session Host: a VM used to run remote apps, without offering the full desktop experience. When publishing a new application, this VM is rebuilt from scratch.
    • Desktop Session Host: a VM that offers a full desktop experience.
    • App Installation Host: a VM used to reconfigure templates for App and Desktop Session Hosts.
    • Network Drive Host: a VM used as network storage.
    • Windows Host: a VM that is part of the network, domain joined, but is not used for application publishing or desktop session publishing. Typically used as an LOB (Line Of Business) server, such as database or an application server.
    • Persistent Session Host: a VM that does not rebuild itself from scratch when publishing a new application.
  3. IP address: the IP address assigned to the VM in the domain.
  4. vCPU utilization level: a high level of vCPU usage for long periods of time may indicate the need for more resources. Consider provisioning more vCPU cores to the target VM.
  5. vRAM utilization level: a high level of vRAM usage for long periods of time may indicate the need for more resources. Consider provisioning more RAM to the target VM.
  6. Alerts: this section informs you of any actions that you may need to take for a specific VM.

Filtering Virtual Machines

In large environments using multiple workspaces, the need for additional VMs can increase. This can make the process of managing said VMs increasingly difficult.

The Virtual Machines section allows you to filter the VMs in your workspaces based on the workspace they are assigned to and the role they fulfill.

Follow the steps below to filter VMs based on your criteria.

  1. Log in to your Neverfail Workspaces account.
  2. Go to Virtual Machines.
  3. Use the Workspace and Roles filters at the top of the table to narrow down your VM search.

To eliminate the applied filters and see all VMs across your workspaces, click Remove filters.


0 out of 0 found this helpful



Article is closed for comments.