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
When you replace the default certificate with your own certificate, clients use your certificate to authenticate
the server. If your certificate is signed by a CA, the certificate for the CA itself is typically embedded in the
browser or is located in a trusted database that the client can access. After a client accepts the certificate, it
responds by sending a secret key, which is encrypted with the public key contained in the certificate. The secret
key is used to encrypt traffic between the client and the server.
You use the keytool and openssl utilities to create and manage certificates for View.
Add keytool and openssl to the System Path
keytool and openssl are key and certificate management utilities. You must add the paths to these utiilties to
the system environment Path variable so that you can run the utilities from any directory on your host.
Procedure
1 On your View Connection Server or security server host, right-click My Computer and select
Properties.
a On the Advanced tab, click Environment Variables.
b In the System variables group, select Path and click Edit.
c Type the path to the JRE directory in the Variable Value text box. Use a semicolon (;) to separate each
entry from other entries in the text box.
For example:
install_directory
\VMware\VMware View\Server\jre\bin
2 On your View Transfer Server host, right-click My Computer and select Properties.
a On the Advanced tab, click Environment Variables.
b In the System variables group, select Path and click Edit.
c Type the paths to the JRE and Apache directories in the Variable Value text box. Use a semicolon (;)
to separate each entry from other entries in the text box.
For example:
install_directory
\VMware\VMware
View\Server\httpd\bin;
install_directory
\VMware\VMware View\Server\jre\bin
3 Click OK until the Windows System Properties dialog box closes.
Use an Existing PKCS#12 Certificate and Private Key
If your organization already has a valid server SSL certificate, you can use that certificate to replace the default
server SSL certificate provided with View Connection Server.
To use an existing certificate, you also need the accompanying private key. The PKCS#12 file format includes
both the server certificate and the private key.
If a PKCS#12 file contains a server certificate that is signed by an intermediate CA rather than by a root CA,
you must convert the PKCS#12 keystore to JKS format. See “Convert a PKCS#12 Keystore to JKS Format,” on
page 82.
You can use several different tools to generate PKCS#12 files. This procedure explains how to use the Internet
Information Services (IIS) Manager to generate a PKCS#12 file from an IIS certificate store, and how to use
openssl to extract a PEM format certificate and private key.
Prerequisites
If you want to create a certificate that you can use with a View Transfer Server instance, add openssl to the
system Path variable on your host. See “Add keytool and openssl to the System Path,” on page 80
VMware View Installation
80 VMware, Inc.