I then had one final issue when selecting a Desktop in the Horizon Client, where the connection was attempted but then closed with the error "The connection to the remote computer ended". Menu->Configure SSL.->Do not verify server identity certificates. I'll need to get a trusted cert for my Connection Server and import it to the UAG as well, but the certificate issues can be ignored by accessing the settings menu in the Horizon Client while disconnected from a server.
I successfully connected to my UAG with the Horizon Client and it displayed all of my Connection Server Desktop Pools. It seems like the non-FIPS version has more capability and manual configuration options available. Interesting enough, the non-FIPS version of UAG has all the manual configuration options available whereas the FIPS version had most of them grayed out. At this time, I don't think I have a requirement to use the FIPS deployment so I should be fine. My Connection Server was most likely deployed in a non-FIPS configuration as well.
I had to redeploy my UAG Appliance using the non-FIPS version in order for the UAG to be registered as a Gateway Server in the Connection Server.
0 kommentar(er)
