6.0

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.
NOTE 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, View 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.
Prerequisites
n
Verify that at least one View Connection Server instance is installed and configured 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 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,” on page 38.
n
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.
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 hotfix that is described in KB 978116 at
http://support.microsoft.com/kb/978116.
n
Verify that your installation satisfies the requirements described in “View 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 View Connection
Server Instances,” on page 9.
n
Prepare your environment for the installation. See “Installation Prerequisites for View Connection
Server,” on page 37.
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 Configuration,” on page 38.
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 56.
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 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.
n
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,” on page 57.
View Installation
44 VMware, Inc.