In the initial authentication phase, the connection is from the Horizon Client to the Connection Server. Normally, this is for connections that are internal to the corporate network. To explore the components and architecture of Horizon, see the Horizon Architecture section of the VMware Workspace ONE and VMware Horizon Reference Architecture.Īn internal connection is one where the Horizon client connects directly to the Connection Server and then directly to the Horizon agent. Following successful authentication, a connection using one or more secondary protocols is then made to the resource.įigure 1: Primary and Secondary Protocols The first phase of a connection is always the primary XML-API protocol over HTTPS, which provides authentication, authorization, and session management. It also can perform the authentication itself, leveraging an additional layer of authentication when enabled.įirst, it is important to understand that when a Horizon Client connects to a Horizon environment, several different protocols are used, and a successful connection consists of two phases. Unified Access Gateway directs authenticated requests to the appropriate resource and discards any unauthenticated requests. When providing access to internal resources, Unified Access Gateway can be deployed within the corporate DMZ or internal network, and acts as a proxy host for connections to your company’s resources. VMware Unified Access Gateway is a virtual appliance that enables secure remote access from an external network to a variety of internal resources, including Horizon-managed resources. The Connection Server authenticates users through Active Directory and directs the request to the appropriate and entitled resource. The Horizon Connection Server securely brokers and connects users to the Horizon Agent that has been installed in the desktops and RDS Hosts. Machines can be virtual desktops, Remote Desktop Session Hosts (RDS Host), physical desktops PCs, or blade PCs. This agent allows the machine to be managed by Connection Servers and allows a Horizon Client to form a protocol session to the machine. The Horizon Agent is installed on the guest OS of target VM or system.
VMWARE HORIZON CLIENT ERROR 1904 SOFTWARE
You can optionally use a web browser as an HTML client for devices on which installing client software is not possible.
The Horizon Client is installed on a client device to access a Horizon-managed system that has the Horizon Agent installed. The core components of Horizon that are used in a Horizon connection are described in the following table. Knowledge of other technologies, such as Horizon is also helpful. Familiarity with networking and storage in a virtual environment, Active Directory, identity management, and directory services is assumed. This guide is intended for IT administrators and product evaluators who are familiar with VMware vSphere and VMware vCenter Server®. This guide focuses on the connections between VMware Horizon Client and a resource, and how this understanding can be applied to troubleshooting connection issues in both VMware Horizon and Horizon Cloud Services.
This guide is focused on Blast Extreme connections but most of the content, especially around understanding connections, also applies to PCoIP connections. This can help determine the best architecture, understand the traffic flow, and network ports, and help in troubleshooting.Īlthough VMware Horizon is used here, including its Horizon Connection Server, most of what is described here is applicable to VMware Horizon Cloud as well. Before starting to plan or trying to troubleshoot Horizon and Blast connections, it is important to understand how a VMware Horizon Client connects to a resource.
0 kommentar(er)
