Editing: VMM Troubleshooting: Windows Remote Management (WinRM)

Title
<html> <body> 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: <ul> <li>Hyper-V Virtual Host Servers </li><li>Virtual Server Host Servers </li><li>Remote Library Servers </li></ul> 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. <table class="TableGrid1" border="1" cellspacing="0" cellpadding="0" width="98%" style="width:98%; border-collapse:collapse; border:medium none"> <tbody> <tr style="page-break-inside:avoid"> <td valign="top" style="padding:0in 4.3pt 0in 0in; background-color:transparent; width:17%; white-space:nowrap; border-color:#f0f0f0">  Tip: </td> <td valign="top" style="padding:5.75pt 5.75pt 0.1in; width:83%; background-color:#e9eff7; border-color:#f0f0f0"> 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. </td> </tr> </tbody> </table>     <a name="_Toc303153641"></a> <a name="_Toc303153641"></a> <h1><a name="_Toc303153641"></a><a name="Test_local_WinRM_functionality"></a>Test local WinRM functionality</h1>   When troubleshooting WinRM treat the process as if performing a simple network ping test. Type the command below at an elevated command prompt: winrm id This should produce output similar to below: IdentifyResponse     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: winrm qc 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.   <a name="_Toc303153642"></a> <a name="_Toc303153642"></a> <h1><a name="_Toc303153642"></a><a name="Test_remote_WinRM_functionality"></a>Test remote WinRM functionality</h1> 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> This should produce output similar to below: winrm id -r:vmmr2lab-cl20 IdentifyResponse     ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd     <a name="_Toc303153643"></a><a name="_Toc303152440"></a><a name="_Toc238017391"></a><a name="_Toc238016032">ProductVendor = Microsoft Corporation</a>     ProductVersion = OS: 6.1.7201 SP: 0.0 Stack: 2.0 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. WSManFault     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.   <a name="_Toc303153644"></a><a name="_Toc303152441"></a><a name="_Toc238017392"></a><a name="_Toc238016033">Error number:  -2144108250 0x80338126</a> 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.   </body> </html>
Comment
Tags
Please add 7 and 8 and type the answer here:

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?