You must set up system and database accounts to administer View components.

Table 1. View System Accounts

View Component

Required Accounts

Horizon Client

Configure user accounts in Active Directory for the users who have access to remote desktops and applications. The user accounts must be members of the Remote Desktop Users group, but the accounts do not require View administrator privileges.

vCenter Server

Configure a user account in Active Directory with permission to perform the operations in vCenter Server that are necessary to support View.

For information about the required privileges, see the View Installation document.

View Composer

Create a user account in Active Directory to use with View Composer. View Composer requires this account to join linked-clone desktops to your Active Directory domain.

The user account should not be a View administrative account. Give the account the minimum privileges that it requires to create and remove computer objects in a specified Active Directory container. For example, the account does not require domain administrator privileges.

For information about the required privileges, see the View Installation document.

View Connection Server

When you install View, you can specify a specific domain user, the local Administrators group, or a specific domain user group as View administrators. We recommend creating a dedicated domain user group of View administrators. The default is the currently logged in domain user.

In View Administrator, you can use View Configuration > Administrators to change the list of View administrators.

See the View Administration document for information about the privileges that are required.

Table 2. View Database Accounts

View Component

Required Accounts

View Composer database

An SQL Server or Oracle database stores View Composer data. You create an administrative account for the database that you can associate with the View Composer user account.

For information about setting up a View Composer database, see the View Installation document.

Event database used by View Connection Server

An SQL Server or Oracle database stores View event data. You create an administrative account for the database that View Administrator can use to access the event data.

For information about setting up a View Composer database, see the View Installation document.

To reduce the risk of security vulnerabilities, take the following actions:

  • Configure View databases on servers that are separate from other database servers that your organization uses.

  • Do not allow a single user account to access multiple databases.

  • Configure separate accounts for access to the View Composer and event databases.