RDS Connection Broker or RDMS fails after you disable TLS 1.0 in Windows Server

This article provides methods to make sure Remote Desktop service (RDS) Connection Broker and Remote Desktop Management service (RDMS) can work as expected.

Original KB number:   4036954


Assume that you use the inbox Windows Internal Database (WID) in Windows Server. If you disable Transport Layer Security (TLS) 1.0 when you configure security settings, you experience the following issues:

  • The Remote Desktop service (RDS) may fail.

  • An existing RDS deployment that uses Remote Desktop Connection Broker and WID may fail.

  • The Remote Desktop Management service (RDMS) doesn't start.

  • You receive the following error message when you try to start the RDMS:

    The Remote Desktop Management service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

  • The Remote Desktop Connection Broker role can't be installed.


This behavior is expected because of the current dependencies between RDS and Windows Internal Database (WID). RDMS and Connection Broker depend on TLS 1.0 to authenticate with the database. WID doesn't currently support TLS 1.2. So, disabling TLS 1.0 breaks this communication.


RDS deployments that use Connection Broker have to establish an encrypted channel to WID by using one of the following methods:

  • TLS
  • SSL 3.0
  • FIPS


To fix this issue, use one of the following methods:

  • Set up RDS without Connection Broker for a single-server installation.
  • Don't disable TLS 1.0 on a single Connection Broker deployment.
  • Configure a high availability Connection Broker deployment that uses dedicated SQL Server.
  • Upgrade the computers that run the RDS services to Windows Server 2019.


Microsoft has released TLS 1.2 support for Microsoft SQL Server to enable SQL Server communication to use TLS 1.2.