Designing and Implementing Environment Manager Personalization

The following points are recommendations for the design and implementation of Environment Manager User Personalization.

Install the Personalization Database and Personalization Server on separate devices (physical or virtual).
Where possible, install the Personalization Database with High Availability in mind. Typically for this, clustering of the Microsoft SQL Server is recommended.
When required, Personalization Servers will support Network Load Balancing being placed in front of the servers.
For multiple Environment Manager sites or data centers, it is recommended that Personalization Servers and Databases are installed on these sites and local clients pointed to their local Personalization Server and Databases. This reduces performance issues across WAN links.

Setting Up a Personalization Configuration

The following steps outline how to create a basic configuration to manage and migrate existing user data into the Personalization database.

Create the Personalization Groups required for your organization and add membership rules to represent your users.

Enable Application Data Collection to passively gather registry and folder usage data for the applications your users have run.

It is recommended that Application Data Collection is disabled when no longer required.

Use the collected data to create managed Application Groups to manage the applications within your organization.

Add Windows Settings Groups to manage the settings users apply to their endpoints.

Use Profile Migration to import data from existing user profiles.

This page refers to an older version of the product.
View the current version of the User Help.