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. Overview

User Profile Disk (UPD)

As the successor of Roaming User Profiles, UPD stores user profiles in a VHD/VHDX container. This container mounts on a machine upon the user logging in. Microsoft is no longer actively developing UPD and as a result it is considered a legacy technology. Management of UPD in Parallels RAS is only available when upgrading from previous versions of Parallels RAS and is no longer available in new deployments of Parallels RAS.

The limitations of this technology are:

  • UDP cannot be used on multiple devices concurrently. Once VHD(X) is mounted for the user, it cannot be mounted on a different device if the user still has an active session on the given session host. If a user connects to another session host while the UPD is already in use, a temporary profile is created.

  • UPD requires a configuration at the level of RDS collections. Should there be a user with the ability to log on to several collections, a separate profile will be used for each collection. In Parallels RAS this applies to RDSH host pool. Whenever a user connects to two servers that belong to different RDSH host pool, the second RDP session uses a temporary profile.

  • Windows deletes the search index for a user profile when the UPD disconnects at logoff. The search index is recreated upon every login. This means that Windows search is not usable in non-persistent VDI environments. This issue also extends to Outlook search capabilities on RD Session Hosts.

  • UPD is supported on RD Session Hosts and Windows client systems in VDI. Physical Windows client machines are not supported.

PreviousRoaming User ProfilesNextFSLogix Profile Containers

Last updated 8 months ago