4.6
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 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 Certificate Authentication
- Replacing the Default Certificate
- Add keytool and openssl to the System Path
- Use an Existing PKCS#12 Certificate and Private Key
- Convert a PKCS#12 Keystore to JKS Format
- Creating a New SSL Certificate
- Configure a View Connection Server Instance or Security Server to Use a New Certificate
- Configure a View Transfer Server Instance to Use a New Certificate
- Configure SSL for Client Connections
- Configure SSL for View Transfer Server Communications
- Using Group Policy to Configure Certificate Checking in View Client
- Creating an Event Database
- Installing and Starting View Client
- Install the Windows-Based View Client or View Client with Local Mode
- Start the Windows-Based View Client or View Client with Local Mode
- Install View Client by Using View Portal
- Install View Client on Mac OS X
- Start View Client on Mac OS X
- Set Printing Preferences for the Virtual Printer Feature on Windows Clients
- Using USB Printers
- Installing View Client Silently
- Index
Convert a PKCS#12 Keystore to JKS Format
If you already have a PKCS#12 keystore file and a server certificate that is signed by an intermediate CA rather
than a root CA, you must convert the PKCS#12 keystore to JKS format before you can use it with View.
Procedure
1 If the PKCS#12 keystore does not already contain the intermediate certificate, create the JKS keystore and
add the intermediate certificate to the keystore.
To avoid seeing errors from keytool, you must add the intermediate certificate to the keystore before you
can add the server certificate.
a Save the intermediate certificate as intermediateCA.p7 in the directory that contains the keystore file.
b Import the intermediate certificate into the keystore file.
For example:
keytool -importcert -keystore keys.jks -storepass secret -trustcacerts -alias
intermediateCA -file intermediateCA.p7
2 Add the server certificate and private key from the PKCS#12 file to the JKS keystore.
For example:
keytool -importkeystore -destkeystore keys.jks -deststorepass secret -srckeystore keys.p12 -
srcstoretype PKCS12 -srcstorepass clydenw
The keytool utility creates the JKS keystore if it does not already exist.
What to do next
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 85.
Creating a New SSL Certificate
You can use a self-signed certificate or a certificate signed by a CA to replace the default server SSL certificate
that is provided with View Connection Server.
A CA is a trusted third party that guarantees the identity of the certificate and its creator. When a certificate is
signed by a trusted CA, users no longer receive messages asking them to verify the certificate, and thin client
devices can connect without requiring additional configuration. If your clients need to determine the origin
and integrity of the data they receive, you should obtain a CA-signed certificate rather than use a self-signed
certificate.
1 Obtain a Signed Certificate from a CA for Use with a View Connection Server Instance or Security
Server on page 83
To obtain a signed certificate from a CA, you must use keytool to generate a keystore file and a certificate
signing request (CSR). For testing purposes, you can obtain a free temporary certificate based on an
untrusted root from GlobalSign, Thawte, or VeriSign.
2 Obtain a Signed Certificate from a CA for Use with a View Transfer Server Instance on page 84
To obtain a signed certificate from a CA, you must use openssl to generate a private key file and a
certificate signing request (CSR). For testing purposes, you can obtain a free temporary certificate based
on an untrusted root from GlobalSign, Thawte, or VeriSign.
VMware View Installation
82 VMware, Inc.