5.0
Table Of Contents
- VMware View Installation
- Contents
- VMware View Installation
- System Requirements for Server Components
- System Requirements for Client Components
- Supported Operating Systems for View Agent
- Supported Operating Systems for Windows-Based View Client and View Client with Local Mode
- Hardware Requirements for Local Mode Desktops
- Client Browser Requirements for View Portal
- Remote Display Protocol and Software Support
- Adobe Flash Requirements
- Smart Card Authentication Requirements
- 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
- Microsoft Windows Installer Command-Line Options
- Uninstalling View Products Silently by Using MSI Command-Line Options
- 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
- Configuring View Client Connections
- Sizing Windows Server Settings to Support Your Deployment
- Installing the View Connection Server Software
- Installing View Transfer Server
- Configuring SSL Certificates for View Servers
- Configuring SSL Certificates for View Connection Server and Security Server
- Configuring SSL Certificates for View Transfer Server
- Prepare an Existing Certificate in PKCS#12 Format for Use with View Transfer Server
- Obtain a Signed Certificate from a CA for Use with a View Transfer Server Instance
- Generate a Self-Signed Certificate for View Transfer Server
- Configure a View Transfer Server Instance to Use a Certificate
- Configure SSL for View Transfer Server Communications
- Configuring Certificate Checking in View Client for Windows
- Appendix: Additional SSL Configuration Tasks
- Creating an Event Database
- Installing and Starting View Client
- Index
Table 7-1. SSL Certificate Formats and Configuration Path (Continued)
If you have this SSL certificate
format... Take these steps
PKCS#12 - You are not sure which type of
CA has signed your certificate.
If you are not sure whether your PKCS#12 file is signed by a root CA or
intermediate CA, see “Determine the Type of CA Signature on Your PKCS#12
Certificate,” on page 77.
PEM If your organization provides you with an SSL certificate in PEM format, the
certificate must be exported to PKCS#12 format. A certificate in PEM format
might have an extension such as .crt or .pem. Consult with the provider of
your certificate for advice on exporting the certificate to PKCS#12 format.
JKS If your organization provides you with a Java keystore (JKS) file, you can use
the existing JKS file when you configure your View Connection Server instance
or security server to use the certificate. A JKS file might have an extension such
as .jks. See “Configure a View Connection Server Instance or Security Server
to Use a New Certificate,” on page 81.
Determine the Type of CA Signature on Your PKCS#12 Certificate
If you are not sure whether your PKCS#12 file is signed by a root CA or intermediate CA, you can determine
the signature type by using the certutil utility.
Procedure
1 Navigate to the directory that contains the PKCS#12 keystore file.
For example: abc.p12
2 Run the certutil command.
For example: certutil abc.p12
3 At the Windows prompt, type your PFX password.
The utility displays information about the PKCS#12 keystore file, including summaries of all certificates
in the trust chain.
4 Look for the lines describing the Signature, Root Certificate, and Intermediate Certificate.
For example, a self-signed certificate might display the following lines:
Signature matches Public Key
Root Certificate: Subject matches Issuer
What to do next
If your PKCS#12 file contains a server certificate that is signed by a root CA and not an intermediate CA, you
can use your existing PKCS#12 file when you configure your View Connection Server instance or security
server to use the certificate. See “Configure a View Connection Server Instance or Security Server to Use a New
Certificate,” on page 81.
If a PKCS#12 file contains a server certificate that is signed by an intermediate CA rather than by a root CA,
you must import the PKCS#12 keystore into a JKS keystore. See “Convert a PKCS#12 File to JKS Format,” on
page 78.
Chapter 7 Configuring SSL Certificates for View Servers
VMware, Inc. 77