SPI for Terminal Server User`s Guide

HERMES SoftLab
Microsoft Terminal Server
SMART Plug-In for HP
OpenView Operations/
Windows
(SPI for Terminal Server)
Version 01.00
________
User’s Guide
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Document Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Edition History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Before Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Product Web Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapters Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About Microsoft Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Typical Enterprise Setup of Terminal Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About SPI for Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
High-Level Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Quick Introduction to SPI for Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Service Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Setting Up the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
i
Setting Up the Terminal Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Autodiscovery of the Terminal Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Launching Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Deploying Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Verifying the Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuring Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Assigning Policies and Collecting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Managing Terminal Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
About Managing Microsoft Terminal Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Managing Terminal Server Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Setting Up Terminal Server Services Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Service Monitoring Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Windows Event Log Forwarding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Managing Terminal Server Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Setting Up Terminal Server Sessions Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Session Resource Consumption Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Session Network Issue Detection Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitoring Session State Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Session Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interacting with Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
34
34
35
35
Managing Windows User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Setting up Windows User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Monitoring Windows User Profile Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
ii
User Guide
Contents
Monitoring for Presence of Specific File Categories in Windows User Profiles . . . . . . . . . . . . . . . . . . . 40
Viewing Windows User Profile Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Managing Terminal Server Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Setting Up Terminal Server Servers Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Monitoring Terminal Server Logon State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Managing Terminal Server Logon State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Managing Terminal Server User Logon Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting Up Terminal Server User Logon Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
How it works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Monitoring User Logon Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Viewing User Logon Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Managing Terminal Server Service Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Setting Up Terminal Server Service Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Generating Terminal Server Service Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Collecting Terminal Server Performance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Terminal Server Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Managing License Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
About Managing Microsoft Terminal Server License Servers . . . . . . . . . . . . . . . . . . . . 52
Managing Terminal Server License Server Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Setting Up Terminal Server License Server Services Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
i
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Service Monitoring Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Windows Event Log Forwarding Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Interacting with Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Managing Terminal Server License Server Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Setting Up Terminal Server License Server Licenses Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Monitoring License Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Viewing License Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Managing Terminal Server License Server Service Map . . . . . . . . . . . . . . . . . . . . . . . . . 59
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Setting Up Terminal Server License Server Service Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Collecting Terminal Server License Server Performance Information . . . . . . . . . . . . . 61
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Terminal Server License Server Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Maintaining SPI for Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
About Maintaining Microsoft Terminal Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
SPI for Terminal Server Requirements and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPI for Terminal Server Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing SPI for Terminal Server Subagent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating SPI for Terminal Server Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the SPI for Terminal Server Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing the SPI for Terminal Server Files from the Managed Node . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
User Guide
65
66
67
67
67
68
Contents
Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
SPI for Terminal Server Tools and Tool Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
TSSPI-SPI Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
TSSPI-SPI Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
TSSPI-SPI Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
TSSPI-SPI Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
TSSPI-SPI Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
TSSPI-SPI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
TSSPI-Terminal License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TSSPI-TLS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TSSPI-TLS Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
TSSPI-TLS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
TSSPI-Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
TSSPI-TS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
TSSPI-TS Session Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
TSSPI-TS Disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
TSSPI-TS Send Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
TSSPI-TS Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
TSSPI-TS Logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
TSSPI-TS Logon Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
TSSPI-TS Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
TSSPI-TS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
SPI for Terminal Server Policies and Policy Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Scheduled Task Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
TSSPI-LogLicenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
TSSPI-LogProfile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
TSSPI-LogProfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
TSSPI-LogServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
TSSPI-LogSessInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
TSSPI-LogSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
TSSPI-LogUserLogonProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Windows Event Log Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
TSSPI-FwdOsAndTSAppInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI-FwdOsAndTSAppWarnError . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI-FwdOsAndTSSysInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI-FwdOsAndTSSysWarnError . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI-FwdTlsSysInfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI-FwdTlsSysWarnError . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
85
85
86
86
87
Open Message Interface Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
TSSPI-Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Measurement Threshold Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
v
TSSPI-ChkLogonState . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
TSSPI-ChkOsAndTSServices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
TSSPI-ChkProfileExecutableCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
TSSPI-ChkProfileFileCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
TSSPI-ChkProfileFullSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
TSSPI-ChkProfileMediaCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
TSSPI-ChkProfileRoamingFileCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TSSPI-ChkProfileRoamingSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TSSPI-ChkProfilesTotalExecutableCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TSSPI-ChkProfilesTotalFileCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
TSSPI-ChkProfilesTotalMediaCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
TSSPI-ChkProfilesTotalRoamingFileCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
TSSPI-ChkProfilesTotalRoamingSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
TSSPI-ChkProfilesTotalSize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
TSSPI-ChkRDPListenerSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
TSSPI-ChkRequirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
TSSPI-ChkSessionHandleCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
TSSPI-ChkSessionPageFileBytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
TSSPI-ChkSessionProcessorTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
TSSPI-ChkSessionThreadCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
TSSPI-ChkSessionTotalBytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
TSSPI-ChkSessionTotalErrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
TSSPI-ChkSessionTotalFrames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
TSSPI-ChkSessionTotalTimeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
TSSPI-ChkSessionTotalTransportErrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
TSSPI-ChkSessionWorkingSet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
TSSPI-ChkSessionsActive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
TSSPI-ChkSessionsAll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
TSSPI-ChkSessionsInactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
TSSPI-ChkTSServicePortProbing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
TSSPI-ChkTls50Dev2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
TSSPI-ChkTls50Temp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
TSSPI-ChkTls52Dev2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
TSSPI-ChkTls52Dev2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
TSSPI-ChkTls52Temp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
TSSPI-ChkTls52User2003 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
TSSPI-ChkTlsService . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
TSSPI-ChkUserLogonProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
TSSPI-ChkUserLogonProcessCompleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
TSSPI-ChkUserLogonProcessPh1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
TSSPI-ChkUserLogonProcessPh2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
TSSPI-ChkUserLogonProcessPh3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
TSSPI-DscServiceModel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
SPI for Terminal Server Reports and Report Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Metric Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
TSSPI_PSLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
TSSPI_SESSINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
vi
User Guide
Contents
TSSPI_SESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI_PROFILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI_LIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI_SRV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSSPI_PROFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
106
106
107
107
108
Report Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
TS - User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - Top Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - Top Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - User Logon Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TLS - Terminal Server Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - Top Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TS - Threshold Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
108
109
110
110
111
111
111
112
112
Autogroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Product Terminal Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
SPI for Terminal Server Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Terminal License Server (Win2003) - License Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Terminal Server - User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Terminal Server - User Logon Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Terminal Server - Session Resource Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Terminal Server - Active Session Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Terminal Server - Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Terminal Server - User Logon Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Terminal License Server (Win2000) - License Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Troubleshooting Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
v
viii
User Guide
Notices
The information contained in this document is subject to change without notice.
HERMES SOFTLAB D.D. PROVIDES THIS MATERIAL "AS IS" AND MAKES
NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. HERMES SOFTLAB D.D.
SHALL NOT BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR
INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH
THE FURNISHING, PERFORMANCE OR USE OF THIS MATERIAL WHETHER
BASED ON WARRANTY, CONTRACT, OR OTHER LEGAL THEORY.
Trademarks
This document contains proprietary information, which is protected by
copyright. All rights are reserved. No part of this document may be photocopied,
reproduced or translated to another language without the prior written consent of
HERMES SoftLab d.d.
HP® and OpenView® are registered trademarks of the Hewlett-Packard
Company in the United States and other jurisdictions.
Microsoft®, Windows®, Windows® 2000, Windows® 2003, and Windows NT®
are registered trademarks of Microsoft Corporation in the United States and/or
other countries.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Solaris Operating Environment, Java, and all Java-based trademarks are
trademarks of Sun Microsystems, Inc. in the United States, other countries, or
both.
IBM® and AIX® are registered trademarks of the IBM Corporation.
All other product names are the property of their respective trademark or service
mark holders and are hereby acknowledged.
ix
HERMES SoftLab d.d.
Litijska 51
SI-1000 Ljubljana
Slovenia, Europe
www.hermes-softlab.com
© Copyright HERMES SoftLab d.d. 2006
x
User Guide
Chapter 1
Document Overview
Edition History
New editions are complete revisions of the manual. The printing dates for each
edition are listed below.
2
Edition
Date
Product Version
First Edition
September 2006
01.00
Installation and Configuration Guide
Conventions
The following typographical conventions are used in this manual:
Font
Definition
Example
Italic
Product names, book or manual titles, Refer to the SPI for Terminal Server
man page names, and section, table,
User’s Guide for additional
and figure titles.
information.
Emphasis.
You must follow these steps.
Window and dialog box names.
From the Deploy policies on… window,
select a node.
Bold
Commands on menus and buttons,
dialog box titles and options, menu
and icon names.
Select SPI for Terminal Server and
click OK.
Computer
File names, syntax, directory names, or The following file is located on the root
text that should be entered on screen directory of the SPI for Terminal
or that is displayed on the monitor.
Server installation CD: tsspireadme.txt.
Document Overview
3
Product Documentation
With SPI for Terminal Server, the following documentation is provided:
•
•
•
•
•
4
HERMES SoftLab Microsoft Terminal Server SMART Plug-In for HP OpenView
Installation and Configuration Guide
Installation and Configuration Guide is available in printed and PDF format
(TSSPI-InstallGuideWIN.pdf).
HERMES SoftLab Microsoft Terminal Server SMART Plug-In for HP OpenView
User’s Guide
User’s guide is available in printed and PDF format (TSSPI-UserGuideWIN.pdf).
Release notes
Release notes are available in TXT format (tsspi-release-notes-win.txt).
Readme
Readme file is available in TXT format (tsspi-readme.txt).
HERMES SoftLab license and support terms file
License file is available in TXT format (hsl_software_license_support_terms.txt)
Installation and Configuration Guide
Customer Support
Use the following e-mail and Web page addresses if you need help with the licensing
process or while using the product, and if you would like additional information
about this or other HERMES SoftLab products.
Licensing
To obtain the license activation file you can visit HERMES SoftLab licensing portal:
http://spi.hermes-softlab.com/licensing/
or send an e-mail to the following address:
spi-licensing@hermes.si
For more information on licensing and licensing procedure refer to the Licensing
chapter in the SPI for Terminal Server Installation and Configuration Guide.
If you encounter any problems with the licensing process, contact the HERMES
SoftLab licensing department at:
spi-licensing@hermes.si
Contacting Support
IMPORTANT
Should you require additional assistance or information while using the product,
contact your vendor.
If you have purchased the software directly from HERMES SoftLab, send e-mail to:
support-tsspi@hermes.si
Before Contacting Support
Before you contact the support department, have the following information available
so that a technical support analyst can work on your problem more efficiently:
•
the support file tsspi_supp.zip
To create the support file tsspi_supp.zip, run the TSSPI-Collect Support
Information tool on one or more nodes. To run the tool, perform the following
steps:
Document Overview
5
1. Go to Tools/SPI for Terminal Server /TSSPI-Maintenance/TSSPI-Support
tools group and run the TSSPI-Collect Support Information tool. The Select where
to launch this tool window opens.
2. Select the node(s) and click Launch to run the tool. The files with the support
information are created in the following directory on the node(s):
%OvAgentDir%\tsspi\
•
•
•
•
symptoms
sequence of events leading to the problem
commands and options that you used
messages you have received (a description with the time and date)
General Information
For marketing or business-related issues in reference to this or other HERMES
SoftLab SPIs, send e-mail to:
spi-info@hermes-softlab.com
Product Web Sites
Visit HERMES SoftLab SMART Plug-In Web site at:
http://www.hermes-softlab.com/products/SPI/about_SPI.html
and the company Web site at:
http://www.hermes-softlab.com/
6
Installation and Configuration Guide
Chapters Summary
This guide describes how to use HERMES SoftLab Microsoft Terminal Server
SMART Plug-In for HP OpenView to monitor and manage Microsoft Terminal
Server and related components from the HP OpenView environment. It also
addresses and troubleshoots some of the problems you may encounter while using
the product.
NOTE
This document assumes that you are familiar with the HP OpenView Operations
administration procedures and concepts.
The guide contains the following chapters:
•
“Getting Started” on page 9
This chapter contains the basic information about the Terminal Server
environment, and an overview of the SPI for Terminal Server functionality.
•
•
•
•
•
•
“Setting Up the Environment” on page 19
This chapter provides instructions on how to perform elementary tasks to set up
and use SPI for Terminal Server.
“Managing Terminal Servers” on page 25
This chapter provides instructions for monitoring and managing Terminal
Servers.
“Managing License Servers” on page 51
This chapter provides instructions for monitoring and managing Terminal Server
License Servers.
“Maintaining SPI for Terminal Server” on page 63
This chapter provides instructions for maintaining SPI for Terminal Server.
“Quick Reference” on page 69
This chapter contains reference information for SPI for Terminal Server
components.
“Troubleshooting” on page 121
This chapter describes known problems that can occur when using SPI for
Terminal Server, and procedures for their resolution or workaround.
Document Overview
7
8
Installation and Configuration Guide
Chapter 2
Getting Started
About Microsoft Terminal Server
With Windows Terminal Server you can deliver Windows-based applications, or the
Windows desktop itself, to any computing device - including those that cannot run
Windows.
When a user runs an application on Terminal Server, the application execution takes
place on the server, and only keyboard, mouse and display information is
transmitted over the network. Each user sees only his or her individual session,
which is managed transparently by the server operating system, and is independent
of any other client session.
Windows 2003 server running Terminal Server uses a specially-modified kernel to
allow many users to connect to the server simultaneously - each running his own
unique virtual desktop. A single server can support dozens or even hundreds of
users. Load-balancing techniques allow a group of servers to provide virtual
desktops to thousands of simultaneous users.
Server-based computing environment consists of three main components:
10
•
a multi-user operating system (Terminal Server)
•
a remote presentation protocol (Remote Desktop Protocol or RDP)
•
client software and devices
User’s Guide
Typical Enterprise Setup of Terminal Server Environment
Typical enterprise setup of Terminal Server environment consists of the following
components:
•
Client devices
•
Network connections
•
SPI for Terminal Server Licensing Server
•
Terminal Servers
•
User and application data
Getting Started 11
About SPI for Terminal Server
HERMES SoftLab Microsoft Terminal Server SMART Plug-In for HP OpenView (SPI
for Terminal Server) is designed specifically for use with Terminal Server products
in HP OpenView environments. SPI for Terminal Server in combination with HP
OpenView Operations for Unix provides the first power-user grade management
solution. It enables you to monitor and manage the Terminal Server environments
using graphical representations of environment architecture, and service oriented
representations of hierarchical dependencies and business impact of Terminal
Server components, their failures, or performance degradations.
With SPI for Terminal Server you can proactively and securely manage a distributed
Terminal Server environment from one, centralized point. Additional benefits
include the following:
•
•
•
12
Non-stop availability – Terminal Server and License servers are monitored for
availability, performance, and license utilization. End-user sessions consuming
excessive amounts of resources are identified, exposing the underlying offending
processes. The user logon process is monitored as it goes through a number of
logon phases, allowing early detection of logon issues. User profiles are
monitored for size and age. All these events can be linked to automatic email/
paging alerting or automatic counteraction such as resetting a session,
terminating a process, or even rebooting a server.
Scalability – SPI for Terminal Server integrates with the HP OpenView family,
which is itself designed for large corporate environments. Autodiscovery, top
reports, and mass commands all simplify manageability as the Terminal Server
environment increases.
End-to-end – Terminal Server management within the OpenView environment
covers back-end applications, network equipment, as well as full OS and
hardware management. Databases, routers, SAP applications, and Terminal
Servers are all examples in the chain of service level delivery for an ERP system.
The OpenView family of solutions automatically integrates the individual point
solutions for each link into full end-to-end managed service.
User’s Guide
High-Level Architecture
Below is the high-level diagram of SPI for Terminal Server architecture.
Getting Started 13
Quick Introduction to SPI for Terminal Server
The main components of SPI for Terminal Server include the following:
•
HP OpenView Operations/Windows Policies
•
HP OpenView Operations/Windows Tools
•
HP OpenView Operations/Windows Reports
•
HP OpenView Operations/Windows Service Map
•
HP OpenView Operations/Windows Graphs
Although these components are discussed in detail in the chapters that follow, a
brief description of each is listed below.
Policies
Policies instruct HP OpenView Operations for UNIX engines how to solve system
management issues, for example, “Monitor CPU Utilization”.
SPI for Terminal Server policies enable you to define complex rules and instructions
for monitoring different systems and services. policies are instructions for HP
OpenView Operations (OVO) agents that monitor your Terminal Server
environment. When an issue is detected, a message is sent to the HP OpenView
Operations (HP OVO) console.
In addition, you can define automated actions to be performed upon detecting a
specific issue, or include instructions for operators as part of the message. Every
policy can start automatic or operator initiated action when issue is detected. You
can check which actions were launched when issue was detected, and check the
action outcome in the message annotation.
SPI for Terminal Server policies enable you to perform the following tasks:
14
•
monitor availability and internal issues of Terminal Servers and License Servers
•
monitor session resource consumption
•
monitor Terminal Server license use
•
monitor user logon process
•
monitor RDP listener session
•
monitor user profiles
User’s Guide
Tools
SPI for Terminal Server supplies powerful tools for monitoring and managing your
Terminal Server environment. SPI for Terminal Server tools enable you to inspect,
analyze, and manage your Terminal Server environment, check the current status of
the environment, and react to issues in your environment.
SPI for Terminal Server tools enable you to perform the following tasks:
•
manage Terminal Server sessions
•
manage Terminal Server and License Server services
•
•
monitor sessions, services, applications, and all components of your Terminal
Server environment
perform discovery of your Terminal Server environment and update the
Terminal Server service model
•
troubleshoot the SPI for Terminal Server installation and configuration
•
display session info, top processes in session, and so on
•
display Terminal Server license use
•
manage Terminal Server and License Server nodes
Reports
SPI for Terminal Server also offers report functionality, where collected performance
data can be represented in web-based reports. SPI for Terminal Server integrates HP
OpenView Reporter and with reporting component embedded within HP OpenView
Operations for Windows. You can generate reports on the following information:
•
•
•
Logon/logoff activity on server level
Detailed user activity (list of sessions, duration of each session, CPU, memory,
and swap usage of each session)
Threshold assistant reports that help you adjust monitoring policies to your
Terminal Server environment
•
Terminal Server License use
•
Windows user profile size and contents
•
Top users in terms of system resource consumption
•
User logon process statistics
Getting Started 15
Service Map
SPI for Terminal Server provides support for HP OpenView Operations / Windows
service map. It automatically generates a Terminal Server service map of the
Terminal Server enterprise configuration, which offers complete graphical
representation of your Terminal Server environment and its hierarchical
organization.
In addition, graphical representation of your Terminal Server environment clearly
indicates relations between Terminal Server environment components, how they
impact one another, and which business services are affected. This enables you to
effectively manage services within your information technology framework.
Example of a service map view:
16
User’s Guide
Graphs
SPI for Terminal Server also offers graph functionality, where collected performance
data can be represented in near real-time graphs. SPI for Terminal Server integrates
with HP OpenView Performance Manager and with graphing component embedded
within HP OpenView Operations for Windows. You can generate graphs displaying
the following information:
•
•
Resource consumption of Terminal Server sessions (CPU, virtual and physical
memory, network traffic and errors, handles, threads)
Number of active sessions compared to total Terminal Server resource
consumption
•
Number of active / disconnected / all sessions on a Terminal Server system
•
Terminal Server License consumption (temporary, per device, per user)
•
•
User profile information on a Terminal Server system (size, number of executable
/ media files)
User logon process information (duration of individual phases / complete logon
process)
Getting Started 17
18
User’s Guide
Chapter 3
Setting Up the Environment
Setting Up the Terminal Server Environment
SPI for Terminal Server enables you to monitor and manage your Terminal Server
environment from one, centralized point. For this purpose Terminal Servers and
Terminal Server License Servers are added as managed nodes on the HP OpenView
Operations management server.
Setting up your Terminal Server environment involves installing, licensing, and
configuring SPI for Terminal Server on the HP OVO management server and on the
managed nodes. For more information on how to install managed nodes, refer to SPI
for Terminal Server Installation and Configuration Guide.
When you successfully configured your environment, you can start using the SPI for
Terminal Server product. For procedural information on how to:
•
•
•
•
20
perform autodiscovery of Terminal Server components and update your
configuration, refer to “Autodiscovery of the Terminal Server Environment” on
page 21
launch SPI for Terminal Server tools on managed nodes, refer to “Launching
Tools” on page 22
deploy SPI for Terminal Server policies on managed nodes, refer to “Deploying
Policies” on page 23
configure SPI for Terminal Server reporting functionality, refer to “Configuring
Reports” on page 24
User’s Guide
Autodiscovery of the Terminal Server Environment
SPI for Terminal Server is able to visualize Terminal Servers and Terminal Server
License Servers in an HP OpenView Operations for Windows service map.
Perform the following steps to generate SPI for Terminal Server service map:
1. Login to your Windows machine where the HP OpenView Operations for
Windows console is installed as the user administrator.
2. Select Policy management and Policy groups. Then, select SPI for Terminal
Server.
3. Depending on the type of the node (Terminal Server or Terminal Server License
Server node) and the version of the operating system (Windows 2000 server,
Windows server 2003), select one of the following policy groups:
•
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Discovery
•
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Discovery
•
TSSPI-TS License Server 5.0 (Win2000) / TSSPI-TLS50 Discovery
•
TSSPI-TS License Server 5.2 (Win2003) / TSSPI-TLS52 Discovery
4. From the right window pane, select and right-click the TSSPI-DscServiceModel
policy.
5. From the menu displayed next, select All Tasks… and then Deploy on. The Deploy
policies on…window opens.
6. From the Deploy policies on…window, select the node(s) on which you want to
deploy the policy. When your selections have been made, press OK and wait for
deployment to finish.
7. Select Tools, then select SPI for Terminal Server.
8. Depending on the type of the node (Terminal Server or Terminal Server License
Server node), select one of the following tools:
•
TSSPI-Terminal Server / TSSPI-TS Discovery
•
TSSPI-Terminal License Server / TSSPI-TLS Discovery
9. Launch the tool TSSPI-Autodiscovery against the server and in a few moments
the server should appear in service map under Services / Applications / SPI for
Terminal Server.
Setting Up the Environment 21
Launching Tools
SPI for Terminal Server implements many HP OpenView Operations for Windows
tools. To start a selected tool on a selected node, perform the following steps:
1. From the HP OpenView Operations GUI, choose Tools, TSSPI-Terminal Server,
and then a tool group, for example, TSSPI-TS Services.
2. In the right window pane, double-click the tool that you want to launch, for
example, TSSPI-Start Netlogon Service. A Select where to launch this tool window
opens.
3. From the Select where to launch this tool window, select the node(s) on which to
launch the tool.
4. Press Launch… and wait for the tool to launch.
22
User’s Guide
Deploying Policies
Policies instruct HP OpenView Operations engines how to solve system
management issues, for example, “Monitor CPU Utilization”. Additionally, when a
specific system event occurs, policies can generate HP OpenView Operations
messages. These messages then trigger automatic or operator-initiated actions.
Follow the steps in this section to deploy policies to nodes. Note that the
Administrator should also customize the thresholds within the policies.
1. In the HP OpenView Operations for Windows console, select Policy management
followed by selecting Policies group and TSSPI-Terminal Server. Then, select the
policy group to deploy, for example, TSSPI-TS50 Quick Start.
2. From the right window pane, select and right-click the policy to deploy
3. From the menu displayed next, select All Tasks… followed by selecting Deploy
on. The Deploy policies on… window opens.
4. From the Deploy policies on… window, select the node(s) on which you want the
policy deployed and check your deployment options. Click OK.
5. Wait for deployment to finish. You can observe deployment in the Deployment jobs
tree.
NOTE
SPI for Terminal Server policies are logically grouped together under the SPI for
Terminal Server policy group. For example, you can deploy policies in the Quick
Start group to get started quickly with the SPI for Terminal Server.
Verifying the Deployment
To check which policies are deployed on a specific node, perform the following
steps:
1. In the HP OpenView Operations for Windows console, select Nodes and then
select and right-click a node. A menu opens.
2. From the menu, select View and then Policy inventory. A list of all deployed
policies is displayed.
Setting Up the Environment 23
Configuring Reports
SPI for Terminal Server integration with HP OpenView Reporter requires that the
following actions have occurred before you install reports on a system:
•
•
The HP OpenView Reporter is installed on the same system as the HP OpenView
Management server or it is installed as a standalone system, and the Reporter
Service is running.
An HP OpenView Operations Agent 7.x is installed on the Managed Nodes for
which you want to generate reports.
Assigning Policies and Collecting Performance Data
To produce reports, policies must be assigned. All policies related to collecting
performance data are grouped together under the following policy group: SPI for
Terminal Server…TSSPI-T(L)Sxx Data Collection. Once policies are successfully
installed on the agent, the Embedded Performance Agent (CODA agent) begins to
collect performance data for sessions, services processes, and published applications
at regular intervals. For all Terminal Server systems where CODA agents are
collecting data, HP OpenView Reporter can be used to generate reports.
24
User’s Guide
Chapter 4
Managing Terminal Servers
About Managing Microsoft Terminal Servers
Managing Terminal Server environment involves the following:
26
•
“Managing Terminal Server Services” on page 27
•
“Managing Terminal Server Sessions” on page 31
•
“Managing Windows User Profiles” on page 37
•
“Managing Terminal Server Servers” on page 42
•
“Managing Terminal Server User Logon Process” on page 44
•
“Managing Terminal Server Service Map” on page 47
•
“Collecting Terminal Server Performance Information” on page 49
User’s Guide
Managing Terminal Server Services
Managing Terminal Server services involves monitoring and handling the following
software items:
•
•
Terminal Server and related Windows OS services
System and Application event-logs messages related to Terminal Server and
related Windows OS services
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting Up Terminal Server Services Management” on page 27)
which policies are needed for monitoring Terminal Server services
(refer to “Policies” on page 28)
which tools are needed for managing Terminal Server services
(refer to “Tools” on page 28)
Setting Up Terminal Server Services Management
To monitor and manage Terminal Server services, deploy the policies to all managed
nodes. Based on the Windows Terminal Server version, use the following policy
groups:
•
•
on Windows 2000 Terminal Server
deploy the TSSPI-TS50 Quick Start policy group
on Windows 2003 Terminal Server
deploy the TSSPI-TS52 Quick Start Services policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Managing Terminal Servers 27
Policies
To set up management of the Terminal Server services, deploy the policies in the
following policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Quick Start
TSSPI-Terminal Server 5.2 (Win2003)/ TSSPI-TS52 Quick Start
•
TSSPI-ChkOsAndTSServices
•
TSSPI-ChkTSServicePortProbing
•
TSSPI-FwdOsAndTSAppWarnError
•
TSSPI-FwdOsAndTSSysWarnError
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Additional
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Additional
•
TSSPI-FwdOsAndTSAppInfo
•
TSSPI-FwdOsAndTSSysInfo
Tools
To manage the Terminal Server services, SPI for Terminal Server provides the tools
in the following tool group:
TSSPI-Terminal Server / TSSPI-TS Services
•
•
•
•
•
•
•
•
•
TSSPI-Start Netlogon Service
TSSPI-Start Spooler Service
TSSPI-Start Terminal Server Service
TSSPI-Start Terminal Server Session Directory Service
TSSPI-Status OS and Terminal Server Services
TSSPI-Stop Netlogon Service
TSSPI-Stop Spooler Service
TSSPI-Stop Terminal Server Service
TSSPI-Stop Terminal Server Session Directory Service
How It Works
Service Monitoring Policies
Microsoft Terminal Server component consists of a single Windows service Terminal Services service. With Windows Server 2003, Terminal Services Session
Directory has been added as an optional service you can use in load-balanced
Terminal Server farms.
28
User’s Guide
Two other Windows OS services (Netlogon and Print Spooler) are also important
from the Terminal Server perspective as they are essential for user authentication
and printing.
The table below lists Windows OS services that are important from the Terminal
Server component perspective:
Service Name
Windows 2003
Windows 2000
Net Logon
yes
yes
Print Spooler
yes
yes
Terminal Services
yes
yes
Terminal Services Session Directory
yes
The following policies implement Terminal Server / Windows OS service
monitoring:
•
TSSPI-ChkOsAndTSServices
Monitors all important Terminal Server and Windows OS services if they are in
running state, as given in table above.
•
TSSPI-ChkTSServicePortProbing
Monitors whether a Terminal Services service listens on a specific port for
incoming Terminal Server client connections. Default port number the service is
listening on is 3389. The policy is able to automatically detect if this port has been
modified through registry value HKLM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp\PortNumber.
Windows Event Log Forwarding Policies
Terminal Server component logs a lot of internal issues it detects to the Windows
Event Log. To early detect issues that may be developing, it is important to monitor
both Application and System Windows Event Logs. The following Terminal Server
and Windows OS tool event log sources are being monitored:
Application Event Log Source Name
Windows 2003
Windows 2000
SpoolerCtrs
yes
yes
The following Terminal Server system event log sources are being monitored:
System Event Log Source Name
Windows 2003
Windows 2000
TermDD
yes
yes
TermServDevices
yes
yes
TermService
yes
yes
Managing Terminal Servers 29
System Event Log Source Name
Windows 2003
Windows 2000
TermServJet
yes
TermServSessDir
yes
Netlogon
yes
yes
Print
yes
yes
The following policies implement Event Log forwarding.
•
TSSPI-FwdOsAndTSAppWarnError
Forwards Terminal Server and OS-related Warning and Error messages from the
Windows Application event log.
•
TSSPI-FwdOsAndTSSysWarnError
Forwards Terminal Server and OS-related Warning and Error messages from the
Windows System event log.
•
TSSPI-FwdOsAndTSAppInfo
Forwards Terminal Server and OS-related Informational messages from the
Windows Application event log.
•
TSSPI-FwdOsAndTSSysInfo
Forwards Terminal Server and OS-related Informational messages from the
Windows System event log.
30
User’s Guide
Managing Terminal Server Sessions
Managing Terminal Server sessions involves monitoring and managing the
following:
•
session resource consumption
•
session network issues
•
session state
•
server resources
•
end-user experience
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting Up Terminal Server Sessions Management” on page 31)
which policies are needed for monitoring Terminal Server sessions
(refer to “Policies” on page 47)
which tools are needed for managing Terminal Server sessions
(refer to “Tools” on page 28)
Setting Up Terminal Server Sessions Management
To monitor and manage Terminal Server sessions, deploy the policies to all managed
nodes. Based on the Windows Terminal Server version, use the following policy
groups:
•
•
on Windows 2000 Terminal Server
deploy the TSSPI-TS50 Quick Start policy group
on Windows 2003 Terminal Server
deploy the TSSPI-TS52 Quick Start policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
Managing Terminal Servers 31
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up management of the Terminal Server sessions, deploy the policies in the
following policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Quick Start
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Quick Start
•
TSSPI-ChkRDPListenerSession
•
TSSPI-ChkSessionHandleCount
•
TSSPI-ChkSessionPageFileBytes
•
TSSPI-ChkSessionProcessorTime
•
TSSPI-ChkSessionsActive
•
TSSPI-ChkSessionsAll
•
TSSPI-ChkSessionsInactive
•
TSSPI-ChkSessionThreadCount
•
TSSPI-ChkSessionTotalBytes
•
TSSPI-ChkSessionTotalErrors
•
TSSPI-ChkSessionTotalFrames
•
TSSPI-ChkSessionTotalTimeouts
•
TSSPI-ChkSessionTotalTransportErrors
•
TSSPI-ChkSessionWorkingSet
Tools
To manage the Terminal Server sessions, SPI for Terminal Server provides the tools
in the following tool groups:
TSSPI-Terminal Server / TSSPI-TS Information
•
TSSPI-Display All Session Processes
•
TSSPI-Display Sessions Info
TSSPI-Terminal Server / TSSPI-TS Session Control / TSSPI-TS Disconnect
32
•
TSSPI-Disconnect All Sessions
•
TSSPI-Disconnect Session (ID)
•
TSSPI-Disconnect Session (Name)
•
TSSPI-Disconnect User Sessions
User’s Guide
TSSPI-Terminal Server / TSSPI-TS Session Control / TSSPI-TS Logoff
•
TSSPI-Logoff All Sessions
•
TSSPI-Logoff Session (ID)
•
TSSPI-Logoff Session (Name)
•
TSSPI-Logoff User Sessions
TSSPI-Terminal Server / TSSPI-TS Session Control / TSSPI-TS Reset
•
TSSPI-Reset All Sessions
•
TSSPI-Reset Session (ID)
•
TSSPI-Reset Session (Name)
•
TSSPI-Reset User Sessions
TSSPI-Terminal Server / TSSPI-TS Session Control / TSSPI-TS Send Message
•
TSSPI-Send Message to All Sessions
•
TSSPI-Send Message to Session (ID)
•
TSSPI-Send Message to Session (Name)
•
TSSPI-Send Message to User Sessions
How It Works
Session Resource Consumption Policies
Session resource consumption policies are able to detect excessive use of system's
resources. These often indicate tool faults. In a multi-user environment, such as
Terminal Server, excessive use of system resources by only one session can result in
bad end-user experience for all other users connected to the same server.
Session resource consumption policies include two separate sets of thresholds: one
for Console session and one for all other sessions. Console session is very different
from all other user sessions as, among other things, all system services are running in
it. Therefore it typically shows higher use of system resources compared to ordinary
user sessions. To monitor session resource consumption, the following policies are
provided:
•
TSSPI-ChkSessionProcessorTime
Monitors percentage of elapsed processor time used by processes running in
individual session.
•
TSSPI-ChkSessionWorkingSet
Monitors physical memory consumption of processes running in individual
session.
•
TSSPI-ChkSessionPageFileBytes
Monitors virtual memory consumption of processes running in individual session.
Managing Terminal Servers 33
•
TSSPI-ChkSessionHandleCount
Monitors total number of handles currently opened by processes running in
individual session.
•
TSSPI-ChkSessionThreadCount
Monitors total number of threads currently active in processes running in
individual session.
•
TSSPI-ChkSessionTotalBytes
Monitors number of bytes transferred over the network between individual
Terminal Server client and server.
•
TSSPI-ChkSessionTotalFrames
Monitors the total number of frames transferred over the network between
individual Terminal Server client and server.
Session Network Issue Detection Policies
Session network issues detection policies are able to detect various issues on the
network connection between Terminal Server and its clients. These issues usually
have very high impact on end-user experience in form of unresponsive tools or even
loss of connectivity. To monitor network session issues, the following policies are
provided:
•
TSSPI-ChkSessionTotalErrors
The total number of errors detected on the network connection between
individual Terminal Server client and server. Examples of errors include: lost
ACK's, badly formed packets, and so on.
•
TSSPI-ChkSessionTotalTimeouts
The total number of time-outs detected on the network connection between
individual Terminal Server client and server. These are typically the result of a
noisy line. On high latency networks, you should consider increasing protocol
time-out if these occur often.
•
TSSPI-ChkSessionTotalTransportErrors
The total number of transport-level errors on the network connection between
individual Terminal Server client and server.
Monitoring Session State Information
To monitor session state information on a server level, the following policies are
provided:
•
TSSPI-ChkSessionsActive
Monitors the number of active sessions on the server. Before deployed, Terminal
Server systems are often load-tested to determine how much load (active sessions)
they can take. This policy can monitor against load-testing established baselines
34
User’s Guide
and alert when a system crosses them.
•
TSSPI-ChkSessionsInactive
Monitors the number of inactive (disconnected) sessions on the server. Inactive
sessions are not connected to any client, but they are still consuming resources on
the server. Users can re-connect to these sessions. If the number of inactive sessions
increases over time, this can impact system performance. To preserve system
resources, you can log off sessions that have been inactive for a long time.
•
TSSPI-ChkSessionsAll
Monitors the number of all sessions on the server. In addition to active and inactive
sessions, these also include sessions in more exotic states like connected /
connecting / idle / down / listening / resetting, and so on.
•
TSSPI-ChkRDPListenerSession
Monitors if a very important listener session, called RDP, is present. Without RDP
listener session running, no user can connect to the system using the Terminal
Server client.
Viewing Session Information
A set of tools is provided that allows displaying various session information. These
tools are located in the TSSPI-Terminal Server/TSSPI-TS Information tool group.
•
TSSPI-Display All Session Processes
Displays the names of processes and basic process information for all processes
currently running in a specific session.
•
TSSPI-Display Sessions Info
Displays basic session information for all sessions currently running on a system.
Interacting with Sessions
SPI for Terminal Server provides a rich set of tools that allow interaction with enduser sessions. These tools are located in the TSSPI-Terminal Server/TSSPI-TS Session
Control tool group.
•
TSSPI-TS Disconnect
Tools in this group allow disconnecting selected or all sessions from the server.
Sessions can be selected by their session ID or session name. Sessions can also be
disconnected by the username. Disconnecting all sessions on a server is also
possible.
•
TSSPI-TS Logoff
Tools in this group allow logging off selected or all sessions from the server.
Sessions can be selected by their session ID or session name. Sessions can also be
logged off by their username. Logging off all sessions on a server is also possible.
Managing Terminal Servers 35
•
TSSPI-TS Reset
Tools in this group allow resetting selected or all sessions on the server. Resetting
a session can sometimes help with a session that seems to be non-responding.
Sessions can be selected by their session ID or session name. Sessions can also be
reset by their username. Resetting all sessions on a server is also possible.
•
TSSPI-TS Send Message
Tools in this group allow sending messages to selected or all sessions from the
server. Sessions can be selected by their session ID or session name. A message can
also be sent to a session by specifying a username. Sending a message to all
sessions on a server is also possible.
36
User’s Guide
Managing Windows User Profiles
A user profile is a collection of settings, configurations, and personal files that are
unique to each user. A number of settings can be configured using user profiles, for
example: printers, temporary files location, mapped drives, desktop settings, and so
on.
In addition to system settings, most of installed tools set up their own user-specific
settings into the user profile.
There are basically four different ways user profiles can be used in Terminal Server
environments:
•
Local profiles
•
Roaming profiles
•
Mandatory profiles
•
Flex / Hybrid profiles
For more details on user profiles, refer to Terminal Server-related books.
Managing Windows user profiles on a Terminal Server involves managing and
monitoring the following:
•
•
Windows User profile volume (size, number of files)
Presence of specific file categories in user profile (for example, executable files,
media files, and so on)
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting up Windows User Profiles” on page 37)
which policies are needed for monitoring Windows user profiles
(refer to “Policies” on page 47)
which tools are needed for managing Windows user profiles
(refer to “Tools” on page 28)
Setting up Windows User Profiles
To monitor and manage Windows user profiles, deploy the policies to all managed
nodes. Based on the Windows Terminal Server version, use the following policy
groups:
Managing Terminal Servers 37
•
•
on Windows 2000 Terminal Server
deploy the TSSPI-TS50 Quick Start policy group
on Windows 2003 Terminal Server
deploy the TSSPI-TS52 Quick Start policy group
Depending on your needs, you may also consider deploying policies from the
following policy group:
•
•
on Windows 2000 Terminal Server
policies from the TSSPI-TS50 Additional policy group
on Windows 2003 Terminal Server
policies from the TSSPI-TS52 Additional policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up monitoring of the Windows user profiles, deploy the policies in the
following policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Quick Start
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Quick Start
•
TSSPI-ChkProfileFullSize
•
TSSPI-ChkProfileRoamingSize
•
TSSPI-ChkProfilesTotalRoamingSize
•
TSSPI-ChkProfilesTotalSize
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Additional
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Additional
38
•
TSSPI-ChkProfileFileCount
•
TSSPI-ChkProfileRoamingFileCount
•
TSSPI-ChkProfilesTotalFileCount
•
TSSPI-ChkProfilesTotalRoamingFileCount
•
TSSPI-ChkProfileExecutableCount
•
TSSPI-ChkProfilesTotalExecutableCount
User’s Guide
•
TSSPI-ChkProfileMediaCount
•
TSSPI-ChkProfilesTotalMediaCount
Tools
To manage Windows user profiles, SPI for Terminal Server provides the tools in the
following tool group:
TSSPI-Terminal Server / TSSPI-TS Information
•
TSSPI-Display User Profile Information
How It Works
Monitoring Windows User Profile Volume
Roaming profiles are by far the most common profile type used in Terminal Server
environments. They are very easy to setup, and the user has the benefit of having the
same application / user settings on every Terminal Server he connects to.
Simplistically, roaming profiles are copied from the network share location each time
user logs on to the Terminal Server system and copied back to the same network
location when user logs off from the Terminal Server system, hence preserving any
settings user might have changed during the session.
When user is working on a Terminal Server system, a lot of temporary files can get
stored to the user's profile. Often, it does not make sense to copy all those temporary
files to the network share location when user logs off, hence Administrators can limit
the set of user profile directories that get preserved.
You could partition roaming profiles in two parts: "roaming" part and "temporary"
part of user's profile. To monitor Windows user profiles, the following policies are
provided:
•
TSSPI-ChkProfileFileCount
Monitors the number of files in individual user profile
•
TSSPI-ChkProfileFullSize
Monitors the total size of individual user profile
•
TSSPI-ChkProfileRoamingFileCount
Monitors the number of files in the roaming part of individual user profile.
"Roaming part" refers to the set of directories that will get copied to the user's
network share location.
•
TSSPI-ChkProfileRoamingSize
Monitors the size of the roaming part of individual user's profile. "Roaming part"
Managing Terminal Servers 39
refers to the set of directories that will get copied to the user's network share
location.
•
TSSPI-ChkProfilesTotalFileCount
Monitors the total number of files in all user profiles on a Terminal Server system.
•
TSSPI-ChkProfilesTotalRoamingFileCount
Monitors the total number of files in roaming parts of all user profiles. "Roaming
part" refers to the set of directories that will get copied to the user's network share
location.
•
TSSPI-ChkProfilesTotalRoamingSize
Monitors the total size of roaming parts of the user profiles. "Roaming part" refers
to the set of directories that will get copied to the user's network share location.
•
TSSPI-ChkProfilesTotalSize
Monitors the total size of all user profiles on a Terminal Server system.
Monitoring for Presence of Specific File Categories in Windows User Profiles
Terminal Server SPI allows monitoring of Windows user profiles for presence and
amount of specific file categories. Three file categories can be tracked: executable
files, media files, and custom files. First two file categories are pre-defined by
monitoring policies, and the third category can be freely customized.
Executable files are the files with the following suffixes:
.exe,.bat,.com,.btm,.pif,.cmd,.scr,.vbs,.js,.wsf,.vbe,.vb,.wsh,.jse
Media files are the files with the following suffixes:
.wav,.wma,.aif,.aiff,.voc,.au,.snd,.ogg,.nsv,.nsa,.m4a,.mp3,.mp2,.mp1,
.aac,.apu,.mid,.miz,.rmi,.kar,.mpg,.mpeg,.m2v,.avi,.asf,.cda,.pls,.m3u
,.mp2v
To monitor for presence of specific file categories in Windows user profiles, the
following policies are provided:
•
TSSPI-ChkProfileExecutableCount
Monitors the number of executable files in individual user profile.
•
TSSPI-ChkProfilesTotalExecutableCount
Monitors the total number of executable files in all user profiles.
•
TSSPI-ChkProfileMediaCount
Monitors the number of media files in individual user profile.
•
TSSPI-ChkProfilesTotalMediaCount
Monitors the total number of media files in all user profiles.
40
User’s Guide
Viewing Windows User Profile Information
A tool is provided that allows insight into user profiles on a system. It is located in
the TSSPI-Terminal Server/TSSPI-TS Information tool group:
•
TSSPI-Display User Profile Information
Displays the information about the user profiles on the Terminal Server system.
Managing Terminal Servers 41
Managing Terminal Server Servers
Managing Terminal Server servers involves monitoring specific Terminal Server
settings to make sure they have not been changed. They can get changed either by
mistake or on purpose and are then not set back to their "operating" value.
Managing Terminal Server servers involves managing and monitoring the
following:
•
Logon state
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting Up Terminal Server Servers Management” on page 42)
which policies are needed for monitoring Terminal Server servers
(refer to “Policies” on page 47)
which tools are needed for managing Terminal Server servers
(refer to “Tools” on page 28)
Setting Up Terminal Server Servers Management
To monitor and manage Terminal Server servers, deploy the policies to all managed
nodes.
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up interaction with Terminal Servers, deploy the policies in the following
policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Quick Start
42
User’s Guide
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Quick Start
•
TSSPI-ChkLogonState
Tools
To manage the Terminal Servers, SPI for Terminal Server provides the tools in the
following tool group:
TSSPI-Terminal Server / TSSPI-TS Session Control / TSSPI-TS Logon Control
•
TSSPI-Enable Logons
•
TSSPI-Disable Logons
•
TSSPI-Status of Logons
How It Works
Monitoring Terminal Server Logon State
Terminal Server logon state defines whether users are allowed to logon to the
Terminal Server system. Users should be allowed to logon to the server at all times
except during server maintenance when logons are typically disabled.
The following policy implements monitoring of Terminal Server logon state:
•
TSSPI-ChkLogonState
Alerts if users are not allowed to logon to the Terminal Server system.
Managing Terminal Server Logon State
The following tools allow you to change and view Terminal Server logon state:
•
TSSPI-Enable Logons
Enables user logons to Terminal Server system.
•
TSSPI-Disable Logons
Disables user logons to Terminal Server system.
•
TSSPI-Status of Logons
Shows the status of logons to Terminal Server system.
Managing Terminal Servers 43
Managing Terminal Server User Logon Process
User logon is a complex and resource intensive process on a Terminal Server system.
It is initiated when a user launched Terminal Server client, connects to a particular
Terminal Server, and types-in username and password, and it ends when the user is
able to interact with his desktop.
SPI for Terminal Server breaks down user logon process into three phases:
•
Phase 1: User profile loading
•
Phase 2: Applying group policy objects (GPOs)
•
Phase 3: User initialization
For each user logon process phase SPI for Terminal Server measures its duration.
Duration is also calculated for the complete user logon process.
Managing Terminal Server user logon process involves managing and monitoring
the following:
•
Monitoring user logon process
•
Viewing user logon process information
Overview
This section contains the following information:
•
•
•
notes on deploying the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting Up Terminal Server Sessions Management” on page 31)
which policies are needed for monitoring Terminal Server user logon process
(refer to “Policies” on page 45)
which tools are needed for managing Terminal Server user logon process
(refer to “Tools” on page 45)
Setting Up Terminal Server User Logon Process Management
To monitor and manage user logon process on Terminal Servers, deploy the policies
to all Terminal Server managed nodes. Based on the Terminal Server version, use the
following policies:
•
•
44
on Windows 2000 Terminal Server
deploy the TSSPI-TS50 Quick Start policy group
on Windows 2003 Terminal Server
User’s Guide
deploy the TSSPI-TS52 Quick Start policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up management of the Terminal Server user logon process, deploy the policies
in the following policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Quick Start
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Quick Start
•
TSSPI-ChkUserLogonProcess
•
TSSPI-ChkUserLogonProcessCompleted
Depending on your needs, you might also consider deploying some of the following
policies:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Additional
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Additional
•
TSSPI-ChkUserLogonProcessPh1
•
TSSPI-ChkUserLogonProcessPh2
•
TSSPI-ChkUserLogonProcessPh3
Tools
To monitor and manage Terminal Server user logon process information, SPI for
Terminal Server provides tools in the following tool group:
TSSPI-Terminal Server/TSSPI-TS Information
•
TSSPI-Display Logons by User
•
TSSPI-Display Recent User Logonss
Managing Terminal Servers 45
How it works
Monitoring User Logon Process
The following policies implement Terminal Server user logon process monitoring:
•
TSSPI-ChkUserLogonProcess
Monitors duration of the complete user logon process. User logon process
duration is defined as the sum of all individual logon process phase durations.
•
TSSPI-ChkUserLogonProcessCompleted
Monitors whether a user logon process has completed in a timely manner. By
default, if any phase of the user logon process takes more than 300 seconds, or if
the process does not go through all logon process phases, the user logon process
is considered to be incomplete.
•
TSSPI-ChkUserLogonProcessPh1
Monitors duration of phase 1 of the user logon process. By default, if phase takes
more than 300 seconds to complete, it is timed-out.
•
TSSPI-ChkUserLogonProcessPh2
Monitors duration of phase 2 of the user logon process. By default, if phase takes
more than 300 seconds to complete, it is timed-out.
•
TSSPI-ChkUserLogonProcessPh3
Monitors duration of phase 3 of the user logon process. By default, if phase takes
more than 300 seconds to complete, it is timed-out.
Viewing User Logon Process Information
A set of tools allow viewing user logon process information that is being collected on
Terminal Server systems. These tools are located in the TSSPI-Terminal Server/TSSPITS Information tool group:
•
TSSPI-Display Logons by User
Displays all logons that were carried out on a system by a specified user. All
logons older than 24 hours are purged from the local store.
•
TSSPI-Display Recent User Logons
Displays all user logons that were carried out within a specified amount of time.
All logons older than 24 hours are purged from the local store.
46
User’s Guide
Managing Terminal Server Service Map
SPI for Terminal Server service map groups all Terminal Server systems in your
environment to provide better overview of their operational status.
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting Up Terminal Server Service Map” on page 47)
which policies are needed for monitoring Terminal Server service map
(refer to “Policies” on page 47)
which tools are needed for managing Terminal Server service map
(refer to “Tools” on page 28)
Setting Up Terminal Server Service Map
To monitor and manage Terminal Server part of the SPI for Terminal Server service
map, deploy the policies to all managed nodes. Based on the Terminal Server
version, use the following policy groups:
•
•
on Windows 2000 Terminal Server
deploy the TSSPI-TS50 Discovery policy group
on Windows Server 2003 Terminal Server
deploy the TSSPI-TS52 Discovery policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up management of the Terminal Server part of the SPI for Terminal Server
service map, deploy the policies in the following policy groups:
Managing Terminal Servers 47
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Discovery
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Discovery
•
TSSPI-DscServiceModel
Tools
To manage the Terminal Server part of the SPI for Terminal Server service map, SPI
for Terminal Server provides the tools in the following tool group:
TSSPI-Terminal Server / TSSPI-TS Discovery
•
TSSPI-Autodiscovery
How It Works
Generating Terminal Server Service Map
For information on how to add Terminal Server systems to the SPI for Terminal
Server service map, refer to “Autodiscovery of the Terminal Server Environment”
on page 21.
48
User’s Guide
Collecting Terminal Server Performance Information
Terminal Server graphs and reports require that performance data is being collected
on all Terminal Server nodes that are being managed. Without these policies
deployed, SPI for Terminal Server graphs and reports will remain empty.
Overview
This section contains the following information:
•
which policies are needed for collecting SPI for Terminal Server performance data
(refer to “Policies” on page 49)
Policies
To collect SPI for Terminal Server performance data, SPI for Terminal Server
provides the policies in the following policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Data Collection
TSSPI-Terminal Server 5.2 (Win2003) / TSSPI-TS52 Data Collection
•
TSSPI-LogServer
•
TSSPI-LogSessInfo
•
TSSPI-LogSession
•
TSSPI-LogUserLogonProcess
•
TSSPI-LogProfile
•
TSSPI-LogProfiles
How It Works
Terminal Server Data Collection
SPI for Terminal Server reports and graphs rely on performance data being collected
on the managed nodes. Performance data is stored in the Embedded Performance
Component of the OVO agent. Another name for this performance component is also
the CODA subagent.
The following policies collect data on the Terminal Server managed nodes:
•
TSSPI-LogServer
Collects Terminal Server-wide information, like number of active and inactive
sessions.
Managing Terminal Servers 49
•
TSSPI-LogSessInfo
Collects Terminal Server extended session information like session state, user
domain name and account name, client name and IP address, and so on.
•
TSSPI-LogSession
Collects Terminal Server session performance information, like session CPU and
memory resource consumption, number of session threads and handles
consumed, and so on.
•
TSSPI-LogUserLogonProcess
Collects user logon process information for every user that logs-in to the Terminal
Server system. Information collected includes user domain and account name,
duration of logon process phases and of the complete logon process, and so on.
•
TSSPI-LogProfile
Collects user profile information for each individual user that has profile on the
Terminal Server system. Information collected includes size of complete profile
and roaming part of the profile, number of executable and media files, and so on.
•
TSSPI-LogProfiles
Collects summary user profile information on the Terminal Server system.
Information collected includes total size of all user profiles and roaming parts of
their profiles, number of executable and media files, and so on.
50
User’s Guide
Chapter 5
Managing License Servers
About Managing Microsoft Terminal Server License Servers
Terminal Server license server works with Terminal Servers to provide, catalog, and
enforce license policy among Terminal Server clients.
In Windows 2000 Terminal Server environments, the Terminal Server license server
must be installed on a domain controller.
In Windows 2003 Terminal Server environments, the Terminal Server License Server
must be installed on a Windows 2003 server. Contrary to Windows 2000 license
server, the Windows 2003 Terminal Server license server can be any server in the
environment.
Terminal Server license server manages the following license types:
•
•
•
•
•
Terminal Server Device Client Access licenses (TS Device CALs). These licenses
are purchased for known, non-Windows devices connecting to a Terminal
Server.
Terminal Server Internet Connector licenses. This license is used to allow
anonymous use of a Windows 2000 terminal server by non-employees across the
Internet on a concurrent basis. On Windows 2003, this license is replaced by the
External Connector license.
Built-in licenses. Clients that are running the Windows 2000 operating system are
automatically licensed as Terminal Services Clients.
Temporary licenses. When a terminal server requests a client access license and
the License server has none to give, it will issue a temporary license. The license
server will track the issuance and expiration of these.
Windows 2003 only: Terminal Server User Client Access licenses (TS User CALs).
These licenses are purchased for known users connecting to a Terminal Server.
Managing Terminal Server License Servers involves the following:
“Managing Terminal Server License Server Services” on page 53
“Managing Terminal Server License Server Licenses” on page 56
“Managing Terminal Server License Server Service Map” on page 59
“Collecting Terminal Server License Server Performance Information” on page 61
52
User’s Guide
Managing Terminal Server License Server Services
Managing Terminal Server License Server services involves managing and
monitoring the following:
•
Terminal Server License Server-related services
•
Terminal License Server-related Windows Event Log entries
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server License
Server nodes
(refer to “Setting Up Terminal Server License Server Services Management” on
page 53)
which policies are needed for monitoring Terminal Server License Server services
(refer to “Policies” on page 54)
which tools are needed for managing Terminal Server License Server services
(refer to “Policies” on page 54)
Setting Up Terminal Server License Server Services Management
To monitor and manage Terminal Server License Server services, deploy the policies
to all managed nodes. Based on the Windows Terminal Server License Server
version, use the following policy groups:
•
•
on Windows 2000 Terminal Server License Server
deploy the TSSPI-TLS50 Quick Start policy group
on Windows 2003 Terminal Server License Server
deploy the TSSPI-TLS52 Quick Start policy group
Depending on your needs, you may also consider deploying policies from the
following policy group:
•
•
on Windows 2000 Terminal Server
policies from the TSSPI-TLS50 Additional policy group
on Windows 2003 Terminal Server
policies from the TSSPI-TLS52 Additional policy group
Managing License Servers 53
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server License Server managed nodes. For this purpose
you can use the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up monitoring of the Terminal Server License Server managed nodes, deploy
the policies in the following policy groups:
TSSPI-TS License Server 5.0 (Win2000) / TSSPI-TLS50 Quick Start
TSSPI-TS License Server 5.2 (Win2003) / TSSPI-TLS52 Quick Start
•
TSSPI-ChkTlsService
•
TSSPI-FwdTlsSysWarnError
TSSPI-TS License Server 5.0 (Win2000) / TSSPI-TLS50 Additional
TSSPI-TS License Server 5.2 (Win2003) / TSSPI-TLS52 Additional
•
TSSPI-FwdTlsSysInfo
Tools
To manage Terminal Server License Server systems, SPI for Terminal Server
provides the tools in the following tool group:
TSSPI-Terminal License Server/TSSPI-TLS Services
•
TSSPI-Start Terminal Server Licensing Service
•
TSSPI-Status Terminal Server Licensing Service
•
TSSPI-Stop Terminal Server Licensing Service
How It Works
Service Monitoring Policies
Terminal Server License Server is made of a single Windows service.
54
User’s Guide
The following table lists all Terminal Server License Server services and versions of
Windows OS product they are delivered as part of:
Service Name
Windows 2003
Windows 2000
TermServLicensing
yes
yes
The following policy implements Terminal Server license server service monitoring:
•
TSSPI-ChkTlsService
Monitors Terminal Server license server service if it is in a running state.
Windows Event Log Forwarding Policies
Terminal Server license server service logs a lot of internal issues it detects to the
Windows Event Log. Closely monitoring the System Windows Event Log is
therefore very important for early detection of issues that may be developing. The
following Terminal Server license server System event log sources are being
monitored:
Application EventLog Source Name
Windows 2003
Windows 2000
TermServLicensing
yes
yes
The following policies implement Event Log forwarding.
•
TSSPI-FwdTlsSysWarnError
Forwards Terminal Server license server-related Warning and Error messages
from the Windows System event log.
•
TSSPI-FwdTlsSysInfo
Forwards Terminal Server license server-related Informational messages from the
Windows System event log.
Interacting with Services
A set of tools allow interacting with Terminal Server license server services. They all
are located in tool group: TSSPI-Terminal License Server / TSSPI-TLS Services. They
allow starting / stopping, and checking status of relevant services.
•
TSSPI-Start Terminal Server Licensing Service
Starts the Terminal Server license server service on the managed node.
•
TSSPI-Stop Terminal Server Licensing Service
Stops the Terminal Server license server service on the managed node.
•
TSSPI-Stop Terminal Server Licensing Service
Shows status of the Terminal Server license server service on the managed node.
Managing License Servers 55
Managing Terminal Server License Server Licenses
Managing Terminal Server license server licenses involves managing and
monitoring the following:
•
License usage
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server nodes
(refer to “Setting Up Terminal Server License Server Licenses Management” on
page 56)
which policies are needed for monitoring Terminal Server services
(refer to “Policies” on page 54)
which tools are needed for managing Terminal Server services
(refer to “Tools” on page 54)
Setting Up Terminal Server License Server Licenses Management
To monitor and manage Terminal Server License Server licenses, deploy the policies
to all Terminal Server License Server managed nodes. Based on the Windows
Terminal Server version, use the following policy groups:
•
•
on Windows 2000 Terminal Server License Server
deploy the TSSPI-TLS50 Quick Start policy group
on Windows 2003 Terminal Server License Server
deploy the TSSPI-TLS52 Quick Start policy group
Depending on your needs, you may also consider deploying policies from the
following policy group:
•
•
on Windows 2000 Terminal Server License Server
policies from the TSSPI-TLS50 Additional policy group
on Windows 2003 Terminal Server License Server
policies from the TSSPI-TLS52 Additional policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server managed nodes. For this purpose you can use
the TSSPI-Check Requirements/Configuration tool.
56
User’s Guide
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Policies
To set up monitoring of the Terminal Server license server licenses, deploy the
policies in the following policy groups:
TSSPI-TS License Server 5.0 (Win2000) / TSSPI-TLS50 Quick Start
•
TSSPI-ChkTls50Dev2000
TSSPI-TS License Server 5.0 (Win2000) / TSSPI-TLS50 Additional
•
TSSPI-ChkTls50Temp
TSSPI-TS License Server 5.2 (Win2003) / TSSPI-TLS52 Quick Start
•
TSSPI-ChkTls52Dev2000
•
TSSPI-ChkTls52Dev2003
TSSPI-TS License Server 5.2 (Win2003) / TSSPI-TLS52 Additional
•
TSSPI-ChkTls52Temp
•
TSSPI-ChkTls52User2003
Tools
To manage Terminal Server License Server systems, SPI for Terminal Server
provides the tools in the following tool groups:
TSSPI-Terminal License Server/TSSPI-TLS Informations
•
TSSPI-Start Terminal Server Licensing Service
•
TSSPI-Status Terminal Server Licensing Service
•
TSSPI-Stop Terminal Server Licensing Service
How It Works
Monitoring License Usage
Monitoring Terminal Server CAL usage will let you know when you are
approaching the license limits. Device, user, and temporary license usage can be
monitored on Windows 2000 / Windows Server 2003 Terminal Server License
Servers using the following policies:
•
TSSPI-ChkTls50Dev2000
Managing License Servers 57
Monitors usage of Windows 2000 TS Device CALs on Windows 2000 TS License
Server.
•
TSSPI-ChkTls50Temp
Monitors usage of temporary Windows 2000 TS Device CALs on Windows 2000
TS License Server.
•
TSSPI-ChkTls52Dev2000
Monitors usage of Windows 2000 TS Device CALs on Windows 2003 TS License
Server.
•
TSSPI-ChkTls52Dev2003
Monitors usage of Windows 2003 TS Device CALs.
•
TSSPI-ChkTls52Temp
Monitors usage of temporary Windows 2003 TS Device CALs.
•
TSSPI-ChkTls52User2003
Monitors usage of Windows 2003 TS User CALs.
Viewing License Usage
A tool is available that allows viewing Terminal Server license server license usage.
It is located in the TSSPI-Terminal License Server / TSSPI-TLS Information tool
group.
•
TSSPI-Display TLS Information
Displays the Terminal Server License Server license usage information.
58
User’s Guide
Managing Terminal Server License Server Service Map
SPI for Terminal Server service map groups all Terminal Server License Server
systems in your environment to provide better overview of their operational status.
Overview
This section contains the following information:
•
•
•
notes on distributing the SPI for Terminal Server on Terminal Server License
Server nodes
(refer to ““Setting Up Terminal Server License Server Service Map” on page 59)
which policies are needed for monitoring Terminal Server License Server service
map
(refer to “Policies” on page 60)
which tools are needed for managing Terminal Server License Server service map
(refer to “Tools” on page 60)
Setting Up Terminal Server License Server Service Map
To monitor and manage Terminal Server License Server part of the SPI for Terminal
Server service map, deploy the policies to all managed nodes. Based on the Terminal
Server License Server version, use the following policy groups:
•
•
on Windows 2000 Terminal Server License Server
deploy the TSSPI-TLS50 Discovery policy group
on Windows Server 2003 Terminal Server License Server
deploy the TSSPI-TLS52 Discovery policy group
Before you deploy the policies, verify that SPI for Terminal Server is fully configured
and licensed on all Terminal Server License Server managed nodes.
For this purpose you can use the TSSPI-Check Requirements/Configuration tool.
NOTE
For instructions on how to distribute SPI for Terminal Server tools, policies, and
reports, refer to Chapter 3, “Setting Up the Environment”.
Managing License Servers 59
Policies
To set up management of the Terminal Server License Server part of the SPI for
Terminal Server service map, deploy the policies in the following policy groups:
TSSPI-TS License Server 5.0 (Win2000) / TSSPI-TLS50 Discovery
TSSPI-TS License Server 5.2 (Win2003) / TSSPI-TLS52 Discovery
•
TSSPI-DscServiceModel
Tools
To manage the Terminal Server License Server part of the SPI for Terminal Server
service map, SPI for Terminal Server provides the tools in the following tool group:
TSSPI-Terminal License Server / TSSPI-TLS Discovery
•
TSSPI-Autodiscovery
How It Works
For information on how to add Terminal Server License Server systems to the SPI for
Terminal Server service map, refer to “Autodiscovery of the Terminal Server
Environment” on page 21.
60
User’s Guide
Collecting Terminal Server License Server Performance
Information
For Terminal Server License Server graphs and reports, performance data must be
collected on all Terminal Server License Server nodes you are managing. Without
these policies deployed, Terminal Server SPI graphs and reports for License Servers
will remain empty.
Overview
This section contains the following information:
•
which policies are needed for collecting SPI for Terminal Server license server
performance data
(refer to “Policies” on page 61)
Policies
To collect SPI for Terminal Server license server performance data, deploy the policy
in the following policy groups:
TSSPI-Terminal License Server 5.0 (Win2000) / TSSPI-TLS50 Data Collection
TSSPI-Terminal License Server 5.2 (Win2003) / TSSPI-TLS52 Data Collection
•
TSSPI-LogLicenses
How It Works
Terminal Server License Server Data Collection
SPI for Terminal Server reports and graphs rely on performance data being collected
on the managed nodes. Performance data is stored in the Embedded Performance
Component of the OVO agent. Another name for this performance component is also
the CODA subagent.
The following policy collects data on the Terminal Server License Server managed
nodes:
•
TSSPI-LogLicenses
Collects Terminal Server License Server information about Terminal Server license
use for each individual license set installed on the license server. Information
collected includes license set name and the number of available and used licenses
Managing License Servers 61
in the license set.
62
User’s Guide
Chapter 6
Maintaining SPI for Terminal Server
About Maintaining Microsoft Terminal Servers
There are a few configurational tasks that need to be carried out for SPI for Terminal
Server to operate correctly, or to troubleshoot it should this be required. Maintaining
Terminal Server environment involves the following:
•
Checking SPI requirements and configuration
•
SPI for Terminal Server licensing
•
Managing SPI for Terminal Server subagent
•
Generating SPI for Terminal Server support information
•
Viewing SPI for Terminal Server documentation
•
Removing SPI for Terminal Server files from the managed node
Overview
This section contains the following information:
•
•
which policies are needed for maintaining Terminal Server services
(refer to “Policies” on page 64)
which tools are needed for managing Terminal Server services
(refer to “Tools” on page 64)
Policies
To carry-out specific Terminal Server maintenance tasks, deploy the policies in the
following policy groups:
TSSPI-Terminal Server 5.0 (Win2000) / TSSPI-TS50 Quick Start
TSSPI-Terminal Server 5.2 (Win2003)/ TSSPI-TS52 Quick Start
TSSPI-Terminal License Server 5.0 (Win2000) / TSSPI-TLS50 Quick Start
TSSPI-Terminal License Server 5.2 (Win2003) / TSSPI-TLS52 Quick Start
•
TSSPI-ChkRequirements
TSSPI-SPI Licensing
•
TSSPI-Licensing
Tools
To maintain Terminal Server, SPI for Terminal Server provides the tools in the
following tool group:
64
User’s Guide
TSSPI-Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Configure
•
•
TSSPI-Register Subagent
TSSPI-Unregister Subagent
TSSPI-Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Documentation
•
TSSPI-Display Install Guide
•
TSSPI-Display Installation / Configuration Slides
•
TSSPI-Display Product License / Support Terms
•
TSSPI-Display Readme
•
TSSPI-Display Release Notes
•
TSSPI-Display Supported Platforms
•
TSSPI-Display User's Guide
TSSPI-Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Licensing
•
TSSPI-1. Clear License Request File on Mgmt Server
•
TSSPI-2. Generate License Request for Node
•
TSSPI-3. Merge License Activation Codes on Mgmt Server
•
TSSPI-List License Activation Codes
TSSPI-Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Support
•
TSSPI-Check Requirements/Configuration
•
TSSPI-Collect Support Information
•
TSSPI-Display Support Information
TSSPI-Terminal Server/TSSPI-SPI Maintenance/TSSPI-SPI Uninstall
•
TSSPI-Remove SPI from Managed Node
How It Works
SPI for Terminal Server Requirements and Configuration
For SPI for Terminal Server to operate correctly, the following requirements and
configuration items need to be correct:
•
version of Terminal Server/Terminal Server License Server must be compatible
with the SPI
•
SPI for Terminal Server license must be present and valid for the managed node
•
Terminal Server must not be installed
When installing and configuring SPI for Terminal Server to work on the managed
node, a tool TSSPI-Check Requirements/Configuration is executed and configuration
Maintaining SPI for Terminal Server 65
corrected until the tool reports everything is correctly configured on the node. Once
this is achieved, the TSSPI-ChkRequirements policy should be deployed to the node.
The policy will regularly check SPI for Terminal Server requirements and
configuration and alert you should something go wrong on the node (license file is
accidentally deleted, license expires, or similar).
The following policies implement SPI for Terminal Server requirements and
configuration-related activities:
•
TSSPI-ChkRequirements
Regularly checks is requirements and configuration on the managed node are
valid for SPI to work correctly.
The following tools implement SPI for Terminal Server requirements and
configuration-related tasks:
•
TSSPI-Check Requirements/Configuration
Displays result of the SPI for Terminal Server requirements and configuration
check on the managed node.
SPI for Terminal Server Licensing
For SPI for Terminal Server to operate correctly on the Terminal Server or Terminal
License Server managed node, a valid product license needs to be available for that
node. For a detailed description on how to license your SPI for Terminal Server
product, refer to the Licensing chapter in the SPI for Terminal Server Installation and
Configuration Guide.
The following policies implement SPI for Terminal Server licensing-related
activities.
•
TSSPI-Licensing
Intercepts and processes licensing-related opcmsg messages generated on the
managed node.
The following tools implement SPI for Terminal Server licensing-related tasks:
•
TSSPI-1. Clear License Request File on Mgmt Server
Clears the license request file on the management server.
•
TSSPI-2. Generate License Request for Node
Generates license request for the managed node and sends it to the management
server.
•
TSSPI-3. Merge License Activation Codes on Mgmt Server
License requests are activated by HERMES SoftLab licensing system. After the
license activation codes are received, they need to be merged with the existing set
of license activations using this tool.
•
66
TSSPI-List License Activation Codes
User’s Guide
Lists license activation codes that are available on the management server along
with their expiration dates.
Managing SPI for Terminal Server Subagent
When configuring SPI for Terminal Server, one of the essential tasks is also the
registration of the SPI subagent with the OVO agent. SPI subagent is the principal
component of SPI for Terminal Server, capable of performing advanced Terminal
Server management features.
The following tools implement SPI for Terminal Server subagent-related tasks:
•
TSSPI-Register Subagent
Registers SPI for Terminal Server subagent with the OVO agent on the managed
node. This is typically performed during the installation of the SPI for Terminal
Server to the managed node. For more information, refer to the SPI for Terminal
Server Installation and Configuration Guide.
•
TSSPI-Unregister Subagent
Unregisters SPI for Terminal Server subagent with the OVO agent on the managed
node. This is typically performed during the uninstallation of the SPI for Terminal
Server from the managed node. For more information, refer to the SPI for Terminal
Server Installation and Configuration Guide.
Generating SPI for Terminal Server Support Information
Should something go wrong and you need help from the SPI for Terminal Server
support engineers, you should generate and send them the file with the support
information to help them troubleshoot the issue.
To generate and display the SPI for Terminal Server support information, SPI for
Terminal Server provides the following tools:
•
TSSPI-Collect Support Information
Collects support information and copies it to a .zip file on the managed node. For
more information, refer to “Before Contacting Support” on page 5.
•
TSSPI-Display Support Information
Displays SPI for Terminal Server support information for the managed node.
Viewing the SPI for Terminal Server Documentation
A set of tools is provided that are able to display various product documents and
manuals from within the management console. Documents are in .txt, .pdf, and
.ppt format, requiring Notepad, Adobe Acrobat Reader, and PowerPoint installed
on the management console to show-up correctly.
The following tools display product documents and manuals:
Maintaining SPI for Terminal Server 67
•
TSSPI-Display Install Guide
Displays the SPI for Terminal Server Installation and Configuration Guide. The tool
requires Adobe Acrobat Reader installed on the management console.
•
TSSPI-Display Installation / Configuration Slides
Displays the SPI for Terminal Server installation and configuration slides.
Requires Microsoft PowerPoint Reader or full product version installed on the
management console.
•
TSSPI-Display Product License / Support Terms
Displays the SPI for Terminal Server product license and support terms that were
accepted during the product installation.
•
TSSPI-Display Readme
Displays SPI for Terminal Server readme document.
•
TSSPI-Display Release Notes
Displays the SPI for Terminal Server release notes document.
•
TSSPI-Display Supported Platforms
Displays the SPI for Terminal Server supported platforms document. The tool
requires Adobe Acrobat Reader installed on the management console.
•
TSSPI-Display User's Guide
Displays the SPI for Terminal Server User's Guide. The tool requires Adobe Acrobat
Reader installed on the management console.
Removing the SPI for Terminal Server Files from the Managed Node
Removing SPI for Terminal Server from the managed node is described in the SPI for
Terminal Server Installation and Configuration Guide.
One of the last steps of this procedure is also removal of the SPI for Terminal Server
files and directories from the managed node.
The following tool removes the SPI for Terminal Server files from the managed
node:
•
TSSPI-Remove SPI from Managed Node
Removes all SPI for Terminal Server files and directories from the managed node.
NOTE
You must perform the complete uninstall procedure on the managed node before
you can execute this tool, so use it only as described in the SPI for Terminal Server
Installation and Configuration Guide.
68
User’s Guide
Chapter 7
Quick Reference
SPI for Terminal Server Tools and Tool Groups
When you install SPI for Terminal Server, a new top level tool group is added in the
HP OpenView Operations administrator GUI. The SPI for Terminal Server tool group
contains all tools, used for managing your Terminal Server environment.
Figure 1. SPI for Terminal Server Tool Group
TSSPI-SPI Maintenance
SPI for Terminal Server maintenance tool group
TSSPI-SPI Uninstall
SPI for Terminal Server uninstall tool group
TSSPI-Remove SPI from Managed Node
Removes all Terminal Server SPI files from managed node and performs all
necessary cleanup steps. Run this tool only after you have undeployed all SPI for
70
User’s Guide
Terminal Server policies from the managed node, and properly uninstalled Web
Interface monitoring and unregistered Terminal Server SPI subagent.
Command:
cmd.exe /c \"if exist \"%OvAgentDir%\\bin\\instrumentation\"
(cscript.exe \"%OvAgentDir%\\bin\\instrumentation\\TSSPIRemoveWholeSPI.vbs\" -removeWholeSPI) else (cscript.exe
\"%OvAgentDir%\\bin\\OpC\\cmds\\TSSPI-RemoveWholeSPI.vbs\" removeWholeSPI)\"
Execute on: Managed Node
TSSPI-SPI Documentation
SPI for Terminal Server documentation tool group
TSSPI-Display Supported Platforms
Displays a list of supported Terminal Server and OpenView platforms (requires
Adobe Acrobat Reader installed on the Console).
Command:
\\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\doc\\SPI_for_Terminal_ServerSupported_Platforms.pdf
Execute on: Management Console
TSSPI-Display Install Guide
Launches the SPI for Terminal Server install guide (requires Adobe Acrobat Reader
installed on the Console).
Command:
\\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\doc\\TSSPI-InstallGuideWIN.pdf
Execute on: Management Console
TSSPI-Display Product License / Support Terms
Displays HERMES SoftLab Terminal Server SPI software license and support terms
Command:
notepad \\\\$OPC_MGMTSV\\SPIShare\\tsspi\\doc\\hsl_software_license_support_terms_signed.txt
Execute on: Management Console
TSSPI-Display Release Notes
Displays Terminal Server SPI release notes document.
Command:
notepad \\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\doc\\tsspi-release-notes-
Quick Reference 71
win.txt
Execute on: Management Console
TSSPI-Display Installation / Configuration Slides
Displays Terminal Server SPI Installation and Configuration PowerPoint slides
(requires PowerPoint or PowerPoint Viewer installed on the Console).
Command:
cmd /c start /B \\\\$OPC_MGMTSV\\SPIShare\\tsspi\\doc\\Installing_Configuring_SPI_for_Terminal_Server_Wind
ows-Slides.ppt
Execute on: Management Console
TSSPI-Display User's Guide
Launches Terminal Server SPI user's guide (requires Adobe Acrobat Reader
installed on the Console).
Command:
\\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\doc\\TSSPI-UserGuideWIN.pdf
Execute on: Management Console
TSSPI-Display Readme
Displays Terminal Server SPI readme document.
Command:
notepad \\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\doc\\tsspi-readme.txt
Execute on: Management Console
TSSPI-SPI Licensing
SPI for Terminal Server licensing tool group
TSSPI-1. Clear License Request File on Mgmt Server
Clears TSSPI license request file on management server. Usually first step when
requesting TSSPI licenses.
Command:
\"\\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\bin\\TSSPILicmgr\" --clear
Execute on: Management Server
TSSPI-List License Activation Codes
Lists and counts existing TSSPI license activations on Mgmt Server.
Command:
72
User’s Guide
\"\\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\bin\\TSSPILicmgr\" --list
Execute on: Management Server
TSSPI-3. Merge License Activation Codes on Mgmt Server
Merges newly obtained TSSPI license activation codes with existing license
activations. After a successful license merge, the license activation codes are ready to
be deployed to Terminal Server managed nodes.
Command:
\"\\\\$OPC_MGMTSV\\SPI-Share\\tsspi\\bin\\TSSPILicmgr\" --merge
Execute on: Management Server
TSSPI-2. Generate License Request for Node
Generates TSSPI license request information for managed node. Usually executed on
many nodes at once to speed-up generation of license requests.
Command:
TSSPILicmgr --generate --company_name=\"your company name\"
Execute on: Managed Node
TSSPI-SPI Configure
SPI for Terminal Server configuration tool group
TSSPI-Unregister Subagent
Unregisters Terminal Server SPI subagent with OVO agent.
Command:
TSSPISwitch.cmd unregsubagt
Execute on: Managed Node
TSSPI-Register Subagent
Registers Terminal Server SPI subagent with OVO agent.
Command:
TSSPISwitch.cmd regsubagt
Execute on: Managed Node
TSSPI-SPI Support
SPI for Terminal Server support tool group
Quick Reference 73
TSSPI-Check Requirements/Configuration
This tool checks whether TS server matches TSSPI requirements and whether it is
correctly configured
Command:
TSSPISupport --check
Execute on: Managed Node
TSSPI-Collect Support Information
This tool collects various support information about TS server
Command:
TSSPISupport --collect
Execute on: Managed Node
TSSPI-Display Support Information
This tool displays various support information about TS server
Command:
TSSPISupport --info
Execute on: Managed Node
TSSPI-Terminal License Server
Top-level Terminal Server License Server tool group
TSSPI-TLS Information
SPI for Terminal Server license server information tool group
TSSPI-Display TLS Information
This tool displays information about Terminal License Server
Command:
TSSPITls --print
Execute on: Managed Node
TSSPI-TLS Discovery
SPI for Terminal Server license server service discovery tool group
TSSPI-Autodiscovery
Tool for automatic discovery of Terminal Server configuration
Command:
74
User’s Guide
TSSPIUtil --svctree
Execute on: Managed Node
TSSPI-TLS Services
SPI for Terminal Server Licensing service tool group
TSSPI-Start Terminal Server Licensing Service
Starts Terminal Server Licensing service. Terminal Server Licensing service provides
registered licenses for Terminal Services clients.
Command:
TSSPISwitch.cmd startsvc TermServLicensing
Execute on: Managed Node
TSSPI-Stop Terminal Server Licensing Service
Stops Terminal Server Licensing service. Terminal Server Licensing service provides
registered licenses for Terminal Services clients.
Command:
TSSPISwitch.cmd stopsvc TermServLicensing
Execute on: Managed Node
TSSPI-Status Terminal Server Licensing Service
Shows status of Terminal Server Licensing service
Command:
TSSPISwitch.cmd disptlssvc
Execute on: Managed Node
TSSPI-Terminal Server
Top-level Microsoft Terminal Server tool group
TSSPI-TS Services
SPI for Terminal Server services tool group
TSSPI-Stop Netlogon Service
Stops Netlogon service. Service maintains a secure channel between this computer
and the domain controller for authenticating users and services.
Command:
TSSPISwitch.cmd stopsvc Netlogon
Quick Reference 75
Execute on: Managed Node
TSSPI-Start Print Spooler Service
Starts Print Spooler service. Service manages all local and network print queues and
controls all printing jobs.
Command:
TSSPISwitch.cmd startsvc Spooler
Execute on: Managed Node
TSSPI-Stop Print Spooler Service
Stops Print Spooler service. Service manages all local and network print queues and
controls all printing jobs.
Command:
TSSPISwitch.cmd stopsvc Spooler
Execute on: Managed Node
TSSPI-Start Terminal Services Session Directory Service
Starts Terminal Services Session Directory service. Service enables a user connection
request to be routed to the appropriate Terminal Server in a cluster.
Command:
TSSPISwitch.cmd startsvc Tssdis
Execute on: Managed Node
TSSPI-Stop Terminal Services Service
Stops Terminal Services service. Service allows users to connect interactively to the
system.
Command:
TSSPISwitch.cmd stopsvc TermService
Execute on: Managed Node
TSSPI-Stop Terminal Services Session Directory Service
Stops Terminal Services Session Directory service. Service enables a user connection
request to be routed to the appropriate Terminal Server in a cluster.
Command:
TSSPISwitch.cmd stopsvc Tssdis
Execute on: Managed Node
76
User’s Guide
TSSPI-Status OS and Terminal Server Services
Shows status of relevant Microsoft Windows and Terminal Server services
Command:
TSSPISwitch.cmd dispostssvc
Execute on: Managed Node
TSSPI-Start Netlogon Service
Starts Netlogon service. Service maintains a secure channel between this computer
and the domain controller for authenticating users and services.
Command:
TSSPISwitch.cmd startsvc Netlogon
Execute on: Managed Node
TSSPI-Start Terminal Services Service
Starts Terminal Services service. Service allows users to connect interactively to the
system.
Command:
TSSPISwitch.cmd startsvc TermService
Execute on: Managed Node
TSSPI-TS Session Control
SPI for Terminal Server session control tool group
TSSPI-TS Disconnect
SPI for Terminal Server session disconnect tool group
TSSPI-Disconnect All Sessions
Disconnects all sessions on TS server. Operator needs to select TS server.
Command:
TSSPIUtil --disconnect --sessname=*
Execute on: Managed Node
TSSPI-Disconnect Session (Name)
Disconnects a session on TS server with specified session name. Operator needs to
specify session name and select TS server.
Command:
TSSPIUtil --disconnect --sessname=\"Type Session Name\"
Quick Reference 77
Execute on: Managed Node
TSSPI-Disconnect Session (ID)
Disconnects a session on TS server with specified ID. Operator needs to specify
session ID and select TS server.
Command:
TSSPIUtil --disconnect --sessid=TypeSessionID
Execute on: Managed Node
TSSPI-Disconnect User Sessions
Disconnects all sessions on TS server with specified username. Operator needs to
specify username and select TS server.
Command:
TSSPIUtil --disconnect --user=\"Type User Name\"
Execute on: Managed Node
TSSPI-TS Send Message
SPI for Terminal Server session send message tool group
TSSPI-Send Message to Session (Name)
Sends message to a session on TS server. Operator needs to specify session name,
message text, and select TS server.
Command:
TSSPIUtil --send=\"Type Your Message\" --sessname=\"Type Session Name\"
Execute on: Managed Node
TSSPI-Send Message to User Sessions
Sends message to all user sessions on TS server. Operator needs to specify user
name, message text, and select TS server.
Command:
TSSPIUtil --send=\"Type Your Message\" --user=\"Type User Name\"
Execute on: Managed Node
TSSPI-Send Message to Session (ID)
Sends message to a session on TS server. Operator needs to specify session ID,
message text, and select TS server.
Command:
TSSPIUtil --send=\"Type Your Message\" --sessid=TypeSessionID
78
User’s Guide
Execute on: Managed Node
TSSPI-Send Message to All Sessions
Sends message to all sessions on TS server. Operator needs to specify message text,
and select the TS server.
Command:
TSSPIUtil --sessname=* --send=\"Type Your Message\"
Execute on: Managed Node
TSSPI-TS Reset
SPI for Terminal Server session reset tool group
TSSPI-Reset Session (Name)
Resets a session on the TS server with specified session name. Operator needs to
specify session name and select TS server.
Command:
TSSPIUtil --reset --sessname=\"Type Session Name\"
Execute on: Managed Node
TSSPI-Reset User Sessions
Resets all sessions on the TS server with specified username. Operator needs to
specify username and select TS server.
Command:
TSSPIUtil --reset --user=\"Type User Name\"
Execute on: Managed Node
TSSPI-Reset All Sessions
Resets all sessions on the TS server. Operator needs to select the TS server.
Command:
TSSPIUtil --reset --sessname=*
Execute on: Managed Node
TSSPI-Reset Session (ID)
Resets a session on TS server with specified ID. Operator needs to specify session ID
and select TS server.
Command:
TSSPIUtil --reset --sessid=TypeSessionID
Execute on: Managed Node
Quick Reference 79
TSSPI-TS Logoff
SPI for Terminal Server session logoff tool group
TSSPI-Logoff User Sessions
Logs off all sessions on TS server with specified username. Operator needs to specify
username and select TS server.
Command:
TSSPIUtil --logoff --user=\"Type User Name\"
Execute on: Managed Node
TSSPI-Logoff Session (Name)
Logs off a session on TS server with specified session name. Operator needs to
specify session name and select TS server.
Command:
TSSPIUtil --logoff --sessname=\"Type Session Name\"
Execute on: Managed Node
TSSPI-Logoff Session (ID)
Logs off a session on TS server with specified ID. Operator needs to specify session
ID and select TS server.
Command:
TSSPIUtil --logoff --sessid=TypeSessionID
Execute on: Managed Node
TSSPI-Logoff All Sessions
Logs off all sessions on TS server. Operator needs to select TS server.
Command:
TSSPIUtil --logoff --sessname=*
Execute on: Managed Node
TSSPI-TS Logon Control
SPI for Terminal Server session logon control tool group
TSSPI-Enable Logons
Enable Logons to TS server.
Command:
TSSPIUtil --enablelogons
Execute on: Managed Node
80
User’s Guide
TSSPI-Status of Logons
Shows whether logons are enabled/disabled on TS server.
Command:
TSSPIUtil --logonstatus
Execute on: Managed Node
TSSPI-Disable Logons
Disable Logons to TS server.
Command:
TSSPIUtil --disablelogons
Execute on: Managed Node
TSSPI-TS Discovery
SPI for Terminal Server service discovery tool group
TSSPI-Autodiscovery
Tool for automatic discovery of Terminal Server configuration
Command:
TSSPIUtil --svctree
Execute on: Managed Node
TSSPI-TS Information
SPI for Terminal Server information tool group
TSSPI-Display Sessions Info
Displays information about system's Terminal Server sessions.
Command:
TSSPIUtil --sessinfo --sessname=*
Execute on: Managed Node
TSSPI-Display Recent User Logons
Displays User Logons that occurred within specific time interval
Command:
TSSPISwitch.cmd displlogonuser /minutes:15
Execute on: Managed Node
Quick Reference 81
TSSPI-Display User Profile Information
Displays information about user profiles.
Command:
TSSPISwitch.cmd dispprofilestatus TSSPI-DisplayUserProfileInformation
Execute on: Managed Node
TSSPI-Display All Session Processes
Displays all processes for specific session.
Command:
TSSPIProc --allproc --sessid=0
Execute on: Managed Node
TSSPI-Display Logons by User
Displays logons for particular user
Command:
TSSPISwitch.cmd displlogonuser /user:<username>
Execute on: Managed Node
82
User’s Guide
SPI for Terminal Server Policies and Policy Groups
SPI for Terminal Server provides four types of policies:
•
Scheduled Task policies
•
Windows Event Log policies
•
Open Message Interface policies
•
Measurement Threshold policies
Scheduled Task Policies
SPI for Terminal Server provides the following Scheduled Task policies:
TSSPI-LogLicenses
<initial policy version>
Execute on:
Minute: "4,9,14,19,24,29,34,39,44,49,54,58"
Hour:
"0-23"
Day:
"1-31"
Month:
"1-12"
Command: TSSPITls --perf
TSSPI-LogProfile
Logs profiles status.
Execute on:
Minute: "9,19,29,39,49,58"
Hour:
"0-23"
Day:
"1-31"
Month:
"1-12"
Command line: TSSPIProfileLog.cmd
TSSPI-LogProfiles
Logs sum of all profiles status.
Execute on:
Quick Reference 83
Minute: "9,19,29,39,49,58"
Hour:
Day:
"0-23"
"1-31"
Month:
"1-12"
Command: TSSPIProfilesLog.cmd
TSSPI-LogServer
Logs selected performance data of Terminal Server.
Execute on:
Minute: "0,5,10,15,20,25,30,35,40,45,50,55"
Hour:
Day:
"0-23"
"1-31"
Month:
"1-12"
Command: TSSPICollectPerf.cmd TSSPI_SRV
TSSPI-LogSessInfo
Logs sessions info for Terminal Server.
Execute on:
Minute: "1,6,11,16,21,26,31,36,41,46,51,56"
Hour:
Day:
"0-23"
"1-31"
Month:
"1-12"
Command: TSSPISession --perf
TSSPI-LogSession
Logs selected performance data of Terminal Server sessions.
Execute on:
Minute: "1,6,11,16,21,26,31,36,41,46,51,56"
Hour:
Day:
Month:
"0-23"
"1-31"
"1-12"
Command: TSSPICollectPerf.cmd TSSPI_SESS
84
User’s Guide
TSSPI-LogUserLogonProcess
Logs Terminal Server user logon process performance information.
Execute on:
Minute: "2,7,12,17,22,27,32,37,42,47,52,57"
Hour:
"0-23"
Day:
"1-31"
Month:
"1-12"
Command: TSSPIPsldLog.cmd
Windows Event Log Policies
SPI for Terminal Server provides the following Windows Event Log policies:
TSSPI-FwdOsAndTSAppInfo
Forwards all OS and Terminal Server Application informational event log entries.
Event log name: %APPLICATION_LOG%
Rules:
•
Forwards informational SpoolerCtrs
Severity: Normal
TSSPI-FwdOsAndTSAppWarnError
Forwards all OS and Terminal Server Application warning / error event log entries.
Event log name: %APPLICATION_LOG%
Rules:
•
Forwards warning/error SpoolerCtrs
Severity: Warning Critical
TSSPI-FwdOsAndTSSysInfo
Forwards all OS and Terminal Server System informational event log entries.
Event log name: %SYSTEM_LOG%
Rules:
•
Forwards informational TermDD
Severity: Normal
Quick Reference 85
•
•
•
•
•
•
Forwards informational TermServDevices
Severity: Normal
Forwards informational TermService
Severity: Normal
Forwards informational TermServJet
Severity: Normal
Forwards informational TermServSessDir
Severity: Normal
Forwards informational Netlogon
Severity: Normal
Forwards informational Print
Severity: Normal
TSSPI-FwdOsAndTSSysWarnError
Forwards all OS and Terminal Server System warning / error event log entries.
Event log name: %SYSTEM_LOG%
Rules:
•
•
•
•
•
•
•
Forwards warning/error TermDD
Severity: Warning Critical
Forwards warning/error TermServDevices
Severity: Warning Critical
Forwards warning/error TermService
Severity: Warning Critical
Forwards warning/error TermServJet
Severity: Warning Critical
Forwards warning/error TermServSessDir
Severity: Warning Critical
Forwards warning/error Netlogon
Severity: Warning Critical
Forwards warning/error Print
Severity: Warning Critical
TSSPI-FwdTlsSysInfo
Forwards all Terminal Server Licensing System informational event log entries.
Event log name: %SYSTEM_LOG%
Rules:
86
User’s Guide
•
Forwards info TermServLicensing
Severity: Normal
TSSPI-FwdTlsSysWarnError
Forwards all Terminal Server Licensing System warning / error event log entries.
Event log name: %SYSTEM_LOG%
Rules:
•
Forwards warning/error TermServLicensing
Severity: Warning Critical
Open Message Interface Policies
SPI for Terminal Server provides the following Open Message Interface policies:
TSSPI-Licensing
Intercepts all TSSPI licensing related messages.
Rules:
•
•
•
•
•
Intercepts license request generation messages
Severity: Normal
Source: SPI for Terminal Server
Object: License
Message text: "LicenseRequestGeneration"
Intercepts "license not found" error
Source: SPI for Terminal Server
Object: License
Message text: "LIC_CHK_NOTFOUND"
Intercepts "part of license information is missing" error
Source: SPI for Terminal Server
Object: License
Message text: "LIC_CHK_LICACTINFO"
Intercepts "license key is incorrect" error
Source: SPI for Terminal Server
Object: License
Message text: "LIC_CHK_LK"
Intercepts "incorrect product ID" error
Severity: Normal Warning Minor Major Critical
Source: SPI for Terminal Server
Quick Reference 87
Object: License
Message text: "LIC_CHK_PID"
•
•
•
•
•
Intercepts "number of processors too high" error
Severity: Normal Warning Minor Major Critical
Source: SPI for Terminal Server
Object: License
Message text: "LIC_CHK_NRP"
Intercepts "license expired" error
Source: SPI for Terminal Server
Object: License
Message text: "LIC_CHK_EXP"
Intercepts "license file not present" error
Source: SPI for Terminal Server
Object: License
Message text: "LIC_OPENR_LICFILE"
Intercepts "Using trial license" info
Source: SPI for Terminal Server
Object: License
Message text: "LIC_USING_TRIAL"
Intercepts all other TSSPI licensing errors
Source: SPI for Terminal Server
Object: License
Message text: "Node <$MSG_NODE_NAME> is running a trial license of SPI for
Terminal Server that will expire <$OPTION(expire_date)>."
Measurement Threshold Policies
SPI for Terminal Server provides the following Measurement Threshold policies:
TSSPI-ChkLogonState
Monitors if logons are enabled.
Execute every: 5min
Command:
TSSPIUtil --logonstatus --noprint --policy=TSSPI-ChkLogonState
Rules:
•
88
Description: Disabled.
Threshold: 1.000000
Severity: Major
User’s Guide
TSSPI-ChkOsAndTSServices
Monitors mandatory and optional Windows and Terminal Server services.
Execute every: 5min
Command:
TSSPISwitch.cmd chkostssvc <$SRCNAME>
Rules:
•
•
•
•
•
•
•
•
•
Description: Running.
Threshold: 1.000000
Severity: Normal
Description: Not running.
Threshold: 0.000000
Severity: Critical
Description: Running.
Threshold: 1.000000
Severity: Normal
Description: Not running.
Threshold: 0.000000
Severity: Major
Description: Not installed.
Threshold: 2.000000
Severity: Critical
Description: Running.
Threshold: 1.000000
Severity: Normal
Description: Not running.
Threshold: 0.000000
Severity: Critical
Description: Running.
Threshold: 1.000000
Severity: Normal
Description: Not running.
Threshold: 0.000000
Severity: Major
TSSPI-ChkProfileExecutableCount
Monitors number of executable files in profile.
Execute every: 20min
Quick Reference 89
Command:
TSSPISwitch.cmd chkprofileexecutables TSSPI-ChkProfileExecutableCount
Rules:
•
Description: warning.
Threshold: 1.000000
Severity: Warning
TSSPI-ChkProfileFileCount
Monitors profile file count.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofilefilecount TSSPI-ChkProfileFileCount
Rules:
•
•
Description: major.
Threshold: 2000.000000
Severity: Major
Description: warning.
Threshold: 1500.000000
Severity: Warning
TSSPI-ChkProfileFullSize
Monitors profile full size.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofilefullsize TSSPI-ChkProfileFullSize
Rules:
•
•
Description: major.
Threshold: 100.000000
Severity: Major
Description: warning.
Threshold: 70.000000
Severity: Warning
TSSPI-ChkProfileMediaCount
Monitors number of media files in profile.
Execute every: 20min
90
User’s Guide
Command:
TSSPISwitch.cmd chkprofilemedias TSSPI-ChkProfileMediaCount
Rules:
•
Description: warning.
Threshold: 1000.000000
Severity: Warning
TSSPI-ChkProfileRoamingFileCount
Monitors roaming profile file count.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofileroamingfilecount TSSPIChkProfileRoamingFileCount
Rules:
•
•
Description: major.
Threshold: 1800.000000
Severity: Major
Description: warning.
Threshold: 1300.000000
Severity: Warning
TSSPI-ChkProfileRoamingSize
Monitors profile roaming size.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofileroamingsize TSSPI-ChkProfileRoamingSize
Rules:
•
•
Description: major.
Threshold: 90.000000
Severity: Major
Description: warning.
Threshold: 60.000000
Severity: Warning
TSSPI-ChkProfilesTotalExecutableCount
Monitors number of executable files in all profiles.
Execute every: 20min
Quick Reference 91
Command:
TSSPISwitch.cmd chkprofilesexecutables TSSPIChkProfilesTotalExecutableCount
Rules:
•
Description: warning.
Threshold: 1.000000
Severity: Warning
TSSPI-ChkProfilesTotalFileCount
Monitors all profiles file count.
Execute every: 20m
Command:
TSSPISwitch.cmd chkprofilesfilecount TSSPI-ChkProfilesTotalFileCount
Rules:
•
•
Description: major.
Threshold: 200000.000000
Severity: Major
Description: warning.
Threshold: 150000.000000
Severity: Warning
TSSPI-ChkProfilesTotalMediaCount
Monitors number of media files in all profiles.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofilesmedias TSSPI-ChkProfilesTotalMediaCount
Rules:
•
Description: warning.
Threshold: 40000.000000
Severity: Warning
TSSPI-ChkProfilesTotalRoamingFileCount
Monitors all roaming profiles file count.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofilesroamingfilecount TSSPIChkProfilesTotalRoamingFileCount
92
User’s Guide
Rules:
•
•
Description: major.
Threshold: 180000.000000
Severity: Major
Description: warning.
Threshold: 130000.000000
Severity: Warning
TSSPI-ChkProfilesTotalRoamingSize
Monitors all profiles roaming size.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofilesroamingsize TSSPIChkProfilesTotalRoamingSize
Rules:
•
•
Description: major.
Threshold: 20000.000000
Severity: Major
Description: warning.
Threshold: 15000.000000
Severity: Warning
TSSPI-ChkProfilesTotalSize
Monitors sum of all profiles size.
Execute every: 20min
Command:
TSSPISwitch.cmd chkprofilestotalsize TSSPI-ChkProfilesTotalSize"
Rules:
•
•
Description: major.
Threshold: 30000.000000
Severity: Major
Description: warning.
Threshold: 25000.000000
Severity: Warning
TSSPI-ChkRDPListenerSession
Monitor RDP Listener session.
Quick Reference 93
Execute every: 5min
Command:
TSSPISession --policy=<$SRCNAME> --listener
Rules:
•
Description: Failed.
Threshold: 1.000000
Severity: Major
TSSPI-ChkRequirements
Monitors requirements.
Execute every: 5min
Command:
TSSPISupport --check --policy=<$SRCNAME>
Rules:
•
Description: failed.
Threshold: 1.000000
Severity: Major
TSSPI-ChkSessionHandleCount
Checks handle count used by any session.
Execute every: 5min
Rules:
•
•
•
•
Description: If handle count used by any session major.
Threshold: 30000.000000
Severity: Major
Description: If handle count used by any session warning.
Threshold: 20000.000000
Severity: Warning
Description: If handle count used by any session major.
Threshold: 25000.000000
Severity: Major
Description: If handle count used by any session warning.
Threshold: 15000.000000
Severity: Warning
TSSPI-ChkSessionPageFileBytes
Checks page file bytes used by any session.
94
User’s Guide
Execute every: 5min
Rules:
•
•
•
•
Description: If page file bytes used by any session major.
Threshold: 768000000.000000
Severity: Major
Description: If page file bytes used by any session warning.
Threshold: 640000000.000000
Severity: Warning
Description: If page file bytes used by any session major.
Threshold: 384000000.000000
Severity: Major
Description: If page file bytes used by any session warning.
Threshold: 256000000.000000
Severity: Warning
TSSPI-ChkSessionProcessorTime
Checks percentage of processor time used by any session.
Execute every: 5min
Rules:
•
•
•
•
Description: If % Processor Time used by console session major.
Threshold: 95.000000
Severity: Major
Description: If % Processor Time used by console session warning.
Threshold: 75.000000
Severity: Warning
Description: If % Processor Time used by any session major.
Threshold: 90.000000
Severity: Major
Description: If % Processor Time used by any session warning.
Threshold: 70.000000
Severity: Warning
TSSPI-ChkSessionThreadCount
Checks thread count used by any session.
Execute every: 5min
Rules:
Quick Reference 95
•
•
•
•
Description: If thread count used by any session major.
Threshold: 1200.000000
Severity: Major
Description: If thread count used by any session warning.
Threshold: 1000.000000
Severity: Warning
Description: If thread count used by any session major.
Threshold: 1100.000000
Severity: Major
Description: If thread count used by any session warning.
Threshold: 900.000000
Severity: Warning
TSSPI-ChkSessionTotalBytes
Checks total bytes used by any session.
Execute every: 5min
Rules:
•
•
Description: If total bytes used by any session major.
Threshold: 384000000.000000
Severity: Major
Description: If total bytes used by any session warning.
Threshold: 256000000.000000
Severity: Warning
TSSPI-ChkSessionTotalErrors
Checks total errors used by any session.
Execute every: 5min
Rules:
•
•
Description: If total errors generated by any session major.
Threshold: 10.000000
Severity: Major
Description: If total errors generated by any session warning.
Threshold: 3.000000
Severity: Warning
TSSPI-ChkSessionTotalFrames
Checks total frames used by any session.
96
User’s Guide
Execute every: 5min
Rules:
•
•
Description: If total frames used by any session major.
Threshold: 512.000000
Severity: Major
Description: If total frames used by any session warning.
Threshold: 256.000000
Severity: Warning
TSSPI-ChkSessionTotalTimeouts
Checks total timeouts used by any session.
Execute every: 5min
Rules:
•
•
Description: If total timeounts generated by any session major.
Threshold: 5.000000
Severity: Major
Description: If total timeounts generated by any session warning.
Threshold: 3.000000
Severity: Warning
TSSPI-ChkSessionTotalTransportErrors
Checks total transport errors used by any session.
Execute every: 5min
Rules:
•
•
Description: If total transport errors generated by any session major.
Threshold: 10.000000
Severity: Major
Description: If total transport errors generated by any session warning.
Threshold: 3.000000
Severity: Warning
TSSPI-ChkSessionWorkingSet
Checks working set bytes used by any session.
Execute every: 5min
Rules:
Quick Reference 97
•
•
•
•
Description: If working set size used by any session is major.
Threshold: 512000000.000000
Severity: Major
Description: If working set size used by any session is warning.
Threshold: 384000000.000000
Severity: Warning
Description: If working set size used by any session major.
Threshold: 256000000.000000
Severity: Major
Description: If working set size used by any session warning.
Threshold: 128000000.000000
Severity: Warning
TSSPI-ChkSessionsActive
Checks number of active sessions on a Terminal Server.
Execute every: 5min
Rules:
•
•
Description: Check for major number of active sessions.
Threshold: 100.000000
Severity: Major
Description: Check for warning number of active sessions.
Threshold: 90.000000
Severity: Warning
TSSPI-ChkSessionsAll
Checks number of sessions on a Terminal Server.
Execute every: 5min
Rules:
•
•
Description: Check for major number of sessions.
Threshold: 120.000000
Severity: Major
Description: Check for warning number of sessions.
Threshold: 90.000000
Severity: Warning
TSSPI-ChkSessionsInactive
Checks number of inactive sessions on a Terminal Server.
98
User’s Guide
Execute every: 5min
Rules:
•
•
Description: Check for major number of inactive sessions.
Threshold: 50.000000
Severity: Major
Description: Check for warning number of inactive sessions.
Threshold: 30.000000
Severity: Warning
TSSPI-ChkTSServicePortProbing
Monitor Terminal Server service with port probing
Execute every: 5min
Command:
TSSPIPortChecker --policy=<$SRCNAME>
Rules:
•
Description: Failed.
Threshold: 1.000000
Severity: Major
TSSPI-ChkTls50Dev2000
Monitors Windows Server 2000 TS Device CALs usage.
Execute every: 15min
Command:
TSSPITls --dev2000 --policy=<$SRCNAME>
Rules:
•
•
•
Description: Major.
Threshold: 98.000000
Severity: Major
Description: Minor.
Threshold: 90.000000
Severity: Minor
Description: Warning.
Threshold: 85.000000
Severity: Warning
TSSPI-ChkTls50Temp
Monitors Temporary Licenses
Quick Reference 99
Execute every: 15min
Command:
TSSPITls --temp2000 --policy=<$SRCNAME>
Rules:
•
Description: Warning.
Threshold: 20.000000
Severity: Warning
TSSPI-ChkTls52Dev2000
Monitors Windows Server 2000 TS Device CALs usage.
Execute every: 15min
Command:
TSSPITls --dev2000 --policy=<$SRCNAME>
Rules:
•
•
•
Description: Major.
Threshold: 98.000000
Severity: Major
Description: Minor.
Threshold: 90.000000
Severity: Minor
Description: Warning.
Threshold: 85.000000
Severity: Warning
TSSPI-ChkTls52Dev2003
DESCRIPTION Monitors Windows Server 2003 TS Device CALs usage.
Execute every: 15min
Command:
TSSPITls --dev2003 --policy=<$SRCNAME>
Rules:
•
•
Description: Major.
Threshold: 98.000000
Severity: Major
Description: Minor.
Threshold: 90.000000
Severity: Minor
100 User’s Guide
•
Description: Warning.
Threshold: 85.000000
Severity: Warning
TSSPI-ChkTls52Temp
Monitors Temporary Licenses
Execute every: 15min
Command:
TSSPITls --temp2003 --policy=<$SRCNAME>
Rules:
•
Description: Warning.
Threshold: 20.000000
Severity: Warning
TSSPI-ChkTls52User2003
Monitors Windows Server 2003 TS User CALs usage.
Execute every: 15min
Command:
TSSPITls --user2003 --policy=<$SRCNAME>
Rules:
•
•
•
Description: Major.
Threshold: 98.000000
Severity: Major
Description: Minor.
Threshold: 90.000000
Severity: Minor
Description: Warning.
Threshold: 85.000000
Severity: Warning
TSSPI-ChkTlsService
Monitors Terminal Server Licensing service.
Execute every: 5min
Command:
TSSPISwitch.cmd chktlssvc <$SRCNAME>
Rules:
Quick Reference 101
•
•
•
Description: Not installed.
Threshold: 2.000000
Severity: Critical
Description: Running.
Threshold: 1.000000
Severity: Normal
Description: Not running.
Threshold: 0.000000
Severity: Critical
TSSPI-ChkUserLogonProcess
Monitors duration of the complete Terminal Server user logon process.
Execute every: 5min
Command:
TSSPISwitch.cmd chkpslogon Phase0 TSSPI-ChkUserLogonProcess
Rules:
•
•
•
Description: time-out.
Threshold: 1000000000.000000
Severity: Major
Description: major.
Threshold: 180000.000000
Severity: Major
Description: warning.
Threshold: 120000.000000
Severity: Warning
TSSPI-ChkUserLogonProcessCompleted
Monitors whether all phases of the user logon process have completed successfully
on the Terminal Server.
Execute every: 5min
Command:
TSSPISwitch.cmd chkpslogon Completed TSSPI-ChkUserLogonProcessCompleted
Rules:
•
Description: major.
Threshold: 2.000000
Severity: Major
102 User’s Guide
TSSPI-ChkUserLogonProcessPh1
Monitors duration of the user profile loading phase of the Terminal Server user
logon process.
Execute every: 5min
Command:
TSSPISwitch.cmd chkpslogon Phase1 TSSPI-ChkUserLogonProcessPh1
Rules:
•
•
•
Description: time-out.
Threshold: 1000000000.000000
Severity: Major
Description: major.
Threshold: 180000.000000
Severity: Major
Description: warning.
Threshold: 120000.000000
Severity: Warning
TSSPI-ChkUserLogonProcessPh2
Monitors duration of the applying group policies phase of the Terminal Server user
logon process.
Execute every: 5min
Command:
TSSPISwitch.cmd chkpslogon Phase2 TSSPI-ChkUserLogonProcessPh2
Rules:
•
•
•
Description: time-out.
Threshold: 1000000000.000000
Severity: Major
Description: major.
Threshold: 180000.000000
Severity: Major
Description: warning.
Threshold: 120000.000000
Severity: Warning
TSSPI-ChkUserLogonProcessPh3
Monitors duration of the user initialization phase of the Terminal Server user logon
process.
Quick Reference 103
Execute every: 5min
Command:
TSSPISwitch.cmd chkpslogon Phase3 TSSPI-ChkUserLogonProcessPh3
Rules:
•
•
•
Description: time-out.
Threshold: 1000000000.000000
Severity: Major
Description: major.
Threshold: 180000.000000
Severity: Major
Description: warning.
Threshold: 120000.000000
Severity: Warning
TSSPI-DscServiceModel
Upload Terminal Server service model.
Rules:
•
Description: Autodiscovery.
Threshold: 1.000000
Severity: Warning
104 User’s Guide
SPI for Terminal Server Reports and Report Groups
When you install SPI for Terminal Server, a new top level report group is added in
the HP OpenView Operations administrator GUI. The SPI for Terminal Server report
group contains all reports, used for managing your Terminal Server environment.
When you use SPI for Terminal Server, reports are grouped by their purpose. This
structure helps you to quickly find the report that you need to use.
Metric Lists
The SPI for Terminal Server report family contains the following metric lists:
TSSPI_PSLD
Summarization: 300
Retain days: 28
Metrics:
•
USERNAME
•
DURATION
•
PH1PROFILE
•
PH3USERINIT
•
PHCOMPLETED
•
PSLDKEY
•
STARTTIME
•
PH2POLICY
TSSPI_SESSINFO
Summarization: 300
Retain days: 28
Metrics:
•
KEY_SESSION
•
CLIENTPROTOCOLTYPE
Quick Reference 105
•
USERNAME
•
WINSTATIONNAME
•
SESSIONID
•
CLIENTADRESS
•
USERDOMAINNAME
•
CLIENTNAME
•
CONNECTSTATE
•
APPLICATIONNAME
•
CLIENTHARDWAREID
TSSPI_SESS
Summarization: 300
Retain days: 28
Metrics:
•
KEY_SESSION
•
TOTALFRAMES
•
USERNAME
•
CPUTIME
•
TOTALERRORS
•
PAGEFILEBYTES
•
WORKINGSETSIZE
•
TOTALTIMEOUTS
•
TOTALBYTES
•
TOTALTRANSPORTERRORS
•
SESSIONNAME
•
HANDLECOUNT
•
THREADCOUNT
TSSPI_PROFILES
Summarization: 300
Retain days: 28
106 User’s Guide
Metrics:
•
MEDIA_SIZE
•
TIME
•
CUSTOM_EXT
•
FILE_COUNT
•
EXECUTABLES_SIZE
•
EXECUTABLES_EXT
•
CUSTOM_SIZE
•
ROAMING_SIZE
•
ROAMING_FILE_COUNT
•
CUSTOM_COUNT
•
FULL_SIZE
•
EXECUTABLES_COUNT
•
MEDIA_EXT
•
MEDIA_COUNT
TSSPI_LIC
Summarization: 300
Retain days: 28
Metrics:
•
LICNAME
•
TOTALLIC
•
USEDLIC
•
SERVERNAME
TSSPI_SRV
Summarization: 300
Retain days: 28
Metrics:
•
INACTIVESESSIONS
•
ACTIVESESSIONS
Quick Reference 107
•
TOTALSESSIONS
•
HINSTANCENAME
TSSPI_PROFILE
Summarization: 300
Retain days: 28
Metrics:
•
MEDIA_SIZE
•
TIME
•
CUSTOM_EXT
•
FILE_COUNT
•
EXECUTABLES_SIZE
•
EXECUTABLES_EXT
•
CUSTOM_SIZE
•
ROAMING_SIZE
•
ROAMING_FILE_COUNT
•
CUSTOM_COUNT
•
FULL_SIZE
•
EXECUTABLES_COUNT
•
MEDIA_EXT
•
USER
•
MEDIA_COUNT
Report Categories
SPI for Terminal Server provides the following report categories and reports:
TS - User Profiles
TSSPI_TsProfExecFileStatsServerDay
Server statistics on executable files in user profiles (yesterday)
108 User’s Guide
TSSPI_TsProfUserProfileDetailsDay
User profile details (yesterday)
TSSPI_TsProfCustFileStatsServerDay
Server statistics on custom files in user profiles (yesterday)
TSSPI_TsProfTop30UsersMediaFilesSizeDay
Top 30 users by size of media files in user profile (yesterday)
TSSPI_TsProfMediaFileStatsServerDay
Server statistics on media files in user profiles (yesterday)
TSSPI_TsProfTop30UsersExecFilesSizeDay
Top 30 users by size of executable files in user profile (yesterday)
TSSPI_TsProfTopServersProfileSizeDay
Top servers by size of user profiles (yesterday)
TSSPI_TsProfTop30UsersProfileSizeDay
Top 30 users by their user profile size (yesterday)
TSSPI_TsProfTop30UsersCustFilesSizeDay
Top 30 users by size of custom files in user profile (yesterday)
TS - Top Users
TSSPI_TsTop30UsersSesNetTrafUse28Days
Top 30 users with highest session network traffic (last 28 days)
TSSPI_TsTop30UsersAvgPhyMemUse28Days
Top 30 users with highest session physical memory consumption (last 28 days)
TSSPI_TsTop30UsersSesNetErr28Days
Top 30 users with highest session network errors (last 28 days)
TSSPI_TsTop30UsersAvgVirMemUse28Days
Top 30 Users with the highest session virtual memory consumption (last 28 days)
TSSPI_TsTop30UsersAvgCpuCons28Days
Top 30 users with highest session CPU consumption (last 28 days)
Quick Reference 109
TS - Top Clients
TSSPI_TsTop30ClientsSesNetErr28Days
Top 30 clients with highest session network errors (last 28 days)
TSSPI_TsTop30ClientsAvgCpuCons28Days
Top 30 clients with highest session CPU consumption (last 28 days)
TSSPI_TsTop30ClientsAvgVirMemUse28Days
Top 30 clients with highest session virtual memory consumption (last 28 days)
TSSPI_TsTop30ClientsAvgPhyMemUse28Days
Top 30 clients with highest session physical memory consumption (last 28 days)
TSSPI_TsTop30ClientsSesNetTrafUse28Days
Top 30 clients with highest session network traffic (last 28 days)
TS - User Logon Process
TSSPI_TsLogProcSrvUnfinPhase2Day
Servers with Issues in Phase 3 User Logon Phase (yesterday)
TSSPI_TsLogProcTop30SrvCompletedLogonsDay
Top 30 Servers with Highest Number of Completed User Logons (yesterday)
TSSPI_TsLogProcUserLogonDetailsDay
User Logon Process Details (yesterday)
TSSPI_TsLogProcSrvUnfinPhasesDay
Servers with User Logon Issues (yesterday)
TSSPI_TsLogProcSrvUnfinPhase0Day
Servers with Issues in Phase 1 User Logon Phase (yesterday)
TSSPI_TsLogProcTop30UsersWorstLT28Days
Top 30 Users with Highest Average Logon Time Duration (last 28 days)
TSSPI_TsLogProcTop30SrvWorstLogonTime28Days
Top 30 Servers with Highest Average User Logon Time (last 28 days)
110 User’s Guide
TSSPI_TsLogProcSrvUnfinPhase1Day
Servers with Issues in Phase 2 User Logon Phase (yesterday)
TSSPI_TsLogProcTop30SrvWorstPh1DurDay
Top 30 Servers with Longest Phase 1 User Logon Phase (yesterday)
TSSPI_TsLogProcSrvLogonDetailsDay
User Logon Process Details per Server (yesterday)
TSSPI_TsLogProcTop30SrvWorstPh2DurDay
Top 30 Servers with Longest Phase 2 User Logon Phase (yesterday)
TSSPI_TsLogProcTop30SrvWorstPh3DurDay
Top 30 Servers with Longest Phase 3 User Logon Phase (yesterday)
TSSPI_TsLogProcTop30UsersUnfinPhaDay
Top 30 Users with Highest Number of Unsuccessful Logons (yesterday)
TLS - Terminal Server Licenses
TSSPI_TlsLicUsedAvail28Days
Terminal Server license use (last 28 days)
TS - Users
TSSPI_TsAccountingUser28Days
User accounting (last 28 days)
TSSPI_TsServerUserStatDay
User session details (last 28 days)
TS - Server
TSSPI_TsServerSessState28Days
Number of active/disconnected sessions on server (last 28 days)
TSSPI_TsServerLogonLogoff28Days
Number of session logons/logoffs (last 28 days)
Quick Reference 111
TSSPI_TsServerSessStateGroup28Days
Number of active/disconnected sessions in group (last 28 days)
TS - Top Servers
TSSPI_TsTopSrvSessAvg28Days
Shows the number of active sessions on each server for the last 28 days
TS - Threshold Assistant
TSSPI_TsThrAssAll28Days
Threshold Assistant for policies (last 28 days)
Autogroups
SPI for Terminal Server provides the following autogroup:
Product Terminal Server
Group: SPI for Terminal Server
Datasource: ^TSSPI.*
112 User’s Guide
SPI for Terminal Server Graphs
The SPI for Terminal Server graph family contains the following graph categories
and graphs:
Terminal License Server (Win2003) - License Use
This graph category contains the following graphs:
Temporary Licenses for Windows Server 2003 - Device CALs
Shows used licenses for Windows 2003 Terminal Server License Server licenses of
type "Temporary Licenses for Windows Server 2003 - Terminal Server Per Device
CAL Token"
Metrics:
•
TSSPI_LIC:TSSPI_LIC:USEDLIC
Licenses for Windows Server 2003 - Device CALs
Shows used and available licenses for Windows 2003 Terminal Server License Server
licenses of type "Windows Server 2003 - Terminal Server Per Device CAL Token"
Metrics:
•
TSSPI_LIC:TSSPI_LIC:TOTALLIC
•
TSSPI_LIC:TSSPI_LIC:USEDLIC
Licenses for Windows 2000 Server - Device CALs
Shows used licenses for Windows 2003 Terminal Server License Server licenses of
type "Existing Windows 2000 Server - Terminal Services CAL Token (per device)"
Metrics:
•
TSSPI_LIC:TSSPI_LIC:USEDLIC
Licenses for Windows Server 2003 - User CALs
Shows used and available licenses for Windows 2003 Terminal Server License Server
licenses of type "Windows Server 2003 - Terminal Server Per User CAL Token"
Quick Reference 113
Metrics:
•
TSSPI_LIC:TSSPI_LIC:TOTALLIC
•
TSSPI_LIC:TSSPI_LIC:USEDLIC
Terminal Server - User Profiles
This graph category contains the following graphs:
Custom Files Size
Shows the total size of custom-defined files across all user profiles on the system
Metrics:
•
TSSPI_PROFILES:TSSPI_PROFILES:CUSTOM_SIZE
Executable Files Size
Shows the total size of executable files present across all user profiles
Metrics:
•
TSSPI_PROFILES:TSSPI_PROFILES:EXECUTABLES_SIZE
Media Files Size
Shows the total size of media files across all user profiles on the system
Metrics:
•
TSSPI_PROFILES:TSSPI_PROFILES:MEDIA_SIZE
Custom Files Count
Shows the number of custom-defined files across all user profiles on the system
Metrics:
•
TSSPI_PROFILES:TSSPI_PROFILES:CUSTOM_COUNT
Media Files Count
Shows the number of media files across all user profiles on the system
Metrics:
114 User’s Guide
•
TSSPI_PROFILES:TSSPI_PROFILES:MEDIA_COUNT
Executable Files Count
Shows the number of executable files present across all user profiles
Metrics:
•
TSSPI_PROFILES:TSSPI_PROFILES:EXECUTABLES_COUNT
Profiles Size
Shows total and roaming size that all user profiles occupy on the system
Metrics:
•
TSSPI_PROFILES:TSSPI_PROFILES:ROAMING_SIZE
•
TSSPI_PROFILES:TSSPI_PROFILES:FULL_SIZE
Terminal Server - User Logon Process
This graph category contains the following graphs:
User Logon Duration (Phase 1)
Shows duration of the phase 1 of the logon process for each individual user that
logged-in to the system
Metrics:
•
TSSPI_PSLD:TSSPI_PSLD:PH1PROFILE
User Logon Duration (Phase 3)
Shows duration of the phase 3 of the logon process for each individual user that
logged-in to the system
Metrics:
•
TSSPI_PSLD:TSSPI_PSLD:PH3USERINIT
Terminal Server - Session Resource Use
This graph category contains the following graphs:
Quick Reference 115
Session Network Timeouts (no Console)
Shows total number of session network timeouts for individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:TOTALTIMEOUTS
Session Network Frames (no Console)
Shows total number of session network frames used by individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:TOTALFRAMES
Session Physical Memory (no Console)
Shows physical memory consumption for individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:WORKINGSETSIZE
Session Virtual Memory (no Console)
Shows virtual memory consumption for individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:PAGEFILEBYTES
Session Network Transport Errors (no Console)
Shows total number of session network transport errors for individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:TOTALTRANSPORTERRORS
Session Network Bytes (no Console)
Shows total number of session network bytes used by individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:TOTALBYTES
116 User’s Guide
Session Thread Count (no Console)
Shows number of threads used by individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:THREADCOUNT
Session Network Errors (no Console)
Shows total number of session network errors for individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:TOTALERRORS
Session Handle Count (no Console)
Shows number of handles used by individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:HANDLECOUNT
Session CPU (no Console)
Shows CPU consumption for individual sessions
Metrics:
•
TSSPI_SESS:TSSPI_SESS:CPUTIME
Terminal Server - Active Session Load
This graph category contains the following graphs:
Active Sessions vs. System Network IO
Shows the number of active sessions vs. system network IO rate
Metrics:
•
TSSPI_SRV:TSSPI_SRV:ACTIVESESSIONS
•
GLOBAL:GBL_NET_OUT_PACKET_RATE
•
GLOBAL:GBL_NET_IN_PACKET_RATE
Quick Reference 117
Active Sessions vs. System Virtual Memory
Shows the number of active sessions vs. system virtual memory utilization
Metrics:
•
TSSPI_SRV:TSSPI_SRV:ACTIVESESSIONS
•
GLOBAL:GBL_SWAP_SPACE_UTIL
Active Sessions vs. System Disk IO
Shows the number of active sessions vs. system disk IO rate
Metrics:
•
TSSPI_SRV:TSSPI_SRV:ACTIVESESSIONS
•
GLOBAL:GBL_DISK_PHYS_IO_RATE
Active Sessions vs. System CPU
Shows the number of active sessions vs. system CPU utilization
Metrics:
•
TSSPI_SRV:TSSPI_SRV:ACTIVESESSIONS
•
GLOBAL:GBL_CPU_TOTAL_UTIL
Active Sessions vs. System Physical Memory
Shows the number of active sessions vs. system physical memory utilization
Metrics:
•
TSSPI_SRV:TSSPI_SRV:ACTIVESESSIONS
•
GLOBAL:GBL_MEM_UTIL
Terminal Server - Sessions
This graph category contains the following graphs:
All Sessions
Shows the number of all sessions on the server
118 User’s Guide
Metrics:
•
TSSPI_SRV:TSSPI_SRV:TOTALSESSIONS
Active Sessions
Shows the number of active sessions on the server
Metrics:
•
TSSPI_SRV:TSSPI_SRV:ACTIVESESSIONS
Inactive Sessions
Shows the number of inactive sessions on the server
Metrics:
•
TSSPI_SRV:TSSPI_SRV:INACTIVESESSIONS
Terminal Server - User Logon Process
This graph category contains the following graphs:
Completed User Logon Phases
Shows the number of completed user logon process phases for each individual user
that logged-in to the system
Metrics:
•
TSSPI_PSLD:TSSPI_PSLD:PHCOMPLETED
User Logon Duration (Phase 2)
Shows duration of the phase 2 of the logon process for each individual user that
logged-in to the system
Metrics:
•
TSSPI_PSLD:TSSPI_PSLD:PH2POLICY
User Logon Duration
Shows duration of the logon process for each individual user that logged-in to the
system
Quick Reference 119
Metrics:
•
TSSPI_PSLD:TSSPI_PSLD:DURATION
Average User Logon Duration
Shows the average duration of the logon process for all users that logged-in to the
system
Metrics:
•
TSSPI_PSLD:TSSPI_PSLD:DURATION
Terminal License Server (Win2000) - License Use
This graph category contains the following graphs:
Temporary Licenses for Windows 2000 Server
Shows used licenses for Windows 2000 Terminal Server License Server licenses of
type "Temporary Licenses for Existing Windows 2000 License"
Metrics:
•
TSSPI_LIC:TSSPI_LIC:USEDLIC
Licenses for Windows 2000 Server
Shows used licenses for Windows 2000 Terminal Server License Server licenses of
type "Existing Windows 2000 License"
Metrics:
•
TSSPI_LIC:TSSPI_LIC:USEDLIC
120 User’s Guide
Chapter 8
Troubleshooting
Troubleshooting Assistance
This chapter describes possible errors that can occur while using SPI for Terminal
Server and gives instructions on how to solve them.
122 User Guide