Subject:Embedded RDP connections fail

Subject:Embedded RDP connections fail

avatar

RDP session fails if it is set up as embedded. It connects perfectly using the same settings but Display changed to External.
It is the same error than reported on this post. I tried remove/reinstall (even in different folder), remove "appdata" folder, etc. The error persists after upgrade to version 8.4.4.0

Thanks

All Comments (8)

avatar

Hi,
Could you take a look at the topic about NLA here?

http://help.remotedesktopmanager.com/troubleshooting_automaticlogon.htm

David Hervieux

avatar

Thank you David, I tried with SingleSignOn on and off but it fails anyway.

avatar

Could you post the error message you get?

David Hervieux

avatar

David,
I am receiving the same type error. If it is the same thing then it never gets to the point of asking for the credentials which would have been fixed by the SSO check box. What is happening in my particular case and possibly Victor's as well is that a session setup to use Tabbed mode fails with a message of "The remote computer disconnected the session due to an error in the licensing protocol. Please contact you system administrator." And while typing this I fixed my own issue though you may have a more elegant solution. If you set the permissions of the shortcut to "Run as Administrator" you will be prompted for permission to run as Administrator (depending on your UAC settings) but after that the sessions will open in tabbed mode. Not sure if this is a one time setting I will test further and reply back again :) One sysadmin/support guy to another :)

avatar

Ok just tested and you do have to leave the Run as Administrator option checked, I was thinking that after the initial run that the registry access that was needed would no longer be needed (I just recently had to update my CAL and I know that after updating a RDP CAL there are registry strings that get updated and that requires Admin level privileges) but unchecking the Run as Administrator option brough the error back. Also as a note the Run as Administrator option needs to be set for ALL shortcuts that you may want to run RDM from (Start Menu, Desktop, Startup Folder, etc.) it will not propagate on its own.

avatar

Hello David, Attached is the error I get.
I also tried to run shortcut as Admin (thaks for the help) but in my case it was not enough. I still get the same error.
One note from my side may help on resolution: The only way to run on tabbed mode is enabling "Open in console". Unfortunately, I haven’t admin rights on target machines.

Capture.GIF

avatar

David Hervieux

avatar

That was the key!! Thanks a lot David.
And congratulations for your really good, and above all, quick support