Hi Stefan,

I absolutly love your product and already purchased it!

However there is one missing functionality regarding remote desktop gateway scenario which would help a lot in my situation.

I would like to connect to my servers by using a remote desktop gateway. The remote desktop gateway is in the same Active Directory domain as my client workstation. The remote servers are in another Active Directory domain. There are no trusts between the two Active Directory.

Currently we have only the following options in Royal TS to authenticate against the RD GW:

-- Ask for credentials

-- Specify credentials - Use credentials from Connection

-- Specify credentials - Use these credentials

I would need a 4th option - Use logged in credentials. Then the Royal TS would use my already logged in account to authenticate against the RD GW and then the login name password which I specified in the Royal TS configuration to log in to the remote computer.

Microsoft Remote Desktop Client has such capability (only when it is configured by group policy).

I am ready to provide additional details about the scenario and hope it could be integrated in the next release.

Thanks!

Nandor Toth

Hi Stefan,

I set the following in group policy (it may be specified in local group policy as well):
User Configuration - Administrative Templates - Windows components - Remote Desktop Services - RD Gateway
Set RD Gateway authentication method - Enabled / Use locally logged-on credentials
Set RD Gateway server address - Enabled / set the address

After that when you start MSTSC and navigate to Advanced / Settings and select Automatically detect RD Gateway server settings you may notice that the Logon Settings part of the window is changed and will show User name: user@domain "Your Windows logon credentials will be used to connect to this RD Gateway server."

I did a couple of test with the MSTC client and unfortunately it does not support my scenario (automatic login to RD GW and ask for password on the remote server).

Yes, I will gladly do scenario tests.

Thanks,

Nandor

PS. I was able to work around this problem in my environment by adding a local user to the RD GW servers. I configured both the RD GW and the remote computer credentials in Royal TS and it works very well. (although not very elegant)

PS2. I think my scenario is not very common as the RD GW and the remote servers are usually in the same AD forest.