Other considerations 编辑

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. It 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 might 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 possible that a new profile obliterates an existing profile with many accumulated and treasured settings. So we recommend that this policy is set on only one platform type at a time. This platform 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 some points. Also, 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 setup can be achieved in several 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 you add only the policy Source for creating cross-platform settings to additional GPOs and filter using a WMI query.