lirick's Posts

Reformat the reply: >> Sometimes it completely fails to connect or allows connection and then later on disconnects the user It's more likely a poor network conditions cause user disconnected, you can check a few things as below: 1) Compare the network settings between "completely fails" and "allow connections and then later disconnect...": network cable connect or wireless connect, proxy enabled or disabled, etc. 2) Check if the same things happens to different clients, like Horizon Windows client and HTML Access client. 3) Check with your IT department to see if the connection is blocked by your company security settings.

> Sometimes it completely fails to connect or allows connection and then later on disconnects the user It's more likely a poor network conditions cause user disconnected, you can check a few things as below: 1) Compare the network settings between "completely fails" and "allow connections and then later disconnect...": network cable connect or wireless connect, proxy enabled or disabled, etc. 2) Check if the same things happens to different clients, like Horizon Windows client and HTML Access client. 3) Check with your IT department to see if the connection is blocked by your company security settings.

Hi carymiller, There are too many factors might cause disconnection, below questions should be benefit to narrow down the issue besides the possibilities provided by Yury: 1. When saying External Customer gets disconnect, which client are external customers using? and what's version of Horizon? 2. How is this issue for different clients, does it happen to other clients(like HTML Access, Mac clients, etc.)? And on the same client host where disconnect happens, does HTML Access show same behavior? 3. Regarding to "disconnect", is it Horizon remote desktop/application "disconnect" or Horizon Server session disconnect? If only desktop/app disconnect, credential will not be asked again when connecting to Horizon Server from Horizon Client. or that should be Horizon Server session disconnect. 4. Considering different Horizon Server and settings are being used for the connection from Domain Joined and Non-Domain Joined client hosts, network policy might be used, if Horizon connection from external domain joined client host, then disconnect after a specific time, if Horizon connection is from non-domain joined client host, session will not be disconnected, in this case, LB policy might be used. 5. Is Workspace ONE Access being used by the customer? in this case, different network range for connection might be used for domain joined and non-domain joined computers, which might have different Horizon connection path.

A pre-launched session will not be opened automatically, by default, an empty session will be established on server side when user login to client, then when the user want to use an app session, he/she will opened it more quickly than before, please be noted that not all types of  clients support this feature, I know it was implemented on Mac and WinCDK clients. To open an app application, you can configure reconnect behavior on Application Settings dialog, there is an option named "Reconnect automatically to open applications".

Multi monitor is only supported on Chrome browser for HTML Access, please check your pool setting and make sure "Max number of monitors" is set 2 or above,  and make sure your VMs are powered off then power on after the setting is changed.

There are two known issue for HTML Access running on Edge browser through UAG, see VMware Horizon HTML Access 4.9 Release Notes Copied as below: If you use a self-signed certificate with Unified Access Gateway, you might not be able to access a Horizon desktop when you use a Microsoft Edge Web browser for your HTML Access session. Workaround: Use one of the following workarounds to resolve this issue. Use a valid CA-signed certificate. Do not use port 8443 for the Blast External URL property. Use port 443 instead. or this one: If you configured Unified Access Gateway with a root certificate that is signed by a Certificate Authority (CA) and the Blast External URL property value is set to blank or to port 8443, you might not be able to connect to  a Horizon desktop if you are using a Microsoft Edge browser. Once the error happens, all new connected sessions are not visible. Workaround: Use one of the following workarounds to resolve the issue. Set the Blast External URL property to port 443. Close the Micrrosoft Edge browser, then relaunch the HTML Access Web Client and connect to a desktop.

You can get this done via a URI link, check more details on page 22 in Using HTML Access guide: https://docs.vmware.com/en/VMware-Horizon-HTML-Access/4.5/horizon-html-access-45-d​ ocument.pdf Here is an example: https://horizon.mycompany.com/?applicationId=Calcolatrice&action=start-session