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
3 On the General tab, delete the Friendly name text and type vdm.
4 Click Apply and click OK.
5 Verify that no other server certificates in the Personal > Certificates folder have a Friendly name of vdm.
a Locate any other server certificate, right-click the certificate, and click Properties.
b If the certificate has a Friendly name of vdm, delete the name, 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.
You must import untrusted root certificates on all replicated View Connection Server instances in a pod.
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
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 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 authenticator, or if the SAML 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.
View Installation
78 VMware, Inc.