@Stefan:
Royal TS already has access to the computer name (RDP Server) and the Session ID. Why not just send a scripted call to C:\Windows\System32\mstsc.exe /v:%servername% /shadow:%sessionid% /control /noConsentPrompt.
It seems a popular demand of Royal Apps customers.
I just implemented the command to the terminal services / remote desktop dashboard. This will be available in the next beta release, probably by the end of the week.
Regards,
Stefan
@Matthew:
I guess we can implement something like that but it will then be started as external application and not embedded. I will put this on the TODO list and hope we can do this some time after V6 has been released.
Regards,
Stefan
Hi all,
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.
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.
Any progress on this? I'm just installing RoyalTS but shadowing would be an AWESOME feature. We'd likely get licenses for the whole I.T. department.
Hi,
I'm sorry for not replying earlier. We missed this thread somehow and last weeks response triggered another notification.
I've looked into session shadowing and the main issue is that we are not using MSTSC in Royal TS. We are using the ActiveX control and according to the docs, there's no API to initiate shadowing. As soon as Microsoft provides the APIs, we're happy to integrate it into our dashboard.
Regards,
Stefan
Hi Timo,
as far as I know, mstsc.exe doesn't allow to pass on credentials via command line arguments. Or am I missing something?
Regards,
Stefan
hi @Stefan Koell
Do you have any update info about shadow beta? Thanks
Hi @Stefan
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.
Thanks
Hi Kevin,
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.
Regards,
Stefan
Hi!
we are currently working on the V6 release and hope to get it out by the end of the week. Stay tuned.
Regards,
Stefan
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.
Hi Stefan,
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?
Regards,
Achim
HostedXL Support
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)
2 people like this idea