5.1

These requirements also apply to replica and security server View Connection Server instances that you install
for high availability or external access.
IMPORTANT The physical or virtual machine that hosts View Connection Server must use a static IP address.
Supported Operating Systems for View Connection Server
You must install View Connection Server on a Windows Server 2008 R2 operating system.
The following operating systems support all View Connection Server installation types, including standard,
replica, and security server installations.
Table 3-2. Operating System Support for View Connection Server
Operating System Version Edition
Windows Server 2008 R2 64-bit Standard
Enterprise
Windows Server 2008 R2 SP1 64-bit Standard
Enterprise
Upgrade Requirements for View Connection Server
The View Connection Server upgrade process has specific requirements and limitations.
n
View Connection Server requires a valid license key for View 5.1.
n
The domain user account that you use to install the new version of View Connection Server must have
administrative privileges on the View Connection Server host. The View Connection Server administrator
must have administrative credentials for vCenter Server.
n
With View Connection Server 5.0 and later releases, when you run the installer, you authorize a View
Administrators account. You can specify the local Administrators group or a domain user or group
account. View assigns full View Administration rights, including the right to install replicated View
Connection Server instances, to this account only. If you specify a domain user or group, you must create
the account in Active Directory before you run the installer.
n
With View 5.1, when you back up View Connection Server, the View LDAP configuration is exported as
encrypted LDIF data. To restore the encrypted backup View configuration, you must provide the data
recovery password. The password must contain between 1 and 128 characters.
Security-Related Requirements
n
View Connection Server requires an SSL certificate that is signed by a CA (certificate authority) and that
your clients can validate. To improve the security of VMware View deployments, VMware is deprecating
support for View Client authentication and brokering over a non-secured HTTP connection. In the past,
you could use the default self-signed certificate that is generated in the absence of a CA-signed certificate.
With View 5.1, you must replace the default self-signed certificate as soon as possible. Self-signed
certificates are shown as invalid in View Administrator.
Also, as a security enhancement, updated View clients expect information about the server's certificate to
be communicated as part of the XML handshake between client and server. Often updated clients do not
trust self-signed certificates. For complete information about security certificate requirements, see
"Configuring SSL Certificates for View Servers" in the VMware View Installation guide.
NOTE If your original View servers already have SSL certificates signed by a CA, during the upgrade,
View imports your existing CA-signed certificate into the Windows Server certificate store.
VMware View Upgrades
12 VMware, Inc.