Microsoft has decided to revert to the Remote Desktop Shadowing (Shadow Connection) feature on Windows 2012 R2 and Windows 8.1. RDS Shadow also works in the most recent versions of the operating system: Windows Server 2016, Windows Server 2019 and Windows 10. Stb erom upgrade tool. Our IDEAL Administration and IDEAL Remote software allows to manage the Shadow Remote. Upgrading to Windows 10 Pro just to use a specific functionality is not wise and when there are so many remote desktop apps available on Windows Store. Nevertheless, nobody can rule out the sophistication of a native Windows tool.
| @ECHOOFF |
| MODE CON:COLS=80 LINES=40 |
| COLOR 1A |
| SETLOCALEnableDelayedExpansion |
| :ENTRY |
| CLS |
| CALL :PRINTBAR |
| ECHO^| RDP Session Shadow Version 2.0 ^| |
| ECHO^| By Craig Crawford ^| |
| ECHO^|------------------------------------------------------------------------------^| |
| ECHO^| This is designed to be used with: ^| |
| ECHO^| * Windows 10 / 2016 and above, ^| |
| ECHO^| * RDP Wrapper Library: https://github.com/stascorp/rdpwrap ^| |
| CALL :PRINTBAR |
| IF [%1][--noping] ( |
| ECHO^| --noping switch enabled. The remote host will not be probed by echo requests ^| |
| ECHO^| before attemping to connect. ^| |
| CALL :PRINTBAR |
| SETNOPING=TRUE |
| ) |
| SET /P PC='Enter PC: ' |
| CALL :PRINTBAR |
| SETCOUNT=0 |
| ECHO Attempting to connect to %PC%.. |
| IF [%NOPING%][TRUE] GOTO NOPING |
| PING%PC% -n 1 -w 100|FIND'Ping request could not find host %PC%'>NUL |
| IF'%ERRORLEVEL%'EQU'0'GOTO FAILED_NOHOST |
| :PING |
| SET /A COUNT+=1 |
| IF'%COUNT%'GEQ'5'GOTO FAILED_NOECHO |
| ECHO Attempting to connect to %PC%. Attempt %COUNT% of 5. |
| PING%PC% -n 1 -w 100>NUL |
| IF'%ERRORLEVEL%'EQU'0' ( |
| ECHO Connected. |
| :NOPING |
| CALL :PRINTBAR |
| ECHO Attempting to display user sessions.. |
| ECHO. |
| QWINSTA /SERVER:%PC% |
| ECHO. |
| SET /P SESSIONID='Enter Session ID: ' |
| MSTSC /v:%PC% /control /shadow:!SESSIONID! |
| GOTO END |
| ) ELSE ( |
| ECHO%PC% failed to respond, trying again in 5 seconds.. |
| TIMEOUT /T 5 /NOBREAK >NUL |
| GOTOPING |
| ) |
| :FAILED_NOECHO |
| CALL :PRINTBAR |
| ECHO Failed to connect to the remote computer: [ %PC% ]. |
| ECHO The remote computer is not responding to ping requests. |
| GOTO END |
| :FAILED_NOHOST |
| CALL :PRINTBAR |
| ECHO Failed to connect to the remote computer: [ %PC% ]. |
| ECHO Unable to find the host's DNS entry. Does it exist? |
| GOTO END |
| :END |
| CALL :PRINTBAR |
| PAUSE |
| GOTO ENTRY |
| :PRINTBAR |
| ECHO |
A system administrator can use shadow session mode to view and remotely manage an active RDP session for any user. This mode has been supported almost since the early versions of Microsoft Terminal Server and was unexpectedly removed from Windows Server 2012 (due to the transfer of the RDP stack from kernel to user mode). Microsoft has decided to revert to the Remote Desktop Shadowing (Shadow Connection) feature on Windows 2012 R2 and Windows 8.1. RDS Shadow also works in the most recent versions of the operating system: Windows Server 2016, Windows Server 2019 and Windows 10.
Our IDEAL Administration and IDEAL Remote software allows to manage the Shadow Remote Control.
You have two options for this:
Rdp Shadow Command
1. Right click on your RDP server, Remote Control / Deployment, Shadow Remote Desktop, Select the desired RDP session. This solution displays the first 25 sessions present on your RDP server.
Important: The user will be asked to authorize your connection.
2. Right click on your RDP server, Print and Sharing Center, Terminal Services Sessions tab. All RDP sessions present on the server are displayed. You can search for a user name using the Action, Search menu.
Mstsc Shadow Windows 10 Login
Two Shadow modes are possible: With connection authorization request and Without authorization request.
Shadow Rdp Control
Important: To use the mode without authorization request, you will need to set up a GPO. To do this, enable Group Policy by going to gpedit.msc, then Local Computer Policy, Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Connections and enable the 'Define rules for remote control of Remote Desktop Services user sessions' setting and select the 'Full control without user authorization' option from the drop-down list.