Embedded RDP session opens in full screen window not tab

Hello,

Just to be sure, what version of RDM are you using?

Best regards,

13.0.6.0

Hi,
If you set the content of the RDP, it's always in external mode. Instead you could do an import.

Regards

Thanks David,

I tried this but I think BT is too fussy. All I get when I use an imported configuration (rather than en embedded one) is this error.


We've never been able to get BT working without having an embedded RDP session

We must be missing one setting. Could you try to export the RDM session into an .rdp and compare it with the one you originally had?

Regards

Ok, I've grabbed both the embedded BT template data and exported the imported file, sorted the contents for ease of comparison and run it through Beyond Compare:



It *could* possibly be the prompt for credentials on client:i:1 but I don't see this as a tick box option in a normal (imported) RDP session properties. There is a "always ask for credentials" tick box, but when exported, this becomes prompt for credentials:i:1

Could you try to manually edit the exported .rdp file to see if it works?

Regards

Looks like I was right about that parameter. If I execute that RDP file as is via mstsc.exe it connects in a 1080x1920 window and and BT happily connects.

Unfortunately, when I try to import the RDP file into RDM (via Edit > New Entry > Import From > RDP Configuration) and select Import RDP Content, It just imports an empty session (computer, username, domain, etc is all blank)

Below is the content of the RDP file. Are you able to put this in a .RDP file and see if you get the same issue if you try & import it ?


screen mode id:i:1
desktopwidth:i:1024
desktopheight:i:768
winposstr:s:0,1,0,0,1920,1080
session bpp:i:24
full address:s:xxxx.yyyy.zzz:9999
compression:i:1
keyboardhook:i:2
audiomode:i:0
drivestoredirect:s:*
redirectprinters:i:0
redirectcomports:i:0
redirectsmartcards:i:0
redirectclipboard:i:1
redirectposdevices:i:0
displayconnectionbar:i:1
connection type:i:1
autoreconnection enabled:i:1
networkautodetect:i:0
authentication level:i:2
prompt for credentials:i:1
negotiate security layer:i:1
username:s:my_domain\my_LANID+my_domain\my_BTID+my_server
domain:s:
remoteapplicationmode:i:0
alternate shell:s:
shell working directory:s:
disable cursor setting:i:0
connect to console:i:0
administrative session:i:0
disable wallpaper:i:1
disable full window drag:i:1
allow desktop composition:i:0
allow font smoothing:i:0
disable menu anims:i:1
disable themes:i:1
bitmapcachepersistenable:i:0
BBarPinned:i:1
gatewaycredentialssource:i:4
gatewayhostname:s:
gatewayprofileusagemethod:i:0
gatewayusagemethod:i:2
promptcredentialonce:i:0
smart sizing:i:1
use multimon:i:0
videoplaybackmode:i:1
audiocapturemode:i:0
redirectdirectx:i:0
bandwidthautodetect:i:1
prompt for credentials on client:i:1

Interesting. I need to verify how I could pass this parameter to the RDP ActiveX. I will investigate.

Regards

I've found it. I will try to support this in RDM embedded.

Fantastic ! Thanks David !

This is now implemented internally and it will be in the next beta of RDM. I hope to release it tomorrow.

Regards

Hi,
The new beta is out:

https://remotedesktopmanager.com/home/thankyou/rdmsetupbeta

Downloading now ! I will test & advise

Ok, have managed to test with both positive results and negative results

If I create a new session using this method, it works perfectly:
1. Add a new session with New Entry > Add session > Microsoft Remote Desktop (RDP)
2. Change :
GENERAL
o Name = name of session
o Computer = my_BT_server
o Port = my_BT_port
o Username = my_domain\my_LANID+my_domain\my_BTID+my_server
ADVANCED
o Prompt for credentials on client = tick
However, if I export that new session as an RDP file and then import it again, BT gives a "Failed to authenticate..." error (like the screenshot above).
Weird....


But I'm happy as I can now create BT sessions that are tabbed and I have also successfully managed to save a working session as a template so I can create new sessions that way too.

I will verify the export. It's possible that I missed a case. I have to be honest, I squeeze this in the release at last minute.

Regards

I have verified and the "prompt for credentials on client" is exported. Could you try a compare of the export and verify if you see another difference. Perhaps the port is not exported. I will verify this.

Regards

Hmm, yeah you're correct, that param exported. What is also weird is that if I create a new session (using the above method) and verify it works, export it, import it again and it doesn't work (the credentials for BT box doesn't appear). BUT if I double click that same exported RDP file from explorer, it successfully opens in RDM (the BT credentials box comes up and I can log in successfully)

I exported an embedded BT connection to an RDP file as well as the newly created session (using the above method) and the only differences were:
* embedded session export didn't export "username" or "full address" param values (they were just username:s:)
* prompt for credentials on client:i:1 wasn't in the embedded session export but was in the manually created session

Where do you store the username? Is it in the RDM database?

Regards

No, my LAN ID and BT ID are passed in as part of the string that makes up the value in the username field


For an embedded session the string is part of the RDP text

So if I understand correctly when you export the connection the username is not exported into the .rdp file?

Regards

Correct, but only for the embedded rdp sessions. Normal ("configured") exports all data