I'm trying to enable automatic shadowing on my Windows 11 Pro machine where I have set up a Remote Desktop Protocol (RDP) server. I've successfully configured it so that I can log into the console session and connect via RDP at the same time, using the command `mstsc /v: /shadow:1 /noconsentprompt /control`, which works without licensing issues according to the EULA. However, when I'm using an RDP mobile app or other similar client, it doesn't allow me to send those command line switches, resulting in the console session being disconnected. I want to configure the RDP server to automatically shadow the console session so that it behaves as if those switches were sent from the client, even if the client doesn't support it. Any thoughts on how to achieve this?
4 Answers
It seems like you might be misunderstanding how Windows handles these features. The shadowing is only supposed to be available for server versions, not for workstation versions like what you have. If you really want to shadow someone effectively, using software like Dameware is your best bet since it’s already designed for this.
You're not using the right executable that can utilize those arguments. Have you thought about trying VNC Server? You can link it to your domain credentials on the RDP server instead.
The `/shadow:1 /noconsentprompt /control` options only work with `mstsc.exe`, and unfortunately, you can’t control this behavior from the server side. What’s your goal, exactly? You can really only be in one place at a time when shadowing is involved.
You can't force the server to act as if those arguments were sent. Shadowing isn't designed to work this way on regular RDP for Pro versions. If you have the right setup on a properly licensed RDP server, shadowing can work as intended, but on workstation versions, you're limited.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures