How To Configue Microsoft Virtual Machine Manager (VMM) server for use with VMTurbo Operations Manager

This article gives a brief description of the configuration changes required to be made on a Windows VMM server so that the properties and objects needed by VMTurbo Operations Manager (OpsMan) can be fetched.

VMTurbo uses a library called Overthere which in turn uses the Windows Remote Management (WinRM) protocol to access the VMM server.  More info on Overthere can be found at: https://github.com/xebialabs/overthere

  • Windows Remote Management (WS-Management) service is setup to be started by default. Check if this is the case and that the service is running.

 

  • If you are running a Windows Server version earlier than Windows Server 2012 R2 for the VMM server, you will need to apply the hotfix referenced in this KB article:  http://support.microsoft.com/kb/2842230

 

  • On the remote host, open a Command Prompt using the Run as Administrator:
> winrm quickconfig
> y
> winrm set winrm/config/service/Auth @{Basic="true"}
> winrm set winrm/config/service @{AllowUnencrypted="true"}
> winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}
Note: The Windows Firewall needs to be running to run the above command. See Microsoft Knowledge Base article #2004640.

  • When the above commands are run a SPN must be setup of the form. A list of SPNs can be obtained using the command setspn -l <vmm-server-name>
PROTOCOL/ADDRESSWINDOWS-HOST
Example: WSMAN/10.99.9.2 VMM-02

If this is not set we need to setup an SPN by running the command

setspn -A PROTOCOL/ADDRESS:PORTWINDOWS-HOST
Example: setspn –A WSMAN/10.99.9.2 VMM-02
Note: PORT is optional

         The IP address should be used for the above commands - not the DNS name. If you have failover setup for the VMM nodes, please use the IP  and name of the cluster in the above command, and add VMM target to VMTurbo appliance use the IP of the cluster.

Additional Notes:

  • Time Synchronization is also extremely important. Please make sure it is synchronized between the VMTurbo appliance and the VMM server.
  • The WinRM/WSMAN protocol uses the 5985 and 5986 TCP ports, so if there is a firewall between the OpsMan and the VMM server, you need to open those ports in order to establish the connection.

 

Have more questions? Submit a request

Comments