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

Shadowing a user

Shadow opens a remote-control window on the user's session. You see what they see; depending on the options, you can also share their keyboard and mouse. The connection runs over RDP and uses the standard Microsoft mstsc.exe client.

Shadow dialog

How to do it

Select one session in the User sessions list, then:

  • Click the Shadow... button in the command row,
  • Right-click and choose Shadow..., or
  • Choose Users > Shadow... from the main menu.

The Shadow dialog opens. Its title names the target, for example Shadow - ahall@RDS-NYC-02, and the Remote session label shows the session.

Shadow options

  • View - watch the session without taking input.
  • Control - share keyboard and mouse with the user.
  • Prompt for user consent - when ticked, the user sees a confirmation prompt and the shadow only starts after they accept. When cleared, the shadow starts without prompting. Whether unprompted shadowing is permitted depends on the server's group policy and the user's permissions; see the RDS properties dialog and the local Set rules for remote control of Remote Desktop Services user sessions policy.

The dialog has no monitor option: Remote Desktop ignores one when shadowing. Extra switches for mstsc.exe can be added in Preferences > Terminal Services, under Additional mstsc parameters when shadowing.

Click OK to start the shadow. Terminal Services Manager launches mstsc.exe with the /shadow switch for the session, plus /control when you chose Control and /noConsentPrompt when the consent box is cleared. Close the mstsc.exe window to end the shadow.

Requirements

  • The account running the program needs permission to shadow on the target server (see Connection credentials).
  • The computer that runs Terminal Services Manager needs mstsc.exe.

When shadow fails

  • Access denied - the connecting account does not have permission. Grant it the right on the session host, or run the program under an account that has it.
  • The session is not in a connectable state - the user is logging off, has been reset, or the session is still initializing. Try again in a few seconds.
  • The user declined the prompt - they clicked No on the consent dialog. Talk to them, then retry.
Was this page helpful?