Windows Remote Management Service Health Monitor

  • ID:  Microsoft.Windows.Server.6.4.OperatingSystem.WindowsRemoteManagementServiceHealth
  • Description:  Monitors the health of the Windows service for the Windows Remote Management
  • Target:  Windows Server Technical Preview Operating System
  • Enabled:  Yes

Operational States

Name State Description
Service Not Running Error The Windows Remote Management service is not running
Service Running Success The Windows Remote Management service is running

Overridable Parameters

Parameter Name Default Value Description Override
Alert only if service startup type is automatic   This may only be set to 'true' or 'false'. If set to 'false', then alerts will be triggered no matter what the startup type is set to. Default is 'true'.

Alert Details

Monitor State Message Priority Severity Auto Resolution
Service Not Running (Error) Windows Remote Management Service Stopped Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

Windows Remote Management (WinRM) service implements the WS-Management protocol for remote management. WS-Management is a standard web services protocol used for remote software and hardware management. The WinRM service listens on the network for WS-Management requests and processes them. The WinRM Service needs to be configured with a listener using winrm.cmd command line tool or through Group Policy in order for it to listen over the network. The WinRM service provides access to WMI data and enables event collection. Event collection and subscription to events require that the service is running. WinRM messages use HTTP and HTTPS as transports. The WinRM service does not depend on IIS but is preconfigured to share a port with IIS on the same machine. The WinRM service reserves the /wsman URL prefix. To prevent conflicts with IIS, administrators should ensure that any websites hosted on IIS do not use the /wsman URL prefix.

Causes

A service can stop for many reasons, including:

  • The service encountered an exception that stopped the service.

  • The service was improperly configured, which prevented it from starting.

  • The service was prevented from starting because the user account assigned to the service could not be authenticated.

Resolutions

If this service is stopped, you will not be able to remotely connect to and manage your core server. If restarting the service doesn’t resolve the issue and the Operating System is unable to boot in Normal Mode the configuration of the service may need to be updated in Safe Mode. Once in Safe Mode the service should be configured with a startup type of “Automatic” and the Log On configuration should be set to “Local System”.

The service can be restarted using the following task:

Start the Windows Remote Management service

External References
This monitor does not contain any external references.

See Also for Windows Server Operating System Management Pack


Downloads for Windows Server Operating System Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED