Hi,
My environment contains two Hyper-V Servers for DCs, Connection Broker, RD-Web, and two Hyper-V servers as virtualization host to thin clients. All Hyper-V servers are only 35% utilized and all client VMs don't have a performance issue.
After setting up the roles and creating the "Personalized Pools", I open the RD-Web, click on the collection and here it takes a very long time in securing connection part, then a warning message appears for the connection broker self-signed certificate, I accept it and again a very long time to open the VM.
After searching the internet I figured out that I should install "PFX" certificates for the connection broker (SSO, Publisher). In my environment, we don't use a public certificate from trusted root CAs, however, we have our own "Enterprise Root CA".
I then figured that I should create a certificate with the following attributes:
Advanced Key Usage: Server Authentication, Client Authentication
Key Usage: Data encipherment, Digital Signature, Key Agreement
I created the certificate and imported it to the RD CB, however, the "securing connection" part was even slower than before, so I duplicated the "Computer" certificate, and configured 1024 bit certificate instead of the old one "2048". The "securing connection" part is taking half the time now, however it is still very long "+60 seconds" to open the VM.
I still suspect that it is a certificate issue and not sure if I have done the correct certificate.
Would anyone help in this case and providing the correct steps to install a certificate for the RD CB from internal CA.
Thanks.