To provide high availability and load balancing, you can install one or more additional instances of View Connection Server that replicate an existing View Connection Server instance. After a replica installation, the existing and newly installed instances of View Connection Server are identical.
About this task
When you install a replicated instance, View copies the View LDAP configuration data from the existing View Connection Server instance.
After the installation, identical View LDAP configuration data is maintained on all View Connection Server instances in the replicated group. When a change is made on one instance, the updated information is copied to the other instances.
If a replicated instance fails, the other instances in the group continue to operate. When the failed instance resumes activity, its configuration is updated with the changes that took place during the outage.
Replication functionality is provided by View LDAP, which uses the same replication technology as Active Directory.
The replica server software cannot coexist on the same virtual or physical machine with any other View software component, including a security server, View Connection Server, View Composer, Horizon Agent, or Horizon Client.
By default, the HTML Access component is installed on the View Connection Server host when you install View Connection Server. This component configures the View user portal page to display an HTML Access icon in addition to the Horizon Client icon. The additional icon allows users to select HTML Access when they connect to their desktops.
For an overview of setting up View Connection Server for HTML Access, see "Preparing View Connection Server and Security Servers for HTML Access" in the Using HTML Access document, located on the Horizon Client Documentation page.
Verify that at least one View Connection Server instance is installed and configured on the network.
To install the replicated instance, you must log in as a user with the View Administrators role. You specify the account or group with the View Administrators role when you install the first instance of View Connection Server. The role can be assigned to the local Administrators group or a domain user or group. See Install View Connection Server with a New Configuration.
If the existing View Connection Server instance is in a different domain than the replicated instance, the domain user must also have View Administrator privileges on the Windows Server computer where the existing instance is installed.
If you use MIT Kerberos authentication to log in to a Windows Server 2008 R2 computer on which you are installing View Connection Server, install the Microsoft hotfix that is described in KB 978116 at http://support.microsoft.com/kb/978116.
Verify that your installation satisfies the requirements described in Horizon Connection Server Requirements.
Verify that the computers on which you install replicated View Connection Server instances are connected over a high-performance LAN. See Network Requirements for Replicated Horizon Connection Server Instances.
Prepare your environment for the installation. See Installation Prerequisites for View Connection Server.
If you install a replicated View Connection Server instance that is View 5.1 or later, and the existing View Connection Server instance you are replicating is View 5.0.x or earlier, prepare a data recovery password. See Install View Connection Server with a New Configuration.
Familiarize yourself with the network ports that must be opened on the Windows Firewall for View Connection Server instances. See Firewall Rules for View Connection Server.
If you plan to pair a security server with this View Connection Server instance, verify that Windows Firewall with Advanced Security is set to on in the active profiles. It is recommended that you turn this setting to on for all profiles. By default, IPsec rules govern connections between security server and View Connection Server and require Windows Firewall with Advanced Security to be enabled.
If your network topology includes a back-end firewall between a security server and the View Connection Server instance, you must configure the firewall to support IPsec. See Configuring a Back-End Firewall to Support IPsec.
- Download the Connection Server installer file from the VMware download site at https://my.vmware.com/web/vmware/downloads.
Under Desktop & End-User Computing, select the VMware Horizon 7 download, which includes Connection Server.
The installer filename is VMware-viewconnectionserver-x86_64-y.y.y-xxxxxx.exe, where xxxxxx is the build number and y.y.y is the version number.
- To start the Connection Server installation program, double-click the installer file.
- Accept the VMware license terms.
- Accept or change the destination folder.
- Select the View Replica Server installation option.
- Select the Internet Protocol (IP) version, IPv4 or IPv6.
You must install all View components with the same IP version.
- Select whether to enable or disable FIPS mode.
This option is available only if FIPS mode is enabled in Windows.
- Make sure that Install HTML Access is selected if you intend to allow users to connect to their desktops by using HTML Access.
If IPv4 is selected, this setting is selected by default. If IPv6 is selected, this setting is not displayed because HTML Access is not supported in an IPv6 environment.
- Enter the host name or IP address of the existing View Connection Server instance you are replicating.
- Type a data recovery password and, optionally, a password reminder.
You are prompted for a data recovery password only if the existing View Connection Server instance you are replicating is View 5.0.x or earlier.
- Choose how to configure the Windows Firewall service.
Configure Windows Firewall automatically
Let the installer configure Windows Firewall to allow the required network connections.
Do not configure Windows Firewall
Configure the Windows firewall rules manually.
Select this option only if your organization uses its own predefined rules for configuring Windows Firewall.
- Complete the installation wizard to finish installing the replicated instance.
- Check for new patches on the Windows Server computer and run Windows Update as needed.
Even if you fully patched the Windows Server computer before you installed View Connection Server, the installation might have enabled operating system features for the first time. Additional patches might now be required.
The Horizon 7 services are installed on the Windows Server computer:
VMware Horizon Connection Server
VMware Horizon View Framework Component
VMware Horizon View Message Bus Component
VMware Horizon View Script Host
VMware Horizon View Security Gateway Component
VMware Horizon View PCoIP Secure Gateway
VMware Horizon View Blast Secure Gateway
VMware Horizon View Web Component
VMware VDMDS, which provides View LDAP directory services
For information about these services, see the View Administration document.
If the Install HTML Access setting was selected during the installation, the HTML Access component is installed on the Windows Server computer. This component configures the HTML Access icon in the Horizon 7 user portal page and enables the VMware Horizon View Connection Server (Blast-In) rule in the Windows Firewall. This firewall rule allows Web browsers on client devices to connect to the Connection Server on TCP port 8443.
What to do next
Configure an SSL server certificate for the View Connection Server instance. See Configuring SSL Certificates for View Servers.
You do not have to perform an initial View configuration on a replicated instance of View Connection Server. The replicated instance inherits its configuration from the existing View Connection Server instance.
However, you might have to configure client connection settings for this View Connection Server instance, and you can tune Windows Server settings to support a large deployment. See Configuring Horizon Client Connections and Sizing Windows Server Settings to Support Your Deployment.
If you are reinstalling View Connection Server and you have a data collector set configured to monitor performance data, stop the data collector set and start it again.