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 will likely
be migrating existing local profiles rather than starting from scratch.
If you decide to
migrate existing profiles, configure the
of existing profiles and
profile conflict handling policies.
diagram illustrates how to configure these policies based on your answer to
If you decide to
create an entirely new set of profiles, consider creating a template for this
purpose using the
profile policy. For information, see
To specify a template or mandatory profile.
If you do not create a template, Profile management will give users the default
Windows profile, for example, from a VDI-in-a-Box master image. If no template
is required, leave this policy disabled.
profile policy is similar to the
Path to user
store policy because it specifies the location of a profile that can be
used as the basis for creating a new user's profile when they first log 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 for this, you should perform tasks such as identifying the
applications that users will access; configuring the registry states,
shortcuts, and desktop settings in the profile accordingly; setting permissions
on profile folders; and modifying users' logon scripts.
Note: When selecting
mandatory profiles in XenDesktop deployments, Citrix recommends using Desktop
Studio rather than the Profile management .adm or .admx file.