Product documentation
Profile Management
Current Release 2507 LTSR 2411 2407 2402 LTSR 2311 2308 2305 2303 2212 2209 2206 2203 LTSR 1912 LTSR 7.15
View PDF

Choose between file-based and container-based profiles

July 24, 2025
Contributed by: 
C

Citrix Profile Management (CPM) supports two profile types: file-based and container-based. Choosing the right type helps improve the user experience, reduce storage requirements, and simplify profile management. You can also use both types together to support different user cases.

Understand the two profile types

Before deciding which profiles type to use, it’s important to understand how each one works and what makes them suitable for different environments.

  • File-based profiles

    File-based profiles store user data and settings in individual files and folders on the profile store. At logon, CPM copies the profile to the local session (unless profile streaming is enabled), and updates the profile in the store at logoff.

    This lightweight, flexible method is ideal when storage capacity or network performance is a concern.

  • Container-based profiles

    Container-based profiles store the user profile in a virtual hard disk (VHDX) file on the profile store. The container is mounted at logon and updates are written directly to the profile store throughout the session.

    This approach simplifies profile inclusion and exclusion logic and is often preferred when working with modern apps such as OneDrive or UWP apps.

When to use file-based profiles

Choose file-based profiles if:

  • Storage space is limited. File-based profiles use much less storage space than container-based profiles. By default, the CPM container has 50 GB storage capacity per user.
  • Profiles are small or simple. File-based profiles work well if users typically have under 1 GB of profile data and don’t require large application caches or personalization.
  • You want to reduce network dependency. File-based profiles copy data to the VDA at logon (if profile streaming is disabled), so network interruptions during sessions have no impact. You might also want to reduce network dependency to avoid delays if troubleshooting requires help from the networking team.
  • You’re satisfied with your existing setup. If you’re already using file-based profiles successfully, you might not need to switch—unless new application requirements arise.

When to use container-based profiles

Choose container-based profiles if:

  • You need to support the OneDrive sync app. File-based profiles don’t support OneDrive sync. Use container-based profiles or enable the OneDrive container for this portion of the profile while keeping the rest of the profile file-based.

    Note:

    Microsoft doesn’t support multiple concurrent OneDrive sync sessions using the same container. For details, see this Microsoft article. If you need multiple concurrent sessions with the sync app, use a separate container for each session or access OneDrive through a browser in secondary sessions.

  • You want simpler profile configuration. Container-based profiles don’t require granular include and exclude rules. All profile data is stored in a VHDX file, reducing admin effort but increasing storage needs.

  • You have robust storage and networking. Container-based profiles rely on a stable connection between the VDA and profile store for real-time reads and writes.

When to use a hybrid approach

You can combine file-based profiles with container-based features to optimize both performance and storage. This approach is helpful when only parts of the profile require the container-based profiles.

Citrix Profile Management supports the following container features:

  • Search index roaming for Outlook: Stores the Microsoft Outlook .OST file and search index in a separate VHDX.

  • OneDrive container: Stores OneDrive data in a separate VHDX file to support OneDrive sync.

  • UWP app load acceleration: Stores Universal Windows Platform (UWP) apps in a VHDX for faster load times.

  • Accelerate folder mirroring: Stores mirrored folders (such as browser cookies) in a VHDX to maintain data integrity.

    Note:

    Folder mirroring is used when an entire profile subfolder must be kept in sync as a single unit to maintain data integrity—for example, when files in the folder reference each other. A common use case is browser cookies, where an index file points to individual cookie files in the same folder.

Summary

There’s no single best profile type. Choose the one that best fits your user personas, application requirements, and IT resources. If you need help deciding, contact your Citrix team for guidance.

Choose between file-based and container-based profiles
July 24, 2025
Contributed by: 
C
July 24, 2025
Contributed by: 
C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.