Windows Remote Management (WinRM) provides the communication services for communication between the VMM management server and the VMM Host agents. This includes inter agent communications to the following hosts:
The SCVMM 2008 R2 VMMServer service utilizes the WinRM scripting API (versus COM) for communication with the Windows Remote Management service on the managed hosts.
WinRM error messages usually provide a hex error code that is useful in understanding the problem. To resolve the hex code to error message type:
winrm helpmsg 0xXXXXXXXX
If the hex code is not preceded by ‘0x’ this command will not work.
When troubleshooting WinRM treat the process as if performing a simple network ping test. Type the command below at an elevated command prompt:
This should produce output similar to below:
ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor = Microsoft Corporation
ProductVersion = OS: 6.1.7201 SP: 0.0 Stack: 2.0
If an error is generated as opposed to the output above, perform a Quick Configuration of WinRM:
You may be prompted with something similar to below. Answer ‘Yes’ to any requests.
WinRM already is set up to receive requests on this machine.
WinRM is not set up to allow remote access to this machine for management.
The following changes must be made:
Enable the WinRM firewall exception.
Make these changes [y/n]?
WinRM has been updated for remote management.
WinRM firewall exception enabled.
WinRM can now be tested again by typing ‘winrm id’ as before.
The second half of a WinRM test establishes that the remote server has WinRM configured correctly. At an elevated command prompt type:
winrm id –r:<remoteserver>
winrm id -r:vmmr2lab-cl20
ProductVendor = Microsoft Corporation
If instead an error such as below appears, this means WinRM is not set up correctly on the remote machine, or there is something preventing communication over port 80 between the two systems. This could be a firewall or antivirus/malware programs.
Message = The WinRM client cannot complete the operation within the time spe
cified. Check if the machine name is valid and is reachable over the network and
firewall exception for Windows Remote Management service is enabled.
Error number: -2144108250 0x80338126
The WinRM client cannot complete the operation within the time specified. Check
if the machine name is valid and is reachable over the network and firewall exce
ption for Windows Remote Management service is enabled.
In this event, test local WinRM functionality on the remote system. If WinRM is configured correctly on the remote system as well the cause is most likely network communication between the two machines. Troubleshoot this as you would any network issue.
Good knowwledge. THanks
I was directed here by an alert from System Center Advisor. As far as I can tell, there are no issues with WinRM on the servers listed in the alert. Since there are no symptoms of trouble other than the advisor alerts, I have to wonder if the alerts aren't erroneous...
Same thing here Gai-jin. Everything seems to be working fine in all the testing I can do, but the alert stays.
Me three. System Center Advisor picked up our VMM couldn't WinRM to one of our Windows 2012 Hyper-V servers, yet the test above is successful. False alert?
The check in the VMM rule from Advisor is executed REMOTELY from the VMM Server against the agents. Have you configured the RunAS account like described here technet.microsoft.com/.../dn500884.aspx ?
Have you configured the RunAS account for VMM as described here technet.microsoft.com/.../dn500884.aspx ? The check is a simple
$test = Test-WSMan -ComputerName $scriptargs.AgentName;
if (!$test.ProductVersion.Contains(“Stack: 3.0″))
so it actually already looks for 3.0. I suspect something else is failing.
If you look on the right end of the Advisor alert, next to the smile/frown faces, there is a section with ‘information detected relating to this issue’ that should have some details of what went wrong during detection.