Total Number of Active Sessions

Microsoft.Windows.Server.2003.TerminalServerRole.ActiveSessions (UnitMonitor)

Monitors the total number of Active Sessions

Knowledge Base article:

Summary

The number of active user sessions for Terminal Server is outside normal operating conditions

Causes

The total number of active user sessions on the terminal server is approaching the performance limits of the computer hardware on which Terminal Server is installed.

Resolutions

To prevent this problem, configure a maximum number of active sessions allowed, based on the performance limits for the computer hardware on which Terminal Server is installed.

You can configure the maximum number of active sessions you want this terminal server to allow in Active Session limit on the Sessions tab of the Connection Properties dialog box in Terminal Services Configuration.

You can also edit this setting in the Group Policy console. In the navigation pane, open Computer Configuration, Administrative Templates, Windows Components, Terminal Services, and then Sessions. Change the properties for maximum allowed active sessions as needed.

External

For more information about allowed sessions and scaling Terminal Server on Microsoft® Windows Server™ 2003, refer to “Windows Server 2003 Terminal Server Capacity and Scaling” on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=43122.

Element properties:

Target

Microsoft.Windows.Server.2003.TerminalServerRole

Parent Monitor

System.Health.PerformanceState

Category

PerformanceHealth

Enabled

True

Instance Name

Terminal Services

Counter Name

Active Sessions

Frequency

900

Alert Generate

True

Alert Severity

Error

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

System.Performance.TwoStateBaseliningMonitorWithoutCompression

Remotable

True

Accessibility

Public

Alert Message

Terminal Services Active Sessions metric above baseline

Active Sessions metric is above the calculated baseline. Current value is {0}

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.2003.TerminalServerRole.ActiveSessions" TypeID="SystemPerf!System.Performance.TwoStateBaseliningMonitorWithoutCompression" Accessibility="Public" Target="Microsoft.Windows.Server.2003.TerminalServerRole" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Enabled="onStandardMonitoring">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.Server.2003.TerminalServerRole.ActiveSessions.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Property[@Name='Average']$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState HealthState="Success" MonitorTypeStateID="WithinEnvelope" ID="ActiveSessionsNormal"/>

    <OperationalState HealthState="Error" MonitorTypeStateID="OutsideEnvelope" ID="ActiveSessionsHigh"/>

  </OperationalStates>

  <Configuration>

    <SignatureID>Microsoft.Windows.Server.2003.TerminalServerRole.ActiveSessions.Sig</SignatureID>

    <DataSourceSettings>

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <ObjectName>Terminal Services</ObjectName>

      <CounterName>Active Sessions</CounterName>

      <InstanceName/>

      <AllInstances>false</AllInstances>

      <Frequency>900</Frequency>

    </DataSourceSettings>

    <LearningAndBaseliningSettings>

      <BusinessCycleLengthUnit>Week</BusinessCycleLengthUnit>

      <BusinessCycleLengthInGivenUnit>1</BusinessCycleLengthInGivenUnit>

      <LearningType>Continuous</LearningType>

      <Offset1>3</Offset1>

      <Offset2>3</Offset2>

      <Offset3>3</Offset3>

      <LearningRate>2.33</LearningRate>

      <InitialNoAlertPeriodInBizCycles>1</InitialNoAlertPeriodInBizCycles>

      <OuterSensitivity>3.31</OuterSensitivity>

      <InnerSensitivity>2.81</InnerSensitivity>

    </LearningAndBaseliningSettings>

    <SignatureCollectionSettings>

      <DBUpdatePeriodInSeconds>900</DBUpdatePeriodInSeconds>

    </SignatureCollectionSettings>

  </Configuration>

</UnitMonitor>