Condividi tramite

Using Windows Remote Management to Troubleshoot Connectors

  • Articolo

Aggiornamento: gennaio 2010

Si applica a: Operations Manager 2007 R2

You can use Windows Remote Management (WinRM) to analyze problems with connectors.

Version

To determine the version of WinRM that is installed on your system, at a command prompt, type the following command:

winrm id

The system will return the current values.

IdentifyResponse

     ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd

     ProductVendor = Microsoft Corporation

     = OS: 5.2.3790 SP: 1.0 Stack: 1.1

The WinRM product version should be 1.1.

Error Codes

Event logs often contain WinRM numeric error codes. To get information about WinRM error codes, at the command prompt, enter the following command:

WinRM helpmsg 0x<errorcode>

Nota

You must include 0x before the error code number.

Using WinRM for Basic Troubleshooting

WinRM commands can help diagnose the following basic connector problems:

  • To skip certificate validation, use the following WinRM flags:

    -skipCNcheck

    -skipCAcheck

    If the connection succeeds without validation, you should return to the section on manually installing certificates and reinstall the certificate. If the connection fails, check that the user credentials are correct and use the ping command to make sure that the host is reachable.

  • To make sure the provider is installed and reachable, use the following WinRM queries:

    Unix: winrm identify -r:https://hostname:1270 -auth:basic -u:user -p:password -encoding:utf-8

    Windows: winrm identify -r:https://hostname:1270 -auth:basic -u:user -p:password -encoding:utf-8

    Windows (using Kerberos authentication): winrm identify -r:https://hostname:1270 -auth:kerberos -u:DOMAIN\user -p:password -encoding:utf-8

    The encoding flag must be set to UTF-8 to work properly. Use the skip flags from the certificate errors if WinRM returns security exceptions related to certificates.