Installation
Table Of Contents
- View Installation
- Contents
- View Installation
- System Requirements for Server Components
- System Requirements for Guest Operating Systems
- Installing View in an IPv6 Environment
- Setting Up View in an IPv6 Environment
- Supported vSphere , Database, and Active Directory Versions in an IPv6 Environment
- Supported Operating Systems for View Servers in an IPv6 Environment
- Supported Windows Operating Systems for Desktops and RDS Hosts in an IPv6 Environment
- Supported Clients in an IPv6 Environment
- Supported Remoting Protocols in an IPv6 Environment
- Supported Authentication Types in an IPv6 Environment
- Other Supported Features in an IPv6 Environment
- Preparing Active Directory
- Configuring Domains and Trust Relationships
- Creating an OU for Remote Desktops
- Creating OUs and Groups for Kiosk Mode Client Accounts
- Creating Groups for Users
- Creating a User Account for vCenter Server
- Creating a User Account for a Standalone View Composer Server
- Create a User Account for View Composer AD Operations
- Configure the Restricted Groups Policy
- Using View Group Policy Administrative Template Files
- Prepare Active Directory for Smart Card Authentication
- Installing View Composer
- Installing View Connection Server
- Installing the View Connection Server Software
- Installation Prerequisites for View Connection Server
- Install View Connection Server with a New Configuration
- Install a Replicated Instance of View Connection Server
- Configure a Security Server Pairing Password
- Install a Security Server
- Firewall Rules for View Connection Server
- Reinstall View Connection Server with a Backup Configuration
- Microsoft Windows Installer Command-Line Options
- Uninstalling View Components Silently by Using MSI Command-Line Options
- Configuring SSL Certificates for View Servers
- Understanding SSL Certificates for View Servers
- Overview of Tasks for Setting Up SSL Certificates
- Obtaining a Signed SSL Certificate from a CA
- Configure View Connection Server, Security Server, or View Composer to Use a New SSL Certificate
- Configure Client Endpoints to Trust Root and Intermediate Certificates
- Configuring Certificate Revocation Checking on Server Certificates
- Configure the PCoIP Secure Gateway to Use a New SSL Certificate
- Setting View Administrator to Trust a vCenter Server or View Composer Certificate
- Benefits of Using SSL Certificates Signed by a CA
- Troubleshooting Certificate Issues on View Connection Server and Security Server
- Configuring View for the First Time
- Configuring User Accounts for vCenter Server and View Composer
- Configuring View Connection Server for the First Time
- View Administrator and View Connection Server
- Log In to View Administrator
- Install the Product License Key
- Add vCenter Server Instances to View
- Configure View Composer Settings
- Configure View Composer Domains
- Allow vSphere to Reclaim Disk Space in Linked-Clone Virtual Machines
- Configure View Storage Accelerator for vCenter Server
- Concurrent Operations Limits for vCenter Server and View Composer
- Setting a Concurrent Power Operations Rate to Support Remote Desktop Logon Storms
- Accept the Thumbprint of a Default SSL Certificate
- Configuring Horizon Client Connections
- Configure the PCoIP Secure Gateway and Secure Tunnel Connections
- Configure Secure HTML Access
- Configuring External URLs for Secure Gateway and Tunnel Connections
- Set the External URLs for a View Connection Server Instance
- Modify the External URLs for a Security Server
- Give Preference to DNS Names When View Connection Server Returns Address Information
- Replacing Default Ports for View Services
- Replace the Default HTTP Ports or NICs for View Connection Server Instances and Security Servers
- Replace the Default Ports or NICs for the PCoIP Secure Gateway on View Connection Server Instances and on Security Servers
- Replace the Default Port for View Composer
- Change the Port Number for HTTP Redirection to Connection Server
- Prevent HTTP Redirection for Client Connections to Connection Server
- Enable Remote Access to View Performance Counters on Connection Servers
- Sizing Windows Server Settings to Support Your Deployment
- Configuring Event Reporting
- Index
Table 6‑3. MSI Properties for Silently Installing a Security Server (Continued)
MSI Property Description Default Value
VDM_SERVER_SS_PCOIP_T
CPPORT
The PCoIP Secure Gateway external TCP port number. This property is
supported only when the security server is installed on Windows Server
2008 R2 or later.
For example: VDM_SERVER_SS_PCOIP_TCPPORT=4172
This property is required if you plan to use the PCoIP Secure Gateway
component.
None
VDM_SERVER_SS_PCOIP_U
DPPORT
The PCoIP Secure Gateway external UDP port number. This property is
supported only when the security server is installed on Windows Server
2008 R2 or later.
For example: VDM_SERVER_SS_PCOIP_UDPPORT=4172
This property is required if you plan to use the PCoIP Secure Gateway
component.
None
VDM_SERVER_SS_BSG_EXT
URL
The Blast Secure Gateway external URL. The URL must contain the
HTTPS protocol, an externally resolvable security server name, and port
number
For example:
VDM_SERVER_SS_BSG_EXTURL=https://view.companydomain.com:
8443
The default port number is 8443. A Blast Secure Gateway must be
installed on the security server to allow users to make Web connections
to View desktops.
None
VDM_SERVER_SS_FORCE_I
PSEC
Forces IPsec to be used between the security server and its paired View
Connection Server instance.
By default, an unattended installation and pairing of security server to a
View Connection Server instance with IPsec disabled causes the pairing
to fail.
The default value of 1 forces IPsec pairing. Set this value to 0 to allow
pairing without IPsec.
1
VDM_IP_PROTOCOL_USAG
E
Specifies the IP version that View components use for communication.
The possible values are IPv4 and IPv6
IPv4
Prepare to Upgrade or Reinstall a Security Server
Before you can upgrade or reinstall a security server instance, you must remove the current IPsec rules that
govern communication between the security server and its paired View Connection Server instance. If you
do not take this step, the upgrade or reinstallation fails.
IMPORTANT This task pertains to View 5.1 and later security servers. If does not apply to View 5.0.x and
earlier security servers.
By default, communication between a security server and its paired View Connection Server instance is
governed by IPsec rules. When you upgrade or reinstall the security server and pair it again with the View
Connection Server instance, a new set of IPsec rules must be established. If the existing IPsec rules are not
removed before you upgrade or reinstall, the pairing fails.
You must take this step when you upgrade or reinstall a security server and are using IPsec to protect
communication between the security server and View Connection Server.
View Installation
64 VMware, Inc.