FSLogix Containers Best Practices
ProductsSupportPartnersDocumentation
  • Overview
    • Roaming User Profiles
    • User Profile Disk (UPD)
    • FSLogix Profile Containers
    • Office Container
    • Concurrent connections and multiple connections
    • Multiple connections
  • Prerequisites
    • Eligibility requirements
    • Required storage permissions
    • FSLogix Profile Containers on Azure Files
    • FSLogix Profile containers on Azure Page Blobs
    • Configuration requirements
    • FSLogix antivirus exclusions
  • Configuring FSLogix via Parallels RAS
    • New FSLogix deployment via Parallels RAS
      • Rebooting a host
    • Configure managing existing profiles by Parallels RAS
      • Prerequisites for existing FSLogix configuration
      • Replicate GPO and FSLogix configuration
    • Migration from UPD and Roaming profiles
    • Best practices
      • Cloud Cache
      • Advanced logging
      • SMB locations
      • Moving to Cloud Cache from traditional FSLogix Profile Container
      • Using Cloud Cache in persistent physical environments
    • FSLogix Containers backup
      • SMB locations
      • Cloud Cache
  • References
Powered by GitBook

Social media

  • Facebook
  • Twitter
  • LinkedIn
  • YouTube

Other Resources

  • Feedback

© 2025 Parallels International GmbH. All rights reserved.

On this page
Export as PDF
  1. Configuring FSLogix via Parallels RAS
  2. Best practices

Moving to Cloud Cache from traditional FSLogix Profile Container

Microsoft allows moving current Profile Container implementations to Cloud Cache. To start using Cloud Cache, replace the VHDLocations setting with CCDLocations. CCDLocations and VHDLocations may not be used in the same implementation simultaneously.

A Cloud Cache Provider contains both the profile container and associated metadata, while a traditional VHDLocation contains only the profile container. If Cloud Cache points to profile containers without metadata, the metadata will be created. When the metadata is added, the Profile Container location is converted to a Cloud Cache provider.

If a user has profile containers in more than one CCDLocation, the profile container listed first in CCDLocations will be updated to a Cloud Cache provider. All other profile containers in the same CCDLocations string will be deleted and replaced from the first Cloud Cache Provider.

There's no mechanism to merge multiple profile containers into a single profile.

PreviousSMB locationsNextUsing Cloud Cache in persistent physical environments

Last updated 9 months ago