Gaute Greipsland's community posts

Michael Albright wrote:
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.

According to the answer I got - It is actually working as designed 1 out of 10 times, and some kind of bug allows you to connect 9 out of 10 times... ;)

My goal was to have a Wyse/Dell thin client connected to a Windows machine (XP/7/10/2008/2012/2016/2019) using RDP (Not "some kind of remote control software" - RDP!! TCP/UDP port 3389) , and when that user needs support I want to connect to the windows machine and connect to the same RDP session that the user is using, so we both see the same screen, move the mouse together and they can show what they did, and I can show what they should have done. This works with a lot of other Remote Control Software, but obviously not RU - according to themselves.

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.

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

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.

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.

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

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

I guess I have not explained the problem well enough. I have:
1 host running i.e. windows 10
1 thin client connecting to this machine via RDP with user A
So far, so good. Then the user calls me and asks for help.
With my computer, I connect to the host using RU - Full Control connection mode,  - I can see the logon screen on the console, but I do not try to log in. I click on the "Terminal Sessions" button on the toolbar and I can see there is a "#1 Console" (The one I am connected to), and a "#2 A (RDP-TCP#6)" (The session that the user is connected to from the thin client. I click on the "#2 A...." and then wait... and wait... After a few seconds RU disconnects and tries to reconnect, but I am not able to connect to the users session. Is this the expected behavior? All my other remote controlling software are able to do this, I can even connect to the user's session with Microsoft's mstsc (Remote Desktop Client). I am aware of the licensing from Microsoft in regards to the number of allowed active sessions and that I can not log in to the user's session from the Console session without disconnecting the user, so I am not doing that. I just want to "shadow" the RDP session.

I am already connecting to the host with Full Control and that works great. It's only when I try to switch into an already existing RDP session I have the problem.
I will send the mentioned files on mail.

Hi.
No, that is what we are doing, but it doesn't switch the session as intended. (On a few machines it does, but not on a lot of them). When we try to switch as you describe, the software freezes for 10-15 seconds and then it fades and says "reconnecting". After some more seconds it reconnects to the console and we are where we started.