6.0

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 Active Directory Domain Services (AD DS) domain functional levels:
n
Windows Server 2003
n
Windows Server 2008
n
Windows Server 2008 R2
n
Windows Server 2012
n
Windows Server 2012 R2
This chapter includes the following topics:
n
“Configuring Domains and Trust Relationships,” on page 19
n
“Creating an OU for Remote Desktops,” on page 20
n
“Creating OUs and Groups for Kiosk Mode Client Accounts,” on page 20
n
“Creating Groups for Users,” on page 21
n
“Creating a User Account for vCenter Server,” on page 21
n
“Create a User Account for View Composer,” on page 21
n
“Configure the Restricted Groups Policy,” on page 22
n
“Using View Group Policy Administrative Template Files,” on page 23
n
“Prepare Active Directory for Smart Card Authentication,” on page 23
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 remote 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. Specifically
this must be an external non-transitive two-way trust.
You can entitle users and groups in the View Connection host's domain to remote desktops and
applications. 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.
VMware, Inc.
19