When monitoring a lot of terminal-servers based on Windows 2012r2 or 2016 RDS deployments, it would be really timesaving to be able to shadow active sessions shown in the Dashboard Tab by right-clicking the session to shadow.
It would be even nicer to have a dropdown submenu on the contextmenu-items
to select options like /Control and/or /noConsentPrompt.
Commandline in the background should than look someting like:
MSTSC /v:servername /shadow:sessionid (/control) (/noConsentPrompt)
this can have different reasons. Mstsc may have different default values which may affect performance. I also should note, that Royal TS is hosting multiple instances of the RDP ActiveX controls in a single process and they all share a single UI thread. When multiple connections are "drawing" on the UI thread, it's busier in Royal TS compared to have multiple mstsc.exe processes where each has its own UI thread.
Thanks for the updates, it's working great so far, nice job!
I would like to ask why using royal ts remote rdp it's a little bit slower than the native builtin mstsc? Not that obvious but very subtle slow.
as far as I know, mstsc.exe doesn't allow to pass on credentials via command line arguments. Or am I missing something?
I just finished my Powershell script for shadowing and now it is implemented in version 6 ... :)
But one problem we have is the current user session the mstsc.exe is running in. All people from IT have normal windows domain users, no special rights on domain, computers, servers etc. For administrative work we are using individual admin accounts. In my script, I start mstsc with my admin account and can connect without the /prompt parameters. With the new shadowing option in RoyalTS, my current logged on user is used and I cannot connect. For sure it is possible with /prompt parameter but then I have to put in my admin credentials each time I connect to a computer. Would it be possible to start mstsc with the credentials configured in the RDP connection? Even better, use the configured credentials from the RDP connection.
providing a default setting UI for this option is a bit more effort. May I kindly ask you to create a dedicated feature request for that in order to track demand for this particular feature?
If yo turn "Control" of by Default, could a setting for defaults be implemented so one can control the default behavior if one desire to use Control or the other switches differently as others.
We would for example always use the Control Option enabled
Thanks for the feedback, Kevin. I have implemented a "Control" option (which is off by default).
btw `/Control` should be by default ticked off when adding to shadow menu, make sense when you want to shadowing a session, usually you want them to view only mode, not controlling
latest version is not working for view only (but control works) @stefan
you should not include `/control` because the main purpose of shadowing is to "view only" current rdp session, not "contrl" the current session(or at least let user choose a option)
example view only the current rdp session using bat:
set /P rcomp="vm PC: "
set /P rid="Enter RDP user ID: "
start mstsc /shadow:%rid% /v:%rcomp% /noConsentPrompt /prompt
I think you guys should add `/control` to shadow menu, by default without `/control` means "view only"
The next release will have a UI where you can enable/disable the /prompt and the /noConsentPrompt argument before you execute the shadow session command.
I guess the logged in Account has no access rights.
I have the same with non admin account.
Can the string be customized?
We would for example need "/prompt" to login with admin credentials and remove "/noConsentPrompt" as we require the consent of our users for remote session.
I honestly can't tell. Royal TS executes the command line as discussed in this topic. Can you check your task manager and compare the command line Royal TS executes with one successful you execute manually?
I have installed version 6 and checked the Shadow Session via Dashboard with high expectations. Unfortunately, this does not work yet and I get the following error message. What am I doing wrong? What have I overlooked?
we are currently working on the V6 release and hope to get it out by the end of the week. Stay tuned.
hi @Stefan Koell
Do you have any update info about shadow beta? Thanks