Connector configuration

The Snow Integration Connector for Microsoft Hyper-V is configured in Snow Integration Manager (SIM). For more information on SIM, refer to Snow Integration Manager.

Prerequisites

  • A supported version of Microsoft Hyper-V is required. Refer to Snow Compatibility Matrix for versions supported by the Snow Integration Connector for Microsoft Hyper-V.

  • When running Snow Integration Manager on Windows 7 or Windows Server 2008, Windows Management Framework 3.0 must be installed.

  • Login credentials for standalone Hyper-V servers:

    • Use either a domain user account or a local user account.

    • The user account must be member of the Hyper-V Administrators group of the Hyper-V server.

    • The credentials must have access to the server’s WMI interface.

  • Login credentials for VMM servers:

    • Use a domain user account.

    • The user must be member of the local Administrators group of the VMM server.

    • The user must be assigned a role that has the Read-Only Administrator profile with the All Hosts scope assigned to it.

      To create the role and set the scope, open the Virtual Machine Manager Console on the VMM server, and then go to Settings|Security|User roles.

  • For VMM servers: Make sure that PowerShell Remoting is enabled on the server.

    Example of PowerShell script:

    Enable-PSRemoting -Force
    

If the connection fails to a server that is not a member of the domain, or if connection by IP address is used, the server’s IP address (or name) might need to be added to “TrustedHosts” on the local computer. Example of PowerShell script:

set-Item wsman:\localhost\Client\TrustedHosts -Value “xxx.xxx.xxx.xxx, xxx.xxx.xxx.xxx, …”

Tip

The recommendation is to either install the Snow Inventory Client for Windows on the virtual machines, or gather inventory data from the virtual machines using another SIM connector. The Hyper-V connector does not perform software scan on the virtual machines.

  • The ports required by the Snow Integration Manager to connect to Microsoft Hyper-V connector include:

    • Dynamic ports used between 49152 – 65535 (UDP)

    • WMI that uses TCP 135

    • WinRM  TCP/5985 (HTTP)  and TCP/5986 (HTTPS)

Configure the Microsoft Hyper-V connector

The Microsoft Hyper-V connector uses an API connection.

  1. Enter the Site name for this collection of Hyper-V servers.

    This setting will override the Global site id.

    hyperv_1.png
  2. To add one or more Hyper-V servers to scan for virtual machines, select Add.

    The Microsoft Hyper-V Server dialog box appears.

    hyperv_2.png
  3. In the Server name or IP box, enter the hostname or IP address of the server (type “.” for localhost).

  4. Specify whether this is a standalone Hyper-V server or a VMM server controlling one or more Hyper-V hosts.

    For a VMM server, select whether HyperThreading is enabled on the hosts to ensure that the correct number of processor cores is reported to Snow License Manager

  5. Enter logon credentials in the User (username or DOMAIN\username) and Password boxes.

  6. By default, each virtual machine’s name is its Fully Qualified Domain Name (computer name + domain), for example MYCOMPUTER.mydomain.local.

    If only the computer name is needed, select the Remove domain suffix from virtual machine names checkbox.

  7. For a VMM server, go to ???. For a Standalone Hyper-V server, go to ???. 

  8. In the DataCenter name area:

    1. Select whether the hosts belong to a VMHostGroup or a HostCluster configuration in the System Center VMM server.

    2. If you prefer stand-alone hosts to belong to the VMM Datacenter, select the Put stand-alone servers into VMM Datacenter checkbox.

    hyperv_3.png
  9. To verify the connection, select Test.