"Terminal Services Session Directory" Health

Microsoft.Windows.Server.2003.TerminalServicesSessionDirectoryRole.ServiceCheck (UnitMonitor)

Monitors the health of the Windows Service "Terminal Services Session Directory"

Knowledge Base article:

Summary

Terminal Services Session Directorystopped

Causes

A service can stop for many reasons, including:

The service was stopped by an administrator.

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

The service encountered an exception that stopped the service.

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

Resolutions

Check for additional service-related alerts that might have occurred concurrently. These alerts might help better identify the reason why the service entered a stopped state. Review the event logs on the managed computer, and correct any underlying problems that might have caused the service to stop unexpectedly. If applicable use task below, or Services MMC snap-in to attempt to restart the service.

Tasks Restart Terminal Services Session Directory

Element properties:

TargetMicrosoft.Windows.Server.2003.TerminalServicesSessionDirectoryRole
Parent MonitorSystem.Health.AvailabilityState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.CheckNTServiceStateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Session Directory Service not running
The Terminal Services Session Directory Service on system {0} is not running
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.2003.TerminalServicesSessionDirectoryRole.ServiceCheck" TypeID="Windows!Microsoft.Windows.CheckNTServiceStateMonitorType" Accessibility="Public" Target="Microsoft.Windows.Server.2003.TerminalServicesSessionDirectoryRole" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Enabled="onEssentialMonitoring">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.2003.TerminalServicesSessionDirectoryRole.ServiceCheck.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Error" HealthState="Error" MonitorTypeStateID="NotRunning"/>
<OperationalState ID="Success" HealthState="Success" MonitorTypeStateID="Running"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ServiceName>Tssdis</ServiceName>
</Configuration>
</UnitMonitor>