Community

Polina wrote:
I'll get back to you with an update on this shortly.

Thank you. I'm looking forward to it :)

I hope it will be fixed, or explained to me what I am doing wrong soon since my Trial license is about to expire and I have to make the decision on what software we will purchase soon.

So you are actually saying that it is impossible to "Shadow" a Windows 10 machine with your software, although it works sometimes, and all the time with other software? Your software can not be used to support a user who is RDP'ing into a Windows 10 machine? I still believe it is a misunderstanding. I am NOT trying to log on as a second user - I am only interested in seeing and interacting with the screen of the already RDP-logged on user. The Microsoft Q&A page you linked to confirms that it is possible in Windows 10, and allowed from a licensing point of view as well, but you say that your software does not support this.

Ok, thanks for your efforts. I guess we have to go with one of the other softwares that allows this.

Gaute Greipsland wrote:

I am only interested in seeing and interacting with the screen of the already RDP-logged on user

hello,
i am also interested to shadow.

if you could take the .rdp file from RUViewer and add some values to the .rdp file, could you get it working that way?

asdffdsa wrote:
if you could take the .rdp file from RUViewer and add some values to the .rdp file, could you get it working that way?

No. They say their software is not able to do this, so you have to either use Microsoft RDP client and run some scripts to find the session-id you want to shadow, or use some of the other remote softwares that are able to do this out of the box.

if you know of any scripts that get the session id and what needs to be feed to the rdp client, i would like to see that.

for RU, i was having an issue with it overwriting values in the .rdp file, as documented so i wrote a script to work around that.

this is a snippet of a support ticked i opened with RU.

in the end, i had to write an autohotkey script.
1. run 'rutview.exe /rdp' - which will update the .rdp with the correct port number for 'full address:s:localhost:'
2. wait for the 'windows security' pop-up to appear asking for the rdp username/password.
3. kill that pop-up window.
4. copy the rdp from rdp_connections to temp.rdp
5. edit temp.rdp file to tweak the settings i need.
6. run temp.rdp using mstsc.exe but NOT rutview.exe
7. be happy

thanks,

I have around 80 Win 10 machines we use RU with.

I am able to,  90% of the time, connect to the machine and switch to the remote session.  this has almost been a requirement during the past year of everyone working from home during the pandemic.

The response from the Dev's seems like an easy (lazy) answer, but I couldn't say what the "Full Control" connection is actually using, assuming it's NOT just RDP..

I found this post as I now have 3 Pro licenses and was researching why 1 out of 10 times it won't let me connect to the session when I connect in "Full Control" mode.

I am discouraged that when Polina went to the Dev team, with what seems like a legit request, only to get  questionable responses to "pass along" to the end users