VMM Host Not Responding Rule

1

WS-Management, also known as Windows Remote Management (WinRM), is stopped on the host.

2

A pre-release version of Hyper-V is running on the host. VMM 2008 only works with the released version of Hyper-V.

3

The virtualization service (either Hyper-V or Virtual Server) is not present on the host, or the service is stopped.

4

The machine account for the VMM server is not in the local Administrators group on the host computer.

5

The machine account for the VMM server is not in Virtual Machine Manager Servers group on host computer.

6

Windows Firewall is enabled on the host computer, and the following firewall exceptions have not been added:

• Port exceptions - HTTP (80), HTTPS (443) (These are the default port assignments for HTTP and HTTPS and may differ from the ports that are in use.)

• Program exception - VMMAgent

7

The WinRM listener is not present or is not listening on all IP addresses on the host. This can happen if WS-Management is uninstalled and then re-installed.

8

A proxy server is preventing communication with the host.

9

The SCVMM user and group have been removed for a host in a perimeter network or a host in a non-trusted Active Directory domain.

10

The WMI store has been corrupted.

11

DNS name resolution issues are preventing communication.

12

Kerberos authentication issues are preventing communication.

1

Ensure that you can connect to the host computer from the VMM server.

2

Ensure that the Virtual Machine Manager Agent service and the WS-Management service (formerly known as WinRM) are running on the host computer. If not, restart the services.

3

Ensure that Hyper-V or Virtual Server is installed on the host computer, and that the Virtual Server service is running.

4

If Hyper-V is installed and running on the server, update Hyper-V to KB956589. To download the update, go to Hyper-V Update for Windows Server 2008 x64 Edition (KB956589) (http://go.microsoft.com/fwlink/?LinkId=113199).

5

Ensure that the machine account for the VMM server is in the following groups on the host computer:

• Administrators

• Virtual Machine Manager Servers

6

If Windows Firewall is enabled on the host computer, check whether the following firewall exceptions have been added. Location: Control Panel\Windows Firewall, Exceptions tab.

• Port exceptions - HTTP (80), HTTPS (443) (These are the default ports, and may not be the ports that you are using.)

• Program exception - VMMAgent

7

Check whether the WinRM listener is present on the host computer. To do this, enter the following at a command prompt:

winrm enum winrm/config/listener

If WinRM is present, the command returns something like this:

Address = *

Transport = HTTP

Port = 80 (Default port used here.)

HostnameEnabled = true

URLPrefix = wsman

CertificateThumbprint

ListeningOn = 127.0.0.1, 172.30.190.61 (All IP addresses of the host)

8

If you updated any configurations in steps 4-6, you must uninstall and re-install the Virtual Machine Manager agent on the host.

9

Remove the Virtual Machine Manager agent locally on the host computer by using Add or Remove Programs in Control Panel.

10

Reinstall the Virtual Machine Manager agent on the host:

• If the host is in a trusted Active Directory Domain Services (AD DS) domain, from any view in the VMM Administrator Console, click Add hosts in the Actions pane, and follow the wizard instructions to add the host to VMM.

• If the host is on a perimeter network, install the Virtual Machine Manager agent locally on the host computer, and then add the host to VMM by using the Add hosts action. For agent installation instructions, see Installing the VMM Agent Locally (http://go.microsoft.com/fwlink/?LinkId=121006) in the Microsoft TechNet Library.

11

If the host is still not available, refresh the host in Virtual Machine Manager. To do this, in the VMM Administrator Console, display Hosts view, select the host, and then click Refresh in the Actions pane.

12

To download the released version of Hyper-V, open http://go.microsoft.com/fwlink/?LinkId=113199.

13

To check the integrity of or repair the host WMI repository, run the following command:

winmgmt /salvagerepository

14

To check your host's WMI virtualization store, do the following:

a. Start Wbemtest while using a local Administrator account on the host computer.

b. Connect to \\hostname\root\virtualization.

c. Try the following query,] and see whether it succeeds: select * from msvm ComputerSystem</host>

15

To check your host's WMI namespace security settings:

a. Open Server Manager, click Configuration, right-click WMI Control, and then select Properties.

b. To review the security settings, on the Security tab, select SCVMM, and click Security Settings. Ensure that both the Administrators group and the Virtual Machine Manager Service have full rights on the namespace.

16

To check the status of WinRM, run the following command: winrm qc

17

To check whether the WinRM listener is running, enter one of the following commands:

* To get only the listener configuration, enter: winrm enum winrm/config/listener

To get the entire WinRM configuration, enter: winrm get winrm/config

18

To check whether the VMM agent is responding to WinRM calls, run the following command:

winrm invoke GetVersion wmi/root/scvmm/AgentManagement -r:http://<host> @{}

19

To manually restart the VMM Server service, enter the following commands:

net stop vmmservice

net start vmmservice

20

To manually restart the VMM Agent service on the host, enter the following commands:

net stop vmmagent

net start vmmagent

21

To manually restart the Hyper-V service, enter the following commands:

net stop vmms

net start vmms

22

To find out whether the DNS name resolution service is working as expected, enter the following command: nslookup <hostname>|<IP address>]

The FQDN should match the FQSDN registered in Active Directory.