6.0

The Highest column on the Product Licensing and Usage page displays the highest number of concurrent
desktop sessions and remote application users since your View deployment was first configured or since the
Reset Highest setting was last selected.
An administrator with the Manage Global Configuration and Policies privilege can select the Reset
Highest setting. To restrict access to the Reset Highest setting, give this privilege to designated
administrators only.
Procedure
1 In View Administrator, select View Configuration > Product Licensing and Usage.
2 (Optional) In the Usage pane, select Reset Highest.
The highest historical number of concurrent connections is reset to the current number.
Update General User Information from Active Directory
You can update View with the current user information that is stored in Active Directory. This feature
updates the name, phone, email, user name, and default Windows domain of View users. The trusted
external domains are also updated.
Use this feature if you modify the list of trusted external domains in Active Directory, especially if the
altered trust relationships between domains affect user permissions in View.
This feature scans Active Directory for the latest user information and refreshes the View configuration.
You can also use the vdmadmin command to update user and domain information. See “Updating Foreign
Security Principals Using the -F Option,” on page 204.
Prerequisites
Verify that you can log in to View Administrator as an administrator with the Manage Global
Configuration and Policies privilege.
Procedure
1 In View Administrator, click Users and Groups.
2 Choose whether to update information for all users or an individual user.
Option Action
For all users
Click Update General User Information.
Updating all users and groups can take a long time.
For an individual user
a Click the user name to update.
b Click Update General User Information.
Migrate View Composer to Another Machine
In some situations, you might need to migrate a VMware Horizon View Composer service to a new
Windows Server virtual or physical machine. For example, you might migrate View Composer and
vCenter Server to a new ESXi host or cluster to expand your View deployment. In addition, View Composer
and vCenter Server do not have to be installed on the same Windows Server machine.
You can migrate View Composer from the vCenter Server machine to a standalone machine or from a
standalone machine to the vCenter Server machine.
n
Guidelines for Migrating View Composer on page 98
The steps you take to migrate the VMware Horizon View Composer service depend on whether you
intend to preserve existing linked-clone virtual machines.
Chapter 6 Maintaining View Components
VMware, Inc. 97