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

Cloud Cache

PreviousBest practicesNextAdvanced logging

Last updated 9 months ago

Cloud Cache is a technology that allows FSLogix Profile Container data to be stored in multiple locations at once, including traditional on-premises SMB shares and public cloud storage providers, and to enable real time, 'active-active' redundancy for Profile Container. Cloud Cache also uses a local cache of the profile disk to service all reads from a redirected profile after the first read. Cloud Cache can protect users from short-term loss of connectivity to remote profile containers. When using Cloud Cache, CCDLocations replaces VHDLocations. CCDLocations and VHDLocations cannot be used at the same time. Note that storing profiles in multiple locations at once generates more Azure consumption. Azure Blob storage specifically can be expensive in certain use cases. In general, always use the to calculate Azure consumption costs up front.

Pros:

  • Seamless failover should the loss of a single storage location occur.

  • Real-time, active-active redundancy for Profile Container .

  • Native cloud storage such as Azure Blob, can be utilized.

  • Useful if you have latency issues between the location of storage and location of workloads.

Cons:

  • Logon and logoff delays that impact the user experience. This delay is variable based on many factors such as the location of the container in relation to the location of workloads.

  • A less mature solution.

  • I/O capabilities must be considered as it affects user experience. See best practices for Cloud Cache below.

Parallels RAS allows you to configure Cloud Cache from within Parallels RAS Console.

To configure Cloud Cache:

  1. Open the User profile tab.

  2. Click Configure general settings and select the Cloud Cache tab.

From here you can configure all advanced settings related to Cloud Cache.

Azure calculator