Okay, we currently have an RDS 2016 Configuration, with the following:
- 1 x RDS 2016 License Manager server
- 2 x RDS 2016 Gateway/Web Access servers
- 2 x RDS 2016 Connection Broker servers
- 4 x RDS 2016 Session Host servers (2 x Session Hosts on load-balanced servers)
The RDS 2016 Connection Broker server is configured in High Availability Mode, and stores it's database on a SQL 2016 Cluster. The initial setup doesn't allow you to specify SQL 2016 *until* you later configure CB to be in High Availability Mode, so it's my understanding that it initially uses a WID (Windows Internal Database) and continues to do so even after configuring High Availability Mode?
Is there any way of "removing" the dependency between the CB and WID, as this TechNet Article seems to suggest that TLS 1.2 can't be configured if WID is involved in the installation?
The reason for asking this, is that we configured the SCHANNEL registry settings to disable everything apart from TLS 1.2, and this broke the connection between RDS and the Connection Broker. The only way to "recover" this was to re-enable TLS 1.0 (TLS 1.1 didn't work).
Any ideas appreciated.
Many thanks.