Hi,
I have a question regarding RemoteApp vs regular Remote Desktop Connection spiced with a VPN connection initiated from the host.
We're in the process of moving from PCs to thin clients and we have set up an RDS farm (all servers are Windows Server 2012 R2, they are all in the same domain and same LAN) as follows:
1 x RD Connection Broker + RD Licensing + RD Web Access
3 x RD Session Host
The users/clients will connect with regular remote desktop connection software (no Citrix or anything). Two of the RD SHs will be providing the users access to their normal applications, but some users also need to use remote resources which are only available via VPN connection, hence the third RD SH. (Currently it is solved by every user having a virtual machine on their PCs and connecting to the VPN from there.) We can't put the VPN connection to the two "regular" RD SHs, because we'll need more VPN connections later. The idea was to install and set up the VPN on the third host and publish the needed apps by RemoteApp to the users who use it.
The problem:
Once the host connects to the VPN the users are unable to launch the RemoteApp applications. If it's not connected then they can start them. The VPN client is a Cisco AnyConnect Secure Mobility Client that can only connect if the connection is initiated by a local user and no other user is currenty logged on (it's a remote side policy we can't change). If the users connect to the RD host with a regular remote desktop connection after the VPN is set up then it works as expected, they can launch the apps and work with them.
The question:
What is the difference between launching a RemoteApp and connecting to the RD host via RDP? How can I debug this RemoteApp connection problem?
Please ask if something is not clear!
Thank you!
PS: If I'm not heading into the right direction and someone has a better idea, I'd be grateful to hear (read) it!
