The first stage in planning a Profile Management deployment is to 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 XenDesktop 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:
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.
If you intend to use the .ini file (UPMPolicyDefaults_all.ini) for evaluation purposes, rename the file (for example, to UPMPolicyDefaults_all_old.ini) before you switch to using Group Policy (GP) in a production environment. 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.