HTML Access has been renamed to Horizon Web Client. In addition, the Horizon Web Client user interface, configuration strings, and file paths have been updated to reflect the new Omnissa brand.
You can find content for previous versions of HTML Access documentation here.
This guide describes how to install, configure, and use the Horizon® Web Client™ software to connect to remote desktops and published applications. This guide is written for administrators and end users of Horizon Web Client.
You can also access this guide by clicking the Help button ( 
) in the Horizon Web Client desktop and application selector window.
About Horizon Web Client
Horizon Web Client communicates with a server, which acts as a broker between the client device and remote desktops and published applications. You enter credentials into Horizon Web Client, the server authenticates your credentials, and then the server finds the remote desktops and published applications that you are entitled to use.
Horizon Web Client is a good alternative when Omnissa Horizon Client software is not installed on the client system.
Note: Horizon Client offers more features and better performance than Horizon Web Client. For example, with Horizon Web Client, some key combinations do not work in the remote desktop, but these key combinations do work with Horizon Client. For more information, see System Requirements for Horizon Web Client.
How to Use This Guide
To get the help that you need from this guide, refer to the chapters that apply to your role and use case.
For end users and administrators - If you are an end user who needs to use Horizon Web Client to connect to remote desktops and applications and work in remote sessions, see the following chapters. These chapters also contain information relevant to administrators.
- Connecting to Remote Desktops and Published Applications
- Using a Remote Desktop or Published Application - HTML
- Using External Devices
- How to Troubleshoot Problems with the Horizon Client
For administrators - If you are an administrator who needs to install Horizon Web Client software on an Omnissa Horizon Connection Server instance and on a virtual desktop or Microsoft Remote Desktop Services (RDS) host, see the following chapters. These chapters are written for experienced system administrators who are familiar with virtual machine technology and data center operations.
How Do I Log In?
Before you can log in and connect to a remote desktop or published application, a system administrator at your company must set up your user account. If Horizon Web Client prompts you for a server name and domain, your system administrator must tell you the server name to type and the domain to select.
Note: If you do not know your username or password, or how to reset your password, contact the system administrator at your company.
When you are ready to log in and get started, see Connecting to Remote Desktops and Published Applications section.
System Requirements for Horizon Web Client
With Horizon Web Client, the client system requires a supported browser. No more software is needed. However, your deployment must meet certain software requirements.
Browsers on the client system
| Browser | Version for 2603 | |
|---|---|---|
| Chrome | 142, 143, 144, 145 | |
| Safari | 17.6, 18.6, 26 | |
| Firefox | 145, 146, 147, 148 | |
| Microsoft Edge | Supported only on Windows clients. | |
| Omnissa Workspace ONE Web | The latest version in the Apple App Store (iOS devices) or Google Play Store (Android devices). | |
Note:
- On an Android device, Chrome does not support the Windows key, multiple monitors, copy and paste to the system, file transfer, printing, H.264 decoding, credential cleanup, and an external mouse. The Del, Ctrl+A, Ctrl+C, Ctrl+V, Ctrl+X, Ctrl+Y, Ctrl+Z key combinations do not work on the software keyboard.
- On an iOS device, Safari does not support an external mouse, the Windows key, multiple monitors, copy and paste to the system, file transfer, printing, H.264 decoding, credential cleanup, and Real-Time Audio-Video.
- For geolocation redirection, the feature requires location services to be activated on the local operating system and on Horizon Agent. If you deny permission to use location services locally and the services are turned on for the agent, the feature uses the location of the agent. For example, suppose that the remote desktop requests weather information and the server is located in Palo Alto, CA and the client device is in Bellevue, WA. Then the location for the server is used and the remote desktop displays weather for Palo Alto, CA.
Client operating systems
| Operating System | Version |
|---|---|
| Windows | 11, 23 H2 10 (32-bit and 64-bit) |
| macOS | 14 (Sonoma) 13 (Ventura) 12 (Monterey) 11 (Big Sur) 10.15.x (Catalina) 10.14.x (Mojave) 10.13.x (High Sierra) |
| iOS | 10 or later |
| Android | 7 or later |
| Chrome | ChromeOS 75 or later, on Chromebooks ChromeOS Flex 103 or later |
Omnissa Horizon 8 Deployments
Horizon Web Client requires the latest maintenance release of one of the following deployment types:
- Horizon 8 version 2006 or later
- Omnissa Horizon Cloud Service - next-gen
- Horizon Cloud in Microsoft Azure
Remote desktops
Horizon Web Client supports all the desktop operating systems that Horizon Agent supports.
Pool settings
Horizon Web Client requires certain pool settings.
- The Max resolution of any one monitor setting must be 1920x1200 or higher so that the remote desktop has at least 17.63 MB of video RAM.
- If you use 3D applications, or if end users use a MacBook with Retina Display or a Google Chromebook Pixel, see Setting the Screen Resolution section.
Horizon Connection Server
For Horizon 8 deployments, install the Horizon Web Client component in Horizon Connection Server. For more information, see Preparing Horizon Connection Server section.
Third-party firewalls
Add rules to allow the following traffic:
- For servers, allow inbound traffic to TCP port 8443.
- For virtual desktop machines, allow inbound traffic (from servers) to TCP port 22443.
When you install the Horizon Web Client component in Horizon Connection Server, the Horizon View Horizon Connection Server (Blast-In) rule is turned on in the Windows Firewall. This rule configures the firewall to allow inbound traffic to TCP port 8443 automatically.
Display protocols
Horizon Web Client supports Omnissa Horizon Blast.
When you use a web browser to access a remote desktop, the client uses the Horizon Blast display protocol, not PCoIP or Microsoft RDP. Horizon Blast uses HTTPS (HTTP over SSL/TLS).
System Requirements for the Session Collaboration Feature
With the Session Collaboration feature, users can invite other users to join an existing remote desktop session. To support the Session Collaboration feature, your deployment must meet certain requirements.
Session collaborators
To join a collaborative session, a user must have Horizon Client for Windows, Mac, or Linux installed on the client system, or must use Horizon Web Client.
Windows remote desktops
The Session Collaboration feature must be enabled at the desktop pool or farm level. For information about enabling the Session Collaboration feature for desktop pools or farms, see the Desktops and Applications in Horizon 8 document.
You can use Horizon Agent group policy settings to configure the Session Collaboration feature. For information, see the Horizon Remote Desktop Features and GPOs document.
Linux remote desktops
For Linux remote desktop requirements, see the Desktops and Applications in Horizon 8 document.
Horizon Connection Server
For Horizon 8 deployments, the Session Collaboration feature requires that the Horizon Connection Server instance uses an Enterprise license.
Display protocols
Horizon Blast
The Session Collaboration feature does not support published application sessions.
System Requirements for Geolocation Redirection
Horizon Agent, and the virtual desktop or RDS host and client machine on which you install the agent and client software, must meet certain requirements to support the Geolocation Redirection feature.
The source of the geolocation information is the operating system of the local device using Horizon Web Client. This information can be redirected by the client to remote desktops or published applications. The configuration settings of the host system and the agent can restrict the feature's availability.
With Geolocation Redirection, geolocation information is sent from the client system to the remote desktop or published application.
Virtual desktop or RDS host
-
The Windows Location service setting must be On in Settings > Privacy > Location.
-
The Geolocation Redirection feature supports the following remote desktop applications.
Application Platform Google Chrome (latest version) All virtual desktops or RDS hosts Internet Explorer 11 All virtual desktops or RDS hosts Microsoft Edge (Chromium) All virtual desktops or RDS hosts Microsoft Edge, Maps, Weather, and other Win32 and UWP apps Windows 10 -
The Location permission setting, if any, must be enabled individually in each supported browser.
-
Horizon Agent must be installed with the Geolocation Redirection custom setup option selected. This option is not selected by default. See the topics about installing Horizon Agent in the Desktops and Applications in Horizon 8 document.
Client system
- To share the client system's location information, you must configure the Geolocation settings in Horizon Web Client.
- For Windows 10 client systems, the Windows Location service setting must be On in Settings > Privacy > Location to make your location information accessible.
Display protocol for the remote session
Horizon Blast
Was this page helpful?