The aim of a pilot
deployment is to be able to demonstrate a solution quickly and reliably, and an
important goal may be to reduce the number of components in the pilot. For
Profile management, two components are the user store and the selection of
users whose profiles are processed.
to user store
Setting up a user
store for Citrix user profiles is exactly like setting up a profile store for
Windows roaming profiles.
For a pilot
deployment, you can often ignore these considerations. The default value for
user store policy is the Windows folder in the user's home
directory. This works well for a single-platform pilot so long as only one
operating system (and therefore only one profile version) is deployed. For
information on profile versions, see
This option assumes that enough storage is available in users' home directories
and that no file-server quotas are applied; Citrix does not recommend the use
of file-server quotas with profiles. The reasons for this are given in
Share Citrix user profiles on multiple file servers.
For a production
deployment, you must carefully consider security, load balancing, high
availability, and disaster recovery. Follow the recommendations in these topics
for creating and configuring the user store:
Processed groups, Excluded groups
The complexity of
production deployments means that you may need to phase the rollout of Profile
management, rather than release it to all users at the same time. You may also
need to tell users that they will receive different profile experiences when
connecting to different resources while the deployment is in the process of
being rolled out.
reasons, Profile management is licensed by an End-User License Agreement (EULA)
not built-in license checking. You may choose to manage license allocation by
assigning users to an Active Directory (AD) user group or using an existing AD
group if a suitable one exists.
deployments, use of Profile management is usually restricted by invitation to a
small group of users, possibly from several departments, where no single,
representative AD group can be used. In this case, leave the
groups and Excluded
groups policies unconfigured; Profile Management performs no checking on
group membership and all users are processed.
information on these policies, see
To define which groups' profiles are processed.
Important: In all cases you must ensure that the number of users processed
by Profile management does not exceed the limits set by the relevant EULA.