Product Documentation

Other considerations

Dec 04, 2012

As configured in this case study, Profile management does not use the settings from NewDomain to initialize the cross-platform settings store. Only settings from OldDomain can be used to initialize the store. This is acceptable until NewDomain contains more than one type of profile (such as Windows 7 32-bit and Windows 7 64-bit). Alternatively, users from NewDomain may need to access resources in OldDomain. In these cases, you must enable the policy Source for creating cross-platform settings on further types of machine appropriately.

Caution: If Source for creating cross-platform settings is set incorrectly, it is entirely possible that a new profile will obliterate an existing profile with many accumulated and treasured settings. To avoid this, Citrix recommends that this policy is set on only one platform type at a time. This is generally the older (more mature) platform, where settings that users most likely want to keep have accumulated.

In this case study, separate domains are used to illustrate a number of points. Additionally, the cross-platform settings feature can manage the roaming of settings between two OUs, or even between machines of different types in a single OU. In this case, you might have to set the policy Source for creating cross-platform settings differently for the different machine types. This can be achieved in a number of ways:

  • Use the setting CPMigrationsFromBaseProfileToCPStore in the .ini file to set the policy differently on each machine type. Do not set the policy Source for creating cross-platform settings.
  • Use Windows Management Instrumentation (WMI) filtering to manage different GPOs on the same OU. You can configure the common settings in a GPO that applies to all machines in the OU, but only add the policy Source for creating cross-platform settings to additional GPOs and filter using a WMI query.