Before deploying Profile management in a production environment, Citrix recommends using a test environment. You can create this setup on a local machine with the supplied .ini file, but a fully supported and easier means of transferring settings to the domain GPO is based on a local installation and configuration of the ADM file on a device. Test logon and logoff behaviors and make adjustments to the local GPO until satisfactory results are obtained. You can perform tests safely this way if the device is a member of a production OU because local policies are invoked where OU and domain policies do not exist or are not configured. When using local policies, ensure no Profile management GPOs are used anywhere else (for example, in the domain or sites).
In addition, where an administrator does not have access to or control of domain GPOs for the configuration of the Profile management ADM file, local GPOs can be used as a long-term solution. However, this introduces complexities into the environment, such as ensuring that the Profile management ADM file is installed and correctly configured on each device and the inability of domain users to maintain settings when accessing multiple devices.
If you are testing on Windows 2008 domain controllers, consider using a Windows Management Instrumentation (WMI) filter to temporarily restrict your configuration to just one machine in an OU.
Minimizing differences in the end user experience when accessing resources from various devices is the ultimate goal when implementing a profile solution. Before Profile management, the contents of users' registry and files might vary depending on the physical device, profile configuration, and operating system. For this reason, Profile management should be configured to address the differences between system installations on computers the users will roam between.
Users may access applications from different operating systems, and the variation between them may create conflicting settings within a single user profile. You should understand the differences between Version 1 and Version 2 profiles and how they affect your deployment, since the variations are key to any profile solution. For more information on Version 1 and Version 2 profiles, see About profiles.