Installation

After the installation, identical View LDAP conguration 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 conguration is updated with the changes that took place during the outage.
N 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 congures 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 seing 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.
Prerequisites
n
Verify that at least one View Connection Server instance is installed and congured on the network.
n
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 rst 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 Conguration,” on page 51.
n
If the existing View Connection Server instance is in a dierent 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.
n
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 hotx that is described in KB 978116 at
hp://support.microsoft.com/kb/978116.
n
Verify that your installation satises the requirements described in “Horizon Connection Server
Requirements,” on page 7.
n
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,” on page 9.
n
Prepare your environment for the installation. See “Installation Prerequisites for View Connection
Server,” on page 50.
n
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 Conguration,” on page 51.
n
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,” on page 71.
n
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 proles. It is recommended that you turn this
seing to on for all proles. By default, IPsec rules govern connections between security server and
View Connection Server and require Windows Firewall with Advanced Security to be enabled.
View Installation
58 VMware, Inc.