Quantcast
Viewing all articles
Browse latest Browse all 27765

Certificate Issues with RemoteApp on two nodes (No Gateway). Simple Question.

Hello TechNet folks!

Hope you are having a nice day.

I am implementing a solution of two servers:

1x RD Host Session + RDWeb + RD Broker Service + Licence 

1x RD Host Session

My company has bought a Root certificate with no wildcards (for exact FQDN)

I added the FQDN name in IIS, RemoteApp and in the host file of my local computer pointing to the IP of the WFE server.

When I get into the RDWeb site, it works just fine, not showing any certificate issues, but when I click in an App and connects to Node 2, certificate comes back with the full domain name of node 2 (rather than the FQDN I also configured in RemoteApp in Node 2, so the client receives a warning of invalid certificate (not correct for the name of the source). This does not happen when I deactivate RD Session Broker and get directly into it (Node 1 or modifying Host file so it points to Node 2 and going to Node 2), it comes back the right certificate for the RD Session.

Is this because I need another certificate for the other node?

Can I make it work with the certificate my client has purchased, has to be a SAN certificate?

p.s. We are to implement F5 Load Balancing as well, does it also have to have another certificate?

I hope you can help me with this, I rarely get frustrated but now I have to explain to the client what is to do in order to sort this issue.

Thanks in advance!



Viewing all articles
Browse latest Browse all 27765

Trending Articles