We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Managed Workplace

Hyper-V User Requirements and Setup

  • Last updated on

The Hyper-V service module supports Hyper-V hosts running the following versions of Microsoft Windows:

  • Microsoft Hyper-V Windows Server 2012
  • Microsoft Hyper-V Windows Server 2012 R2
  • Microsoft Hyper-V Windows Server 2008 R2
  • Microsoft Hyper-V Windows Server 2008
  • Microsoft Windows 8
  • Microsoft Windows 8.1

To install the Hyper-V service module, you must be running Barracuda Managed Workplace 2013 R1 FP2, at a minimum.

Additionally, you must ensure the following requirements are met:

  • You must install the Hyper-V service module, which is available in Update Center. The service module adds one new policy module to the system, to monitor host servers. You can then add this policy module to a policy set, or apply them to the corresponding groups or devices to begin monitoring. See “Using Service Modules” in the User Guide or online help.
  • For a site to be monitored with the Microsoft Hyper-V service module, PowerShell must be installed on the Onsite Manager server and on each host machine. If PowerShell is not installed, a notification message will appear in the service module dashboard. The Hyper-V service module supports all versions of PowerShell except PowerShell 1.0.
  • The role for the user working with Microsoft Hyper-V through Managed Workplace must have permissions to device management and reporting. By default, Administrators, Technicians and Service Managers are configured with these permissions. See “Setting Permissions for a Role” in the User Guide or online help.
  • The user account for the user working with Microsoft Hyper-V must have object access to apply the policy modules to the host machine at a site. See “Setting the Objects a User Account Can Access” in the User Guide or online help.

Applying the Microsoft Hyper-V Policy Module

The Hyper-V service module includes the following policy module:

  • Microsoft Windows Server Hyper-V Technology Policy Module for Service Module

This policy module monitors performance counters and Windows Events on VM hosts, and contains hundreds of alert configurations to alert on the following types of events:

  • guest shutdown
  • a guest consuming excessive memory, potentially causing a performance breakdown
  • failure during snapshot creation.

For information on viewing Hyper-V alerts, see Viewing Hyper-V Alerts.

You can access this policy module from within the service module itself.

  1. In Service Center, click Configuration and then click Service Modules.
  2. From the list of service modules, select Hyper-V.
  3. To apply monitoring to the Microsoft Windows Server Hyper-V Technology policy module:
    1. Click Microsoft Windows Server Hyper-V Technology.
    2. To add the policy module to a policy set, under Policy Set Membership, click Add. Select the policy set, and click Add.
    3. To apply the policy module to a group, click Microsoft Windows Server Hyper-V Technology. Click the Manual Application tab, and then under Applied Groups click Add. Filter on the Group Type, if desired. Select the group and click Add.
    4. To apply the policy module to a device, click Microsoft Windows Server Hyper-V Technology. click the Manual Application tab, and then under Applied Devices click Add. Filter the list of devices. Select the device and click Add.
  • Note: When applying the policy module, you must ensure that the devices to which it is applied, whether through policy sets, groups, or manually added devices, are valid host devices. If the policy module is applied to non-host devices, then some of the monitors will collect data for these devices and present it in the service module dashboards. For example, memory available, memory page faults, etc.

Last updated on