Using Horizon 7 To Access Physical Windows Machines - Swan Sol
REVISED 25 MARCH 2020 USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Table of Contents Overview Versions Architecture and Design – Components – Sizing – Load Balancing – Scaling – Authentication – Display Protocols – Network Ports – Single DMZ – Double DMZ Implementation – Considerations – Requirements – Connection Servers – Unified Access Gateways – Horizon Agent Installation – Desktop Pool – Horizon Client HORIZON 2
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Changelog Author and Contributors – Author – Contributors – Reviewers HORIZON 3
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Using Horizon 7 to Access Physical Windows Machines Overview When faced with unpredictable events like natural disasters, emergencies, or public health outbreaks, organizations are being asked to take action and enable their workforce to access corporate resources remotely. In many cases, the user has a physical Windows machine located in their normal place of work, the office. That machine has all the applications, access to data, and tools that the user needs to do their work. The challenge is that the user is unable to physically get to their machine. What is needed is a solution to enable working from home that gives users secure remote access to their work machine, and the solution needs to be quick and easy to deploy. Figure 1: Securely Accessing Physical Office-Based PCs VMware is well known for virtualization technologies, but VMware Horizon 7 goes beyond brokering virtual machines. Although best known for its myriad benefits when implementing virtual desktops and application servers, Horizon also offers the option to broker access to physical machines. This provides an excellent and familiar experience for employees. Brokering to physical machines can be implemented either with an existing Horizon 7 environment or with a new one. With minimal components required, this solution can be implemented quickly. Connections are encrypted and Horizon 7 supports multiple authentication options including SAML, RADIUS, RSA SecurID, and certificates, including smart cards. Authentication can be carried out in the DMZ at the Unified Access Gateway, before passing authenticated traffic through to the internal resource. To provide support to users, Horizon 7 has the Horizon Help Desk Tool. This is a web application that you can use to get the status of Horizon 7 user sessions and to perform troubleshooting and maintenance operations. See Using Horizon Help Desk Tool in Horizon Console. This guide gives technical detail, with design and implementation considerations and guidance, on how to achieve this. HORIZON 4
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 2: Securely Accessing Physical Office-Based PCs with Horizon 7 Horizon 7 enables access to office-based physical machines by using just a few core Horizon components: 1. The VMware Horizon Client authenticates to a Horizon Connection Server. 2. The Connection Server brokers a connection to a Horizon Agent running on a Horizon-managed desktop or server. For this use case, the Horizon Agent is installed on physical Windows 10 machines. 3. The Horizon Client then forms a protocol session connection to a Horizon Agent in the physical machine. The Horizon Client is available for all major OS platforms including Windows, Mac, Linux, iOS, Android, Chrome OS and also as HTML Access. HTML Access allows users to use a web browser to act as the Horizon Client, where installation of the client software is not possible. See VMware Horizon Client Documentation. To provide secure access from external locations and over the Internet, VMware Unified Access Gateway is deployed to provide secure edge services. 1. The Horizon Client authenticates to a Connection Server through the Unified Access Gateway. 2. The Horizon Client then forms a protocol session connection, through the gateway service on the Unified Access Gateway, to the Horizon Agent running in the physical desktop. Figure 3: Secure External Access with Authentication Through Unified Access Gateway User authentication can be configured in various ways. By default, Active Directory credentials are used, but this can be enhanced with two-factor or alternative authentication initiated from Unified Access Gateway. See the section on authentication later in this HORIZON 5
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES guide. You can quickly set up and configure Horizon 7 for use as an interim solution to broker access to physical machines. This setup also creates an excellent foundation that can be built on, at a later date, to realize the full benefits of the complete Horizon 7 and VMware Workspace ONE platform. These include: Delivering pristine high-performance personalized desktops to end users every time they log in Scaling published applications effortlessly at the push of a button while deploying them faster and eliminating image sprawl Reducing endpoint security concerns by destroying desktops as soon as users log off Drastically lowering costs by pooling required infrastructure components and providing a truly stateless desktop that still delivers the personalization end users expect Versions With Horizon 7 version 7.7, VMware introduced the ability to broker physical machines running Windows 10 version 1803 Enterprise Edition or higher, via the Blast Extreme display protocol. Either the Blast Extreme or RDP protocol can be used, but Blast will give a better user experience. For more information on the key features see VMware Blast Extreme. For Windows 10 versions 1903 and later, use Horizon 7 version 7.12. Note: Windows 10 Pro Edition may work but is not officially supported. The RDP protocol should be used for Pro, so that the display is not mirrored on the physical monitor. If possible, change the license type used for Windows 10 to Enterprise edition. Earlier versions of Horizon 7, before version 7.7, can broker to physical machines using the RDP protocol. Physical machines running Windows 7 will work with some caveats. These can only use RDP as the display protocol. The Horizon Client will need to be installed on the employee’s home device because HTML Access is not available for RDP connections. Configure desktop pools that contain Windows 7 to use the RDP protocol. Table 1: Windows and Horizon 7 Versions Windows Version Horizon Version Protocol Windows 10 Enterprise Edition 1903-1909 7.12 Blast or RDP Windows 10 Enterprise 1803-1809 7.7 - 7.12 Blast or RDP Windows 10 Enterprise 17xx 7.x RDP only Windows 10 (non-Enterprise) 7.x RDP only Windows 7 SP1 or later 7.x RDP only See Display Protocols for more information on Blast Extreme and RDP. Architecture and Design Horizon 7 is a platform for managing and delivering virtualized, session-based, or physical desktops and applications to end users. Horizon 7 allows you to create and broker connections to Windows virtual desktops, Linux virtual desktops, Remote Desktop Server (RDS)–published applications and desktops, and physical machines. A successful deployment of Horizon 7 depends on good planning and a robust understanding of the platform. This section focuses on the main design topics required for a Horizon environment brokering connections to physical desktops. HORIZON 6
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Components The required core components of Horizon 7 are described in the following table. Table 2: Horizon 7 Components Component Description Connection Server The Horizon Connection Server securely brokers and connects users to desktops and published applications running on physical PCs, blade PCs, RDSH servers, or VMware vSphere VMs. The Connection Server authenticates users through Active Directory and directs the request to the appropriate and entitled resource. Horizon Agent The Horizon Agent is installed on the guest OS of target physical systems or VMs. This agent allows the machine to be managed by Connection Servers and allows a Horizon Client to form a protocol session to the machine. Horizon Client The Horizon Client is installed on a client device to access a Horizon-managed system that has the Horizon Agent installed. You can optionally use a web browser as an HTML client for devices on which installing client software is not possible. Unified Access Gateway 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. Unified Access Gateway supports multiple use cases, but for the purposes of this guide, we will focus on providing secure external access to desktops managed by Horizon 7 onpremises. 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. Unified Access Gateway directs authenticated requests to the appropriate resource and discards any unauthenticated requests. It also can perform the authentication itself, leveraging an additional layer of authentication when enabled. Sizing This section gives guidance on the recommended sizing and load for each of the required components. For the most current numbers, limits, and recommendations, see the VMware Knowledge Base article VMware Horizon 7 Sizing Limits and Recommendations (2150348). Connection Server A single Connection Server supports a maximum of 4,000 sessions, although 2,000 is recommended as a best practice. To ensure that the environment includes redundancy and is able to handle failure, deploy one more server than is required for the number of connections (n 1). One key concept in a Horizon 7 environment design is the use of pods and blocks, which gives us a repeatable and scalable approach. When we are brokering connections only to physical desktops, we need focus only on the pod construct and can ignore the block construct. A pod is made up of a group of interconnected Connection Servers that broker connections to desktops or published applications. A pod can broker up to 20,000 sessions (12,000 recommended), including desktop and RDSH sessions. Up to seven Connection Servers are supported per pod with a recommendation of 12,000 desktop sessions in total per pod. Multiple pods can be interconnected using Cloud Pod Architecture (CPA). For complete design guidance, see the Component Design: Horizon 7 Architecture section in VMware Workspace ONE and VMware Horizon Reference Architecture guide. HORIZON 7
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Unified Access Gateway Unified Access Gateway gives three sizing options during deployment: standard, large, and extra-large. When deploying to provide secure edge services for Horizon, the standard size should be used. A standard-sized Unified Access Gateway supports 2,000 Horizon sessions. For complete design guidance, see the Component Design: Unified Access Gateway Architecture section in VMware Workspace ONE and VMware Horizon Reference Architecture guide Desktop Pools Desktop pools are required to allow management, entitlement, and user assignment to the desktop objects within Horizon. There are two main types of virtual desktop pools: automated and manual. Manual desktop pools are a collection of existing VMware vCenter Server virtual machines, physical computers, or third-party virtual machines. An individual pool should contain no more than 2,000 desktops. For the use case of managing physical desktops, manual pools are used. Manual assignment is made to the individual desktops to ensure that each employee gets connected to their own familiar physical machine. Load Balancing It is strongly recommended that end users connect to Unified Access Gateway using a load-balanced virtual IP (VIP). This ensures that user load is evenly distributed across all available Unified Access Gateway appliances. Using a load balancer also facilitates greater flexibility by enabling IT administrators to perform maintenance, upgrades, and configuration changes while minimizing impact to users. An existing load balancer can be used, or a new one such as VMware Avi Vantage can be deployed. See Configure Avi Vantage for VMware Horizon for more details. When load balancing Horizon traffic to multiple Unified Access Gateway appliances, the initial XML-API connection (authentication, authorization, and session management) needs to be load balanced. The secondary Horizon protocols must be routed to the same Unified Access Gateway appliance to which the primary Horizon XML-API protocol was routed. This allows the Unified Access Gateway to authorize the secondary protocols based on the authenticated user session. If the secondary protocol session is misrouted to a different Unified Access Gateway appliance from the primary protocol one, the session will not be authorized. The connection would therefore be dropped in the DMZ, and the protocol connection would fail. Misrouting secondary protocol sessions is a common problem if the load balancer is not configured correctly. The load balancer affinity must ensure that XML-API connections made for the whole duration of a session (with a default maximum of 10 hours) continue to be routed to the same Unified Access Gateway appliance. With the use case of providing secure, external access to resources, there is no need to provide a single namespace to the Horizon Connection Servers because only external users will be connecting. This means that there is no need to provide a load balancer VIP in front of the Connection Servers. HORIZON 8
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 4: Load Balancer Required for Unified Access Gateway Appliances but Not for Connection Servers Although the secondary protocol session must be routed to the same Unified Access Gateway appliance as was used for the primary XML-API connection, there is a choice of whether the secondary protocol session is routed through the load balancer or not. This normally depends on the capabilities of the load balancer. For example, with an F5 BIG-IP Local Traffic Manager (LTM), primary and secondary protocol traffic goes to the F5 LTM, and that ensures the correct routing of secondary protocol sessions by using source IP affinity. This has the advantage that there needs to be only a single public IP address. Where the load balancer does not have this capability, another option is to dedicate additional IP addresses for each Unified Access Gateway appliance so that the secondary protocol session can bypass the load balancer. For more detail on load balancing of Unified Access Gateway appliances, see: Unified Access Gateway Load Balancing Topologies Load Balancing across VMware Unified Access Gateway Appliances High Availability As an alternative to using an external load balancer, Unified Access Gateway provides, out-of-the-box, a high-availability solution for the Unified Access Gateway edge services. The solution supports up to 10,000 concurrent connections in a high-availability (HA) cluster and simplifies HA deployment and configuration of the services. For more information on the Unified Access Gateway High Availability component and configuration of edge services in HA, see the following resources: Configure High Availability Settings Unified Access Gateway Configured with Horizon High Availability section in the Workspace ONE and Horizon Reference Architecture. Scaling Designing to the recommended sizing of 2,000 sessions per Unified Access Gateway appliance and 2,000 sessions per Connection Server, a minimal deployment would have one of each server type. HORIZON 9
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 5: Minimal Design with Only One Unified Access Gateway Appliance and One Connection Server But as mentioned earlier, we should design for availability and deploy at least one additional Unified Access Gateway and one additional Connection Server. As an additional Unified Access Gateway is added: It is added to the load balancer VIP. It uses the new Connection Server, deployed at the same time, as a Connection Server URL target. HORIZON 10
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 6: Design for High Availability Using Two Unified Access Gateway Appliances and Two Connection Servers As we scale up the environment to cater to an increasing number of connections, we can add up to seven Connection Servers in the pod. HORIZON 11
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 7: Design for Maximum Pod Scale Using Seven Unified Access Gateway Appliances and Seven Connection Servers To scale higher than a single pod, multiple pods can be deployed and can be interconnected using Cloud Pod Architecture (CPA). Pods can be deployed on the same site or on different sites. Using Cloud Pod Architecture gives the option of global entitlements. A user can be connected to any Connection Server from any Horizon Pod that is part of the same Cloud Pod Architecture and will be directed and connected to the correct desktop, even if this is managed by another Pod. HORIZON 12
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 8: Multiple Horizon Pods Federated with Cloud Pod Architecture For the full documentation on how to set up and configure CPA, refer to Administering Cloud Pod Architecture in Horizon 7. Authentication Unified Access Gateway supports multiple authentication options; for example, pass-through, RSA SecurID, RADIUS, SAML, and certificates, including smart cards. Pass-through authentication forwards the request to the internal server or resource. Other authentication types enable authentication at the Unified Access Gateway, before passing authenticated traffic through to the internal resource. These options are depicted in the following diagrams. HORIZON 13
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 9: Unified Access Gateway Pass-Through Authentication Figure 10: Unified Access Gateway Two-Factor Authentication You can also use SAML to authenticate Horizon users against a third-party identity provider (IdP), leveraging Unified Access Gateway as the service provider (SP). This new capability requires Horizon Connection Server 7.11 or later, and user authentication must go through Unified Access Gateway. The authentication sequence can be configured as SAML and Passthrough or as just SAML: When Auth Methods is set to SAML and Passthrough, the SAML assertion is validated by Unified Access Gateway, and Connection Server authenticates the user against Active Directory when launching remote desktops and applications. When Auth Methods is set to SAML, the SAML assertion is validated by Unified Access Gateway and passed to the backend. Users single sign-on, leveraging the Horizon True SSO feature, to the remote desktops and applications. In both authentication methods, the user will be redirected to the IdP for SAML authentication. Both SP- and IdP-initiated flows are supported. HORIZON 14
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 11: Unified Access Gateway SAML Authentication For general information and configuration of SAML and Unified Access Gateway support for Horizon, see Configuring Horizon for Unified Access Gateway and Third-Party Identity Provider Integration. For detailed information and step-by-step guidance on how to integrate Okta and Unified Access Gateway for Horizon authentication, see the VMware Tech Zone Operational Tutorial Enabling SAML 2.0 Authentication for Horizon with Unified Access Gateway and Okta. For guidance on how to set up authentication in the DMZ, see Configuring Authentication in DMZ. Display Protocols Horizon 7 is a multi-protocol solution, with three remoting protocols available when creating desktop pools or RDSH-published applications: Blast Extreme, PCoIP, and RDP. When connecting to physical machines, Blast Extreme or RDP can be used. Blast Extreme Where possible, it is recommended to use Blast Extreme because it provides a much richer user experience. Use the Horizon Agent version 7.12 or later with the Horizon Client version 5.4 or later, as these introduce many optimizations and better performance for Blast. For more information on the key features, see VMware Blast Extreme. See the VMware Blast Extreme Optimization guide for more information, including optimization tips and how to configure Blast Extreme for certain network conditions. RDP Some versions of Windows will not support the use of Blast as a display protocol. For these, use RDP. Non-Enterprise Editions of Windows 10 The only supported edition of Windows 10 is Enterprise, although other editions may work with a few caveats. Where possible, change the license type used for Windows 10 to Enterprise edition to allow the use of Blast. On non-Enterprise editions of Windows 10, the RDP protocol should be used, so that the display is not mirrored on the physical monitor. Windows 7 Physical machines running Windows 7 will work with some caveats. These can only use RDP as the display protocol. The Horizon Client will need to be installed on the employee’s home device because HTML Access is not available for RDP connections. Configure desktop pools that contain Windows 7 to use the RDP protocol. Versions of Horizon 7 prior to version 7.7 will not support the use of Blast, but can broker to physical machines using the RDP display protocol. Ideally, upgrade the Connection Servers to version 7.12 or later and use Horizon Agent version 7.12 or later and HORIZON 15
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Horizon Client version 5.4 or later to allow the use of the Blast display protocol. While not supported for an extended period, it may be possible to use the newer versions of the Agent and Client while remaining on the existing version of Connection Servers. Network Ports To ensure correct communication between the components, it is important to understand the network port requirements for connectivity in a Horizon 7 deployment. The following diagram shows the ports required to allow a Blast Extreme connection. Figure 12: Blast Extreme Network Ports The network ports shown are destination ports. The tables that follow show more detail and indicate the source, destination, and the direction of traffic initiation. Horizon UDP protocols are bidirectional. Stateful firewalls should be configured to accept UDP reply datagrams. The following diagram shows the ports required to allow an RDP connection. Figure 13: RDP Network Ports The Network Ports in VMware Horizon 7 guide has more detail, along with diagrams illustrating the traffic. It even has specific sections and diagrams on internal, external, and tunnelled connections. To see more detail on the network ports required see the external connection table and the External Connection diagram. Connection Server The following table lists network ports for external connections from a client device to Horizon 7 components. Table 3: Network Ports for External Connections to Horizon Components HORIZON 16
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Source Destination Network Protocol Destination Port Details 443 Login traffic. Can also carry tunneled RDP, clientdrive redirection, and USB redirection traffic. UDP 443 Optional for login traffic. Blast Extreme tries a UDP login connection if the client experiences difficulty making a TCP connection to the Unified Access Gateway appliance. TCP 8443 Blast Extreme via Blast Secure Gateway on Unified Access Gateway for data traffic (performant channel). UDP 8443 Blast Extreme via Blast Secure Gateway on Unified Access Gateway for data traffic (adaptive transport). 443 Blast Extreme via Blast Secure Gateway on Unified Access Gateway for data traffic where port sharing is used. This would be instead of TCP 8443. 8443 Or 443 Horizon 7 HTML Access (web-based client). 8443 is the default but can be changed to 443 on Unified Access Gateway. TCP Horizon Client Unified Access Gateway TCP Browser for HTML Access Unified Access Gateway TCP Notes: The Blast Secure Gateway on Unified Access Gateway can dynamically adjusts to network conditions such as varying speeds and packet loss. In Unified Access Gateway, you can configure the ports used by the BEAT protocol. By default, Blast Extreme uses the standard ports TCP 8443 and UDP 8443. However, port 443 can also be configured for Blast TCP. Port configuration is set through the Unified Access Gateway Blast External URL property. See Blast TCP and UDP External URL Configuration Options. Unified Access Gateway The following table lists network ports for connections from a Unified Access Gateway to the Connection Server and the Horizon Agent. Table 4: Network Ports for Connections Among Horizon Components HORIZON 17
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Source Unified Access Gateway Destination Network Protocol Destination Port Details Horizon Connection Server TCP 443 Login. TCP 22443 Blast Extreme. UDP 22443 Blast Extreme. TCP 3389 RDP. 9427 Optional for client-drive redirection (CDR) and multimedia redirection (MMR). By default, when using Blast Extreme, CDR traffic is sidechannelled in the Blast Extreme ports indicated previously. If desired, this traffic can be separated onto the port indicated here. 32111 Optional for USB redirection. USB traffic can also be sidechannelled in the Blast Extreme ports indicated previously. See note below. Horizon Agent TCP TCP Note: With the VMware Blast display protocol, you can configure features, such as USB redirection, and client drive redirection, to send side channel traffic over a Blast Extreme ports. See: Enabling the USB Over Session Enhancement SDK Feature. Managing Access to Client Drive Redirection. Horizon Agent The following table lists network ports for connections from a physical, virtual desktop, or RDSH server to other Horizon 7 components. Table 5: Network Port Connections Between Horizon Agent and Connection Server Source Horizon Agent Destination Horizon Connection Server Network Protocol Destination Port Details TCP 4002 Java Message Service (JMS) when using enhanced security (default). TCP 4001 JMS (legacy). TCP 389 Required when doing an unmanaged agent registration; as is the case for physical machines. HORIZON 18
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Single DMZ For on-premises deployment of Horizon within a data center of an organization, it is common to install Unified Access Gateway appliances in a single DMZ, which provides a network isolation layer between the internet and the customer data center. Figure 14: Single DMZ Deployment Unified Access Gateway has built-in security mechanisms for all the Horizon protocols to ensure that the only network traffic entering the data center is traffic on behalf of an authenticated user. Any unauthenticated traffic is discarded in the DMZ. Double DMZ Some organizations have two DMZs (often called a double DMZ or a double-hop DMZ) that are sometimes used to provide an extra layer of security protection between the Internet and the internal network. In a double DMZ, traffic has to be passed through a specific reverse proxy in each DMZ layer. Traffic cannot simply bypass a DMZ layer. Note that in a Horizon deployment, a double DMZ is not required, but for environments where a double DMZ is mandated, an extra Unified Access Gateway appliance acting as a Web Reverse Proxy can be deployed in the outer DMZ. Figure 15: Double DMZ Deployment It is also possible to configure a double DMZ configuration for Horizon with minimal port requirements. This will not be as performant as a deployment with full Horizon protocol and port support as depicted above. HORIZON 19
USING HORIZON 7 TO ACCESS PHYSICAL WINDOWS MACHINES Figure 16: Double DMZ Deployment with Minimal Network Ports For more information, see Unified Access Gateway Double DMZ Deployment for Horizon. Implementation This section provides an overview of the Horizon 7 deployment process, points to specific documents for detailed instructions, and lists certain settings that were used in this guide. This assumes that you do not already have a Horizon 7 environment in place. If an existing Horizon 7 environment exists, you might be able to use that instead of setting up a separate environment. At a high-level, the steps involved are: 1. 2. 3. 4. Install and configure Horizon Connection Servers. Install and configure Unified Access Gateways. Install the Horizon Agent on the physical machines. Configure the desktop pool – Add physical machines, entitle and assign the users. Considerations Before deploying and configuring the solution consider the following and adjust the configuration of the solution accordingly. Machine Settings Evaluate the power policies for the physical machines and make changes to minimize the possibility of physical machines being shut down. All power saving options on physical machines should be disabled. This can be done by the use of a group policy (GPO). If a physical machine crashes or is shuts down, no remote access will be possible to it until it is restarted. Group Policies can be used to disable the shutdown option for users to minimize the risk of this. The use of Wake-On-LAN could also be considered to ensure that machines are powered on. User Assignment Understand how users normally use their desktops, what type of desktop pool is best suited and how users should be assigned access. One user per physical PC In this use case, each physical machine has a single primary user. Manual desktop pools will be used. Dedicated user assignment will be used. Users will be assigned to their specific physical desktop within the pool. Pooled physical PCs This is typical in a hot desk or shared environment where users can use any one of a pool of physical PCs. In environments like these, good profile management and application deployment systems are usually already in place. Manual desktop pools will be used. Floating user assignment will
The Connection Server brokers a connection to a Horizon Agent running on a Horizon-managed desktop or server. For this use case, the Horizon Agent is installed on physical Windows 10 machines. 3. The Horizon Client then forms a protocol session connection to a Horizon Agent in the physical machine.
What Is VMware Horizon 7 with Microsoft Office 365? This section briefly describes VMware Horizon 7 and Microsoft Office 365 in preparation for using them together. What is VMware Horizon 7? VMware Horizon 7 is a family of desktop and application virtualization solutions designed to deliver Windows and Linux virtual desktops and published .
software version. If using an older software version, note that the screenshots presented here may not match the WebUI exactly. 4. VMware Horizon Versions Supported v6.2 & later 5. VMware Horizon VMware Horizon (formerly VMware Horizon View) is a virtual desktop infrastructure (VDI) solution that simplifies
The AGA is limited to annotations to the provisions of the Horizon 2020 MGAs. For a more general overview of how Horizon 2020 grants work, see the . Horizon 2020 Online Manual. A comprehensive list of all Horizon 2020 referen
Horizon HX471S, Icom IC-M88, Icom IC-M72, West Marine VHF 250, Standard Horizon HX500S, Stan-dard Horizon HX600S, Standard Horizon HX370S, Raymarine Ray101. H andheld VHF radios come in handy for a variety of tasks aboard any boat. On small skiffs, they serve well as the main method of communicating—and you don’t
that the Horizon Client software supports. For more information about supported operating systems, see the VMware Horizon Client Documentation. What's New in VMware Horizon Session Enhancement SDK 3.3 The following list summarizes the new features and changes found in version 3.3 of the VMware Horizon Session Enhancement SDK.
From Horizon Client view Click the 3-Line or the Drop-down arrow at the upper-right corner. From the drop-down menu, select 'About VMware Horizon Client' From COSA Desktop From the Options drop-down, select either Support Information' or About VMware Horizon Client' to view your Horizon View Client version.
HORIZON FITNESS 800 BURTON BOULEVARD DEFOREST, WISCONSIN 53532 phone 1.888.993.3199 fax 1.608.842.1660 www.horizonfitness.com Rev. 1.0 ELLIPTICAL HORIZON E20 HORIZON E30 Owner's Guide Designed for life.TM horizon E20, 30 owner's guidev1.0.qxd 7/8/2003 2:03 PM Page 1. FRAME - LIFETIME
All material appearing in aliens is the work of individual authors, whose names are listed at the foot of each article. Contributions are not refereed, as this is a newsletter and not an academic journal. Ideas and comments in aliens are not intended in any way to represent the view of IUCN, SSC or the Invasive Species Specialist Group (ISSG) or sponsors, unless specifically stated to the .
