This monitor tracks the state of the Terminal Server (TermService) service and will change state depending on whether the service is running or not.
The terminal server role service relies on the Terminal Services service to be running in order to accept remote connections. Remote Desktop also relies on the Terminal Services service in order to support remote connections for administrative purposes.
To resolve this issue, start the Terminal Services service on the computer. If the problem persists, restart the computer.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To start the Terminal Services service:
On the computer, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Services pane, right-click Terminal Services, and then click Properties.
On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
Under Service status, click Start.
Click OK to close the Terminal Services Properties dialog box.
Confirm that the Status column for the Terminal Services service displays Started.
| Target | Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer | ||
| Parent Monitor | System.Health.AvailabilityState | ||
| Category | AvailabilityHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.Windows.CheckNTServiceStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
ENU <UnitMonitor ID="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.ServiceStateMonitor" Accessibility="Public" Enabled="onStandardMonitoring" Target="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" ConfirmDelivery="false">
<Category>AvailabilityHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.2008.TerminalServicesRole.Service.TerminalServer.ServiceStateMonitor_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetbiosComputerName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Running" MonitorTypeStateID="Running" HealthState="Success"/>
<OperationalState ID="NotRunning" MonitorTypeStateID="NotRunning" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>TermService</ServiceName>
<CheckStartupType>false</CheckStartupType>
</Configuration>
</UnitMonitor>