Migrate profiles? New profiles?
You can take advantage of a Profile Management deployment to refresh your organization’s profiles, initially using a small, customized profile, and rigidly controlling additions to it. Alternatively, you may need to migrate existing profiles into the Profile Management environment and preserve the personalizations that have built up over many years. With Citrix VDI-in-a-Box deployments, you might migrate existing local profiles rather than starting from scratch.
If you decide to migrate existing profiles, configure the Migration of existing profiles and Local profile conflict handling policies.
The following diagram illustrates how to configure these policies based on your answer to this question.
Policy: Template profile
If you decide to create an entirely new set of profiles, consider creating a template for this purpose using the Template profile policy. For information, see Specify a template or mandatory profile. If you do not create a template, Profile Management gives users the default Windows profile, for example, from a VDI-in-a-Box master image. If no template is required, leave this policy disabled.
The Template profile policy is similar to the Path to user store policy. This policy specifies the location of a profile that can be used as the basis for creating a user’s profile when the user first logs on to a computer managed by Profile Management.
You can optionally use the template as a Citrix mandatory profile for all logons. As part of your planning, you must perform tasks such as identifying the applications that users access. You must configure the registry states, shortcuts, and desktop settings in the profile accordingly. You must set permissions on profile folders and modify users’ logon scripts.
Note: When selecting mandatory profiles in Citrix Virtual Desktops deployments, Citrix recommends using Desktop Studio rather than the Profile Management .adm or .admx file.