Hi Mark. I'm doing the exact same setup for a customer. They have chosen to keep HTTPS between the intermediate server (F5 LTM) and View security servers (external access), View connection servers (internal access). So, in this case the LTM is re-encrypting the SSL and sending the packets along over HTTPS. I take it therefore there's no need for the locked.properties file on each security/connection server?
We also ran into the same issue with the thumbprint as addressed in that kb above and resolved the issue by following the steps.
For some reason we're running into the black screen only on internal access to the View desktops (i.e. LTM balances internal connections to a pair of internal-only Connection servers). Could you let me know what should be checked and the values on each internal View connection server (i.e. http(s) secure tunnel (checked/unchecked, external URL - FQDN VIP (i.e. https://vdi.company.com:443) or FQDN of Connection server (i.e. https://viewcs01.company.com:443).
I assume that since these are internal View connections that I should uncheck the PCoIP Secure gateway? What about the Blast Secure gateway for internal connections?
Thanks
Ian