Home
  •  

Windows services not running on remote computer

Microsoft.SystemCenter.AgentManager.ServicesNotRunning.Monitor (UnitMonitor)

Monitor for when Windows services required for the management server to remotely install an agent are not running.

Knowledge Base article:

Summary

One or more services required by the Management Server to remotely install the agent are not running.

Causes

To remotely install an agent, the following services are required to be started on the target computer:

Display Name

Windows Service Name

Windows Management Instrumentation

WinMgmt

Remote Procedure Call (RPC)

Rpcss

Remote Registry

RemoteRegistry

Windows Installer

MSIServer

Resolutions

If any of the above are not running or their Start Type is set to Disabled, start them up and run the Discovery Wizard again.

For more information on troubleshooting agent installation, see Troubleshooting Issues When You Use the Discovery Wizard to Install an Agent(http://go.microsoft.com/fwlink/?LinkId=181932).

Element properties:

TargetMicrosoft.SystemCenter.AgentManager
Parent MonitorMicrosoft.SystemCenter.AgentManager.ConfigHealthRollup
CategoryConfigurationHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.SystemCenter.AgentManager.AgentManagerFailureMonitor
RemotableTrue
AccessibilityPublic
Alert Message
Failed Agent Push/Repair - Windows Services not running on remote computer
An agent "push" install or repair was attempted and failed. The task was run from the management server {1} against the computer {0}.

Additional details:
Task Start Time: {3} UTC
Task End Time: {4} UTC

Full Event Description: {5}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SystemCenter.AgentManager.ServicesNotRunning.Monitor" Accessibility="Public" Enabled="true" Target="SCLibrary!Microsoft.SystemCenter.AgentManager" ParentMonitorID="Microsoft.SystemCenter.AgentManager.ConfigHealthRollup" Remotable="true" Priority="Normal" TypeID="Microsoft.SystemCenter.AgentManager.AgentManagerFailureMonitor" ConfirmDelivery="true">

  <Category>ConfigurationHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SystemCenter.AgentManager.ServicesNotRunning.Monitor.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.UserActionManager"]/TargetDevicePrincipalName$</AlertParameter1>

      <AlertParameter2>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.UserActionManager"]/ManagementServerName$</AlertParameter2>

      <AlertParameter3>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.UserActionManager"]/PendingStateType$</AlertParameter3>

      <AlertParameter4>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.AgentManager"]/TaskStartTime$</AlertParameter4>

      <AlertParameter5>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.AgentManager"]/TaskEndTime$</AlertParameter5>

      <AlertParameter6>$Data/Context/Property[@Name="Message"]$</AlertParameter6>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="AgentManagerFailure" MonitorTypeStateID="AgentInstallationFailure" HealthState="Error"/>

    <OperationalState ID="AgentManagerSuccess" MonitorTypeStateID="AgentInstallationSuccess" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <EventId>10606</EventId>

    <TaskStartTime>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.AgentManager"]/TaskStartTime$</TaskStartTime>

    <TaskEndTime>$Target/Property[Type="SCLibrary!Microsoft.SystemCenter.AgentManager"]/TaskEndTime$</TaskEndTime>

  </Configuration>

</UnitMonitor>