I have a 2012 R2 RDS install that includes 3 session hosts and one server that functions as Gateway, Connection Broker, and Web Access server. I the proper CAP and RAP policies set up to allow connections. The Gateway and other service machine was upgraded from 2012 to 2012 R2 so I know the basic configuration was sound. The way I went about this was to clone the 2012 machine into our development environment to run the upgrade and then rename, join the domain with different name, remove the old from the domain and rename the new server to the old one's name.
I ran into an issue where the session collection was not populated on the newly upgraded server so I ended up having to delete the deployment and then delete the registry entries for the published apps for the site. After I did that the installation
started working fine from the inside as long as I made sure the Bypass Gateway on local addresses option was checked in the deployment. (I prefer to leave that on so I can see the number of connections in the Gateway Manager but that's a nice to have not a
need to have.)
Where it stands now, if I go to the "Connect to a remote PC" tab and trying to hit a server it does NOT work, but if I run the Mstsc.exe app and specify the gateway server address it DOES work. Something in the way the RDP connection
from that specific function on the server is getting transferred to the client is wrong but I'm not sure how to fix it.
Any ideas on where to check? I'm guessing there's a registry entry somewhere that's wrong but I'm not sure. Anyone run across this or have any ideas?
Thanks,
Jack
Jack