![]() So always use sha1= even if you have a different Secure Hash Algorithm. We entered sha1= and our SHA-256 thumbprint and then everything worked. Rebooting the UAG, redeployment, nothing solved our problem. We checked the certificate and it was valid and the Connection Server URL could be resolved. This can also happen if the certificate is not valid or the UAG can’t resolve the Horizon Connection Server URL. We had SHA-256 certificates and entered sha256=AE:B6… but the Connection Server URL still indicated it was not reachable. When you hover over the I icon it states that you can use sha1= for SHA-1 certificates and sha256= for SHA-256 certificates. After the deployment, we had to add the Certificate thumbprints of the Connection Servers because they were issued by an internal CA. You can find more information on how to deploy the UAG with Powershell on this link. We deployed the UAG with Powershell which is the recommended way. UAG HA mode can only load balance site-local traffic. Keep in mind for multi-site load balancing, you still need a Global Traffic Manager. In a later phase, the updated F5’s can load balance the UAG traffic. After carefully considering the risks we decided to deploy one UAG with 2 NICs. The customer didn’t have 3 public IP Addresses for the POC and upgrading the F5 environment was not an option. One of the prerequisites to setup UAG HA is 3 Public IP Addresses, because of the different traffic flows for XML API and BLAST. ![]() We investigated the High Availability option of UAG because their F5 environment was not supported. ![]() For External Access, we wanted to deploy Unified Access Gateway. Some of the requirements were HA were possible and External Access. I recently did a proof of concept of Horizon Enterprise with App Volumes and User Environment Manager. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |