Forum Discussion

Greg_Crosby_319's avatar
Greg_Crosby_319
Historic F5 Account

Port 8443 is not always used with HTML 5 clients. The iApp offers several ways to configure your BIG-IP based on your available BIG-IP modules and your specific View configuration. The only configuration produced by the iApp that supports HTML 5 (without modification), is the scenario were you use APM to "Securely proxy PCoIP traffic using APM as a PCoIP gateway". It is the default iApp option when using APM with software versions 11.4-11.5.1 (11.4 is required to support PCoIP proxyied connections). The question directly after in the iApp is whether or not you want to support HTML 5 client connections, select yes for this option.

 

Using these options in the iApp, once you connect to the big-ip using a supported browser, you will see the option to use html 5 clients when selecting virtual desktop pool (don't forget you have to have the "HTML Access" option enabled on the pools settings).

 

For those wanting to configure LTM only, or do not currently have the APM module, you have a couple modifications to make after running the iApp. Here is a brief description of the required changes after running the iApp:

 

If you are using security servers, create a virtual server using port 8443 and attach the security server pool created by the iApp to the virtual server. You will also need to modify the persistence profile created by the iApp to "match across services". For this setup the connection server will need to have "Blast Secure Gateway" enabled and set to the correct fqdn:port. Once the clients have successfully logged into the security server, they will attempt to make a 8443 connection to the same security server which proxys 443 connections to the correct virtual desktop.

 

If you are not using security servers, create a forwarding (ip) virtual server using the network your virtual desktops reside for the destination network, and port 443. Once clients have successfully logged into the View connection server, they will attempt to make a 443 connection directly to the assigned desktop. For this setup, you will need to have "Blast Secure Gateway" disabled on each connection server.

 

aschaef, let me know what configuration you are trying to use and I can assist further.

 

AP's avatar
AP
Icon for Nimbostratus rankNimbostratus
May 06, 2016
Edit: Nevermind. Choosing no in the iApp simply Deny's browser access full stop. So you never get to the remote desktop icon on the desktop to select view client or HTML access. It seems there are several threads on Devcentral looking to have users automatically go to HTML access or the view-client but it doesn't seem to be possible at present. Hi Greg, Could I trouble you to elaborate on exactly what configuration changes occur when the HTML Access option is chosen or not chosen in the iApp? I've looked through the iApp code and it's not immediately obvious to me. I've built a configuration from scratch and the HTML access option is available by default it seems. You mentioned that choosing "Yes" in the iApp is what allows this option to be presented to the user, so my question is: How do you turn it off when not using the iApp? Regards, Andrew