Last night we upgraded our public-facing Server 2012R2-based RDS Gateway (GW) and Connection Broker (CB) servers to the brand-new Aug 2019 Rollup. Normally we wait at least a week before applying new patches but last night was already a scheduled maintenance window so we took a chance. And got burned.
After the patching, no one could login. We use an RDP connection file which specifies the use of the GW and has the CB listed as the target system. You would be prompted to authenticate, i.e., I assume your login request was passing through the GW to the CB, but then there was a completely generic error, “Unable to connect.” Since we were under time-pressure I simply rolled-back the updates, and this restored access.
I am still trying to analyze the logs; I’ll have more info later.
Has anyone else applied these patches to their 2012 GW/CB successfully?