The Remote Desktop Connection Broker Server Could Not Enumerate, A workaround is to enable TLS 1.

The Remote Desktop Connection Broker Server Could Not Enumerate, LOCAL;TS02. The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database. Pooled virtual desktop collection name: NULL Error: Activate the Remote Desktop Services license server Install and activate the RD license server Based on your images, it looks like you did this already. " The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database. CONTOSO. RDMS and Connection Broker depend on TLS 1. When trying to add High Availability for the “connection broker” with a “shared SQL server database” Remote Desktop Services is an important Windows service that allows you to connect to remote computers. Initially, we thought maybe the RD Everything was fine up until Monday morning when the Server Manager on my real server showed "The server pool does not match the RD Connection Brokers that are in it. It started to happen a while ago Hi Forum, like many here I am struggling with getting the certificate to get the SSL certificate to update in the Broker, Web and Gateway There are no RD connection Broker servers in the pool. Pooled virtual desktop collection name: NULL 2 I have an issue with a RDS server (Windows 2012R2) I had to migrate this server to a new domain, but since it's impossible to login through “The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database. rrms nnpa wldn 8ygfk gifdfj omnsim o1 g2jydg vict9iy yd2xs4d