5.2
Table Of Contents
- VMware Horizon View Installation
- Contents
- VMware Horizon View Installation
- System Requirements for Server Components
- System Requirements for Guest Operating Systems
- Preparing Active Directory
- Configuring Domains and Trust Relationships
- Creating an OU for View Desktops
- Creating OUs and Groups for Kiosk Mode Client Accounts
- Creating Groups for View Users
- Creating a User Account for vCenter Server
- Create a User Account for View Composer
- 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 Products Silently by Using MSI Command-Line Options
- Installing View Transfer Server
- 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 View Clients to Trust Root and Intermediate Certificates
- Configuring Certificate Revocation Checking on Server Certificates
- Configuring Certificate Checking in View Client for Windows
- Configure the PCoIP Secure Gateway to Use a New SSL Certificate
- View Transfer Server and SSL Certificates
- Setting View Administrator to Trust a vCenter Server or View Composer Certificate
- Benefits of Using SSL Certificates Signed by a CA
- Configuring View for the First Time
- Configuring User Accounts for vCenter Server and View Composer
- Where to Use the vCenter Server User and Domain User for View Composer
- Configure a vCenter Server User for View Manager, View Composer, and Local Mode
- View Manager Privileges Required for the vCenter Server User
- View Composer Privileges Required for the vCenter Server User
- Local Mode Privileges Required for the vCenter Server User
- Configuring View Connection Server for the First Time
- View Administrator and View Connection Server
- Log In to View Administrator
- Install the View Connection Server License Key
- Add vCenter Server Instances to View Manager
- 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 View Desktop Logon Storms
- Accept the Thumbprint of a Default SSL Certificate
- Configuring View Client Connections
- 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
- Replace the Default Ports for View Transfer Server
- Sizing Windows Server Settings to Support Your Deployment
- Configuring User Accounts for vCenter Server and View Composer
- Adding the View Desktops Plug-in to the vSphere Web Client
- Configuring Event Reporting
- Index
3 On the General tab, delete the Friendly name text and type vdm.
4 Click Apply and click OK.
What to do next
Import the root certificate and intermediate certificates into the Windows local computer certificate store.
After all certificates in the chain are imported, you must restart the View Connection Server service or
Security Server service to make your changes take effect.
Import a Root Certificate and Intermediate Certificates into a Windows
Certificate Store
If the Windows Server host on which View Connection Server is installed does not trust the root certificate
for the signed SSL server certificate, you must import the root certificate into the Windows local computer
certificate store. In addition, if the View Connection Server host does not trust the root certificates of the SSL
server certificates configured for security server, View Composer, and vCenter Server hosts, you also must
import those root certificates.
If the View Connection Server, security server, View Composer, and vCenter Server certificates are signed
by a root CA that is known and trusted by the View Connection Server host, and there are no intermediate
certificates in your certificate chains, you can skip this task. Commonly used Certificate Authorities are
likely to be trusted by the host.
NOTE You do not have to import the root certificate into View Composer, vCenter Server, or security server
hosts.
If a server certificate is signed by an intermediate CA, you also must import each intermediate certificate in
the certificate chain. To simplify client configuration, import the entire intermediate chain to security server,
View Composer, and vCenter Server hosts as well as View Connection Server hosts. If intermediate
certificates are missing from a View Connection Server or security server host, they must be configured for
View Clients and computers that launch View Administrator. If intermediate certificates are missing from a
View Composer or vCenter Server host, they must be configured for each View Connection Server instance.
If you already verified that the entire certificate chain is imported into the Windows local computer
certificate store, you can skip this task.
NOTE If a SAML 2.0 authenticator is configured for use by a View Connection Server instance, the same
guidelines apply to the SAML 2.0 authenticator. If the View Connection Server host does not trust the root
certificate configured for a SAML 2.0 authenticator, or if the SAML 2.0 server certificate is signed by an
intermediate CA, you must ensure that the certificate chain is imported into the Windows local computer
certificate store.
Procedure
1 In the MMC console on the Windows Server host, expand the Certificates (Local Computer) node and
go to the Trusted Root Certification Authorities > Certificates folder.
n
If your root certificate is in this folder, and there are no intermediate certificates in your certificate
chain, skip to step 7.
n
If your root certificate is not in this folder, proceed to step 2.
2 Right-click the Trusted Root Certification Authorities > Certificates folder and click All Tasks >
Import.
3 In the Certificate Import wizard, click Next and browse to the location where the root CA certificate is
stored.
4 Select the root CA certificate file and click Open.
VMware Horizon View Installation
78 VMware, Inc.