I am trying to determine the cause of errors deploying new VMs to a host. Some discussions suggested that the VMMCA might be able to shed light on the cause of the problem.
In trying to use VMMCA, I am getting several errors in the report, but I am not convinced that they represent actual problems, and I am beginning to suspect that VMMCA is perhaps outdated.
Any opinions on that?
-
The original error I am trying to eliminate is this:
Error (2915). The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server
-
In VMMCA I get this error for every server (VMM management, hosts, library):
“No required update or hotfix information exists for [server]
The VMMCA does not have a list of required hotfixes for the operating system of the specified server.
VMM may not function correctly or at all with the specified server (note that this does not apply to the VMM console, as the console can be installed in client operating systems and therefore this rule can be ignored).
If the computer is being used or will be used for any of the VMM server roles: host, library, PXE server, WSUS server, or VMM management server, ensure that it has a supported server operating system (Windows Server 2008 or a later version).”
All of the servers are running Windows Server 2012 R2 with all available updates from Windows Update.
I cannot find anywhere a list of recommended updates and hotfixes for VMM 2012 R2. So how should VMMCA be able to do this?
-
I also get this error in the VMMCA report for every host:
“The WMI virtualization store is in an unhealthy state on [server]
The Windows Management Instrumentation (WMI) virtualization store did not respond appropriately to a basic health test on the specified server.
VMM may not function correctly or at all with the specified server. You may see a "Not Responding" message in the VMM console or VMM operations on the server may fail.
Resolution:
1. Verify that the WMI service is running on the specified server by running the command net start winmgmt at a command prompt using elevated privileges
2. Ensure that the WMI virtualization store is in a healthy state on the specified server. To check the integrity of or to repair the virtualization store, run the command winmgmt /salvagerepository at a command prompt using elevated privileges
3. Ensure that all Hyper-V management services are in healthy state if the server is being used or will be used as a host. You may need to restart the following Hyper-V services: Hyper-V Virtual Machine Management, Hyper-V Image Management,
and Hyper-V Networking Management.”
With regard to the 3 steps for resolution:
- The WMI service is already running, so no point in net start.
- I do not want to run winmgmt /salvagerepository unless I am certain something is wrong. I tried winmgmt /verifyrepository which says “WMI repository is consistent”. So I think it looks ok despite the error.
- Again: I do not want to restart these services. There are vm’s running, which do important work. And I have rebooted the servers multiple times lately.
-
And finally I get this one error:
“VMM SPNs are incorrectly registered for [server name]
The Service Principal Names (SPNs) that VMM requires were not correctly registered when the VMM management server was set up on the specified server. This is a known issue in System Center 2012 – Virtual Machine Manager.
The VMM console may not be able to connect to the VMM management server and/or deploying a Hyper-V host to a bare-metal computer may not work.
Resolution:
Manually add the SPNs that are required by VMM by running the following commands as an administrator at an elevated command prompt:
1. setspn -S SCVMM/yourmachine -U domain\account
2. setspn -S SCVMM/yourmachine.fqdn.com -U domain\account”
The text mentions VMM 2012 – not VMM 2012 R2. So I am not convinced that it is a good idea to try to add the SPNs manually without verifying that something is actually wrong.