Skip to main content
Skip table of contents

Virtualization: Operate

Pre-Requisites

This pack requires some categories contained in the Shared Categories content pack, please make sure to have it installed in your environment before installing this pack.

The Virtualization type category must absolutely be configured in order to be able to target the corresponding VDI and SBC VMs. For the rest of the categories, depending on the description of each, you may or may not complete them.

Defining Excluded Applications

Configure Category Virtualization - Excluded Applications to list applications that will not be excluded from being reported on. This is prepopulated with a selection of common applications that would not normally be wanted. Any number of applications can be added or removed.

Defining Excluded Binaries

Configure Category Virtualization - Excluded Binaries to list executable that will not be excluded from being reported on. Any number of executables can be added.

Defining Back End Systems

Configure Category Virtualization - Back End Systems to define destinations that the Virtual Infrastructure will be communicating within your environment. This category can be individual systems or contain entire ranges as is wanted.

Defining VDI Devices

Configure Category Virtualization type to define the Virtual Desktop Infrastructure (VDI) in your environment, such as Citrix, VMWare, or Windows Virtual Desktop (WVD). This category should be assigned to all virtual machines or remote PCs that have the collector installed.

Defining SBC Servers

Configure Category Virtualization type to define the Session-Based Computing (SBC) in your environment, such as Citrix, VMWare, Microsoft Remote Desktop Server Host (RDSH) or Windows Virtual Desktop Multisession (WVD). This category should be assigned to all servers or multisession that have the collector installed.

Defining Different Virtualization Images

Configure Category Virtualization - Virtual Image to define the desktops that are running a particular VDI Image. This is then used for Image performance comparison within the Solution Pack. Rename the images according to needs in the category configuration.

For instance, one keyword could be named "Windows 10 VDI". Then tag your virtual machines to the keywords you just created. Here is a link to the documentation on how to tag objects with Nexthink.

Defining Infrastructure

Category Virtualization - Operate - Infrastructure should be completed if you install Nexthink collector on Virtual Management servers such as Citrix Director or VMware Horizon Management server.

This category is used on the Virtualization - Operate - Controller Servers service to monitor virtual infrastructure devices.

Defining Service and roles

Category Virtualization - Operate - Services and roles should be completed if you want to monitor device compliance and stability on agent

Defining Virtual Agent

Category Virtualization - Operate - Virtual Agent should be completed if you want to use the compliance dashboard to manage the virtual VM compliance.

Defining VDI Network Physical / Virtual

We suggest you to adapt the network response time used in the VDI Network Physical / Virtual dashboard to measure your most important response time; for instance, the response time when connecting to a critical service in your company. To do this edit the metrics Virtualization - Operate - Average network response time on physical devices and Virtualization - Operate - Average network response time on virtual devices.

To clean the Library Pack

Please refer to the Disclaimer

Before cleaning, you can backup your "Virtualization Operate" Library Pack version. To backup, follow this link.

  • In the Finder:

In each section described, right-click on "Library\Virtualization Operate" and delete.

  • Services

  • Metrics

  • Categories

  • Score

  • In the Portal:

Go on the "Virtualization Operate" module menu then click on "Delete Module..."

Go on the "Virtualization Operate Service" module menu then click on "Delete Module..."

The operations described in this article should only be performed by a Nexthink Engineer or a Nexthink Certified Partner.

If you need help or assistance, please contact your Nexthink Certified Partner.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.