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
2 Configure a PSG Certificate in the Windows Certificate Store on page 84
To replace the default PSG certificate with a CA-signed certificate, you must configure the certificate
and its private key in the Windows local computer certificate store on the View Connection Server or
security server computer on which the PSG is running.
3 Set the PSG Certificate Friendly Name in the Windows Registry on page 86
The PSG identifies the SSL certificate to use by means of the server name and certificate Friendly
name. You must set the Friendly name value in the Windows registry on the View Connection Server
or security server computer on which the PSG is running.
4 (Optional) Force a CA-Signed Certificate to Be Used for Connections to the PSG on page 86
You can ensure that all client connections to the PSG use the CA-signed certificate for the PSG instead
of the default legacy certificate. This procedure is not required to configure a CA-signed certificate for
the PSG. Take these steps only if it makes sense to force the use of a CA-signed certificate in your View
deployment.
Verify That the Server Name Matches the PSG Certificate Subject Name
When a View Connection Server instance or security server is installed, the installer creates a registry setting
with a value that contains the FQDN of the computer. You must verify that this value matches the server
name part of the URL that security scanners use to reach the PSG port. The server name also must match the
subject name or a subject alternate name (SAN) of the SSL certificate that you intend to use for the PSG.
For example, if a scanner connects to the PSG with the URL https://view.customer.com:4172, the registry
setting must have the value view.customer.com. Note that the FQDN of the View Connection Server or
security server computer that is set during installation might not be the same as this external server name.
Procedure
1 Start the Windows Registry Editor on the View Connection Server or security server host where the
PCoIP Secure Gateway is running.
2 Navigate to the HKEY_LOCAL_MACHINE\SOFTWARE\Teradici\SecurityGateway\SSLCertPsgSni registry
setting.
3 Verify that the value of the SSLCertPsgSni setting matches the server name in the URL that scanners
will use to connect to the PSG and matches the subject name or a subject alternate name of the SSL
certificate that you intend to install for the PSG.
If the value does not match, replace it with the correct value.
4 Restart the VMware Horizon View PCoIP Secure Gateway service to make your changes take effect.
What to do next
Import the CA-signed certificate into the Windows local computer certificate store and configure the
certificate Firendly name.
Configure a PSG Certificate in the Windows Certificate Store
To replace the default PSG certificate with a CA-signed certificate, you must configure the certificate and its
private key in the Windows local computer certificate store on the View Connection Server or security
server computer on which the PSG is running.
If you intend the PSG to use a unique certificate, you must import the certificate into the Windows local
computer certificate store with an exportable private key and set the appropriate Friendly name.
If you intend the PSG to use the same certificate as the server, you do not have to follow this procedure.
However, in the Windows registry you must set the server name to match the server certificate subject name
and set the Friendly name to vdm.
View Installation
84 VMware, Inc.