Using Windows Terminal Services

Windows Terminal Services (WTS) is a feature that allows more than one user to log onto a Windows machine. This functionality is also referred to as simultaneous user environments or terminal services.

Users can logon to the Windows machine from the console (the screen attached to the Windows machine) or from a remote desktop client.

On Windows 8, Windows 8.1, and Windows 10, more than one user can logon at the console, although only one of the logged-on users will be able to see his desktop at any time. This terminal services function is called fast user switching.

Citrix MetaFrame allows administrators to configure their WTS servers to run individual applications, and to configure each user to run different applications on different servers. Thus, instead logging on to a WTS server, a user launches preconfigured applications from his Citrix environment running on their client machine. Citrix then logs onto the appropriate WTS server and runs the application. When the user closes the application, Citrix shuts down the application, waits for all processes that were started by the application to terminate, and then logs off from the WTS server.

Notes:
  1. A message file log is not maintained for each WTS logon session. Only one message log file is maintained for the WTS server.
  2. When Z and I Emulator for Windows is used in a WTS environment, the maximum of 52 sessions (A-Z or a-z) applies to each WTS logon session. There is not a limit of 52sessions per WTS server.

Session IDs

In simultaneous user environments such as WTS, each time a user logs on, that specific logon session is assigned a session ID. When a user logs on at the console, that session is assigned the session ID 0 (zero)--this is also called the server console session. When a user logs on from a remote desktop, the assigned session IDs begin with session 1.

Trace Facility

For simultaneous user environments such as WTS, the Connectivity functions are only available for users logged in as session 0.

Each user can run his own trace facility, which gives information from that user's specific WTS logon session. However, there are trace options that enable tracing from device drivers, which are not associated with any specific WTS logon session. Thus, those options only appear on the trace facility that is started in the WTS console session (session 0).