shadow: Monitor another Terminal Services session.
The command: "shadow" is on Windows 11, 10, .. not available
The examples for the command "shadow"
Here are some examples of using the `SHADOW`
command in Windows XP:
Example 1: Monitor session (by session name):
SHADOW session name /SERVER:server name
- Here the Terminal Service session with the specified session name on the specified server is monitored.
Example 2: Monitor session (using session ID):
SHADOW session identifier /SERVER:servername
- This example monitors the Terminal Services session with the specified session ID on the specified server.
Example 3: Monitor session with display of information:
SHADOW session name /SERVER:server name /V
- This monitors the Terminal Service session with the specified session name on the specified server and displays additional information about the functions being performed.
Please note that "Session Name"
or "Session ID"
is the specific label of the Terminal Services session you want to monitor, and "Server Name"
is optional and indicates the server on which the session exists (the default is the current server).
It is important to note that the functions of the `SHADOW`
command may have been replaced by other mechanisms or commands in later versions of Windows. In more modern versions of Windows, this could be done, for example, through Remote Desktop management tools or PowerShell cmdlets.
"shadow" Excerpt from Microsoft Windows Help
Microsoft Windows XP [Version 5.1.2600]
(c) Copyright 1985-2001 Microsoft Corp.
Monitor another Terminal Services session.
SHADOW [/SERVER:servername] [/V]
sessionname Identifies the session with name sessionname.
sessionid Identifies the session with ID sessionid.
/SERVER:servername The server containing the session (default is current).
/V Display information about actions being performed.
Important information, tips for the "shadow" command
command is no longer supported in more modern versions of Windows and PowerShell is used instead, especially with the Remote Desktop Services (RDS). If you want to monitor or manage sessions, you can use PowerShell cmdlets. Please note that availability and functionality may vary depending on the version of Windows.
There are several cmdlets in PowerShell for managing sessions and remote desktop functionality, including Get-RDUserSession, Invoke-RDUserLogoff, and Invoke-RDUserLogon. Here is a simple example of how you can retrieve sessions:
Get-RDUserSession -ConnectionBroker YourConnectionBroker
Importantly, many of the RDS cmdlets require administrative rights and the Remote Desktop Services role on the server. You can also run these cmdlets on a remote server by using the `-ComputerName`
Before using PowerShell cmdlets, you should ensure that you have the necessary permissions and review the cmdlet documentation to ensure that you are correctly performing the desired actions. PowerShell offers advanced functionality compared to the older `SHADOW`
command, but may require more in-depth study of the syntax and options.