Installation guide
Table Of Contents
- VMware View Installation Guide
- Contents
- About This Book
- 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
- Export an Existing Microsoft IIS SSL Server Certificate
- 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
- Using USB Printers
- Installing View Client Silently
- Index
Preparing Active Directory 3
View uses your existing Microsoft Active Directory infrastructure for user authentication and management.
You must perform certain tasks to prepare Active Directory for use with View.
View supports the following versions of Active Directory:
n
Windows 2000 Active Directory
n
Windows 2003 Active Directory
n
Windows 2008 Active Directory
This chapter includes the following topics:
n
“Configuring Domains and Trust Relationships,” on page 23
n
“Creating an OU for View Desktops,” on page 24
n
“Creating OUs and Groups for Kiosk Mode Client Accounts,” on page 24
n
“Creating Groups for View Users,” on page 24
n
“Creating a User Account for vCenter Server,” on page 24
n
“Create a User Account for View Composer,” on page 25
n
“Configure the Restricted Groups Policy,” on page 25
n
“Using View Group Policy Administrative Template Files,” on page 26
n
“Prepare Active Directory for Smart Card Authentication,” on page 26
Configuring Domains and Trust Relationships
You must join each View Connection Server host to an Active Directory domain. The host must not be a domain
controller. You place View desktops in the same domain as the View Connection Server host or in a domain
that has a two-way trust relationship with the View Connection Server host's domain.
You can entitle users and groups in the View Connection host's domain to View desktops and pools. You can
also select users and groups from the View Connection Server host's domain to be administrators in View
Administrator. To entitle or select users and groups from a different domain, you must establish a two-way
trust relationship between that domain and the View Connection Server host's domain.
Users are authenticated against Active Directory for the View Connection Server host's domain and against
any additional user domains with which a trust agreement exists.
NOTE Because security servers do not access any authentication repositories, including Active Directory, they
do not need to reside in an Active Directory domain.
VMware, Inc.
23