Profile Management

Plan your deployment

June 9, 2020

Contributed by:

B C

To plan a Profile Management deployment, you decide on a set of policy settings that together form a configuration that is suitable for your environment and users. The automatic configuration feature simplifies some of this decision-making for Citrix Virtual Desktops deployments. As a guide to carrying out this important task on any deployment, see Decide on a configuration.

Having decided on a configuration, and reviewed and tested it, a typical deployment then consists of:

Creating the user store
Installing Profile Management
Enabling Profile Management

Plan a pilot study with the .ini file

The following information is intended to assist you using the Profile Management .ini file during a pilot study or evaluation.

Important: If you intend to use the .ini file (UPMPolicyDefaults_all.ini) for evaluation purposes, rename the file before you switch to using Group Policy (GP) in a production environment. For example, rename the file to UPMPolicyDefaults_all_old.ini. Renaming the file allows you to be certain that only production settings are applied, and that no settings you specified during your evaluation are used.

If the file is not renamed, Profile Management examines it for any settings not configured in Group Policy and adopts any non-default settings it finds. So, to eliminate the risk of unwanted settings being introduced, configure all settings you want to use in your production environment using Group Policy, not the .ini file.

The .ini file contains the same policies as the .adm and .admx files, but the policies have different names. If you are familiar with the names in GP and are planning a pilot study with the .ini file, compare the names using the tables in Profile Management policies.

For more information on .ini file deployments, see Upgrade Profile Management and Test Profile Management with a local GPO.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Plan your deployment

June 9, 2020

Contributed by:

B C

June 9, 2020

Contributed by:

B C

Plan your deployment

Plan a pilot study with the .ini file

In this article