Skip to main content
Terminal Services Managerv26.11 · Nov 2026 Download View Pricing

System requirements

Terminal Services Manager running

Computer that runs Terminal Services Manager

  • Operating system: Windows 10 or later, or Windows Server 2016 or later.
  • Architecture: 64-bit (x64).
  • Network: routable access to every server you want to monitor (TCP/IP).

Servers you want to monitor

Any Windows computer that runs Remote Desktop Services. A computer that is not a Remote Desktop Services host can stay in the list, but its session and process counts stay at zero.

For each remote computer the program uses several Windows administration interfaces:

Feature Interface used
Session and user lists Windows Terminal Services (WTS) API
Performance counters (CPU, memory, disk, network) Performance Data Helper (PDH), which needs the Remote Registry service
Server state check ICMP ping or a TCP connect to a port you choose (or no check)
Remote Desktop sessions RDP, through the standard Remote Desktop client (mstsc.exe)

The account you run Terminal Services Manager under must have administrator rights on the remote computer. For workgroup or cross-domain scenarios, run the program under an account that has those rights (see Connection credentials).

What needs to be reachable

On the remote computer make sure that:

  • The Remote Registry service is running. It is required for performance-counter collection.
  • The firewall allows the Windows administration traffic the program needs (Remote Service Management, Windows Management Instrumentation, and File and Printer Sharing) for the network profile you are connecting through.
  • Remote Desktop Services is installed (always present on Windows Server; needs to be enabled on workstation editions through System Properties).

The method used to decide whether a server is reachable is configurable on the Network preferences page, where you can choose an ICMP ping, a TCP connect to a port, or no check at all.

Was this page helpful?