Hello,
I've been having an issue connecting to new RDS deployments, either Server 2012R2 or 2016, using the modern client (UWA?).
If I connect to the rdweb site via browser, any browser (Chrome, IE, Edge), I can connect fine w/ the downloaded RDP file, either via the old mstsc client, or the modern client. If I open the modern client and add my deployment as an RDS resource, it adds file, but when I try to connect, it doesn't do anything. Monitoring network traffic, it doesn't even try to connect to the rpcproxy.dll,or even send any packets on the wire to my gateway.
Doing some digging, I see the rdp file is saved in my user profile (C:\Users\#####\AppData\Local\Packages\Microsoft.RemoteDesktop_8wekyb3d8bbwe\LocalState\RADC\{9AFF1AD1-C68D-FC28-FA01-4BD806FA43E4}-Committed\Resource) without an extension. If I copy the file from there, give it a .rdp extension, I can also connect with that file via either client.
I also don't appear to be able to add the remote resources, at all, via the IOS RD Client. I haven't tried Mac or Android yet, waiting to stabilize this config, but perhaps that's a separate issue. I don't see it trying to logon or connect to webfeed.aspx on the RDSWeb page at all.
These would all be the lastest iterations of the clients, I just started this whole setup about a week ago. I've tried a standard deployment in 2016, then a quick deployment in 2016, and finally a quick deployment in 2012 R2. I'm familiar with all the cert requirements, etc, I don't think it is any sort of cert issue. I will say the 2012 R2 quick deployment seemed to work OK initially, until I added 2016 session hosts to the deployment, but now I can't say for sure. If needed, I could do another quick deployment to verify.
Any insights would be great. If we can only use rdweb and have users open RDP files I guess we're OK with that, but not ideal.
Thanks!
-jg