Write a commentFor years, there was an unwritten rule in the EUC community: "If you want it easy, use FSLogix. If you want pain, use Citrix UPM." FSLogix was the default choice - install agent, set path, done. Citrix UPM, on the other hand, felt like a relic from the 2000s: tons of policies - includes, excludes, mirror files, sync files, default excludes... Admins got lost in the endless lists and frustrated by the complexity.
But with current releases (CVAD 2402 LTSR and newer), the tables have turned. Citrix hasn't just caught up technologically (VHDX containers, disk compaction, filesystem filters); it now solves architectural problems where FSLogix hits a wall.
It's no longer about "Either/Or". It's about the question: Why use an external tool when the integrated engine can do more?
1. The Stalemate: Setup and "Ease of Use"
The main argument for FSLogix was always its simplicity. With Citrix UPM, you had to click through dozens of policies in Web Studio. Technically, the UPM agent (part of the VDA) is already installed - we just have to "switch it on.",The problem was purely operational: The UPM policies in Web Studio are cluttered. To eliminate this downside and make UPM just as "One-Click-Ready" as FSLogix, I developed a PowerShell script.
It does exactly what we need:
- Enables UPM services
- Configures the VHDX Container
- Sets a clean, modern exclusion list (Teams, Browser Caches, etc.)
This takes the "FSLogix is faster to set up" argument off the table. The script handles this in seconds.
2. The Advantage: Where UPM wins
Now that setup is equal, let's look at the features. Monitoring and Disk Compaction are handled well by both solutions today. However, UPM shows its strength in areas that determine stability in enterprise environments - areas where FSLogix often requires manual tuning or risky workarounds.
A. In-Session Reattachment (Auto-Reconnect)
Every admin knows this scenario: A short glitch in the storage network.
- FSLogix: It loses the handle to the VHDX. While it has retry mechanisms, the session often ends up in an undefined "zombie" state or applications crash because the disk is inaccessible for too long.
- Citrix UPM: With the "Automatically reattach VHDX disks" feature, the UPM service actively monitors the container status. If the connection drops, UPM aggressively attempts to re-mount the disk and renew the handle in the background. While this doesn't save every inflight transaction, it often prevents the entire session from becoming unusable, saving the user from a forced relogon.
B. Zombie Sessions & The "RW Fallback" Dilemma
A session terminates unexpectedly (network cut, process crash), but the OS/File Server still holds the SMB lock on the VHDX container. The user tries to log on to a new server.
- FSLogix: The user hits a wall. If they land on a new server, the logon fails ("File in use"). If you enable "RW Fallback" to bypass this, the user gets in with a Read-Only/Differencing disk. The consequence: They work, save data, log off - and everything is permanently discarded, because FSLogix cannot merge changes back into a locked container.
- Citrix UPM: Handles locked containers gracefully if "Multi-session support for profile containers" is enabled. Instead of just giving up or discarding data, UPM provisions a separate multi-session VHDX for the new session. The user gets full Read/Write access. The crucial difference: UPM actively tracks these changes and synchronizes them back into the main profile once the lock is released or the session ends. No data loss.
C. Store Migration "On the Fly"
A file server migration is coming up.
- FSLogix: This often means downtime on weekends and Robocopy scripts. Paths must be hard-coded in GPOs or the Registry.
- Citrix UPM: The policy "Migrate user store" allows you to change the path during live operations. At the user's next logon, UPM automatically migrates the container from the old to the new location—transparently for the user and without manual copying by the admin.
D. Multi-Session Support (True Concurrent Access)
FSLogix supports multi-session (e.g., Mode 3), but handling simultaneous write access is often complex. Citrix UPM was natively developed for multi-session scenarios (Virtual Apps / Server OS). The logic for how changes from multiple simultaneous sessions (e.g., a Desktop and a published App) are written back to the profile ("Last Writer Wins" or file-level merging) is much more granular in UPM.
💡 Pro-Tip: Local Caching as "Network Insurance"
We all know the drill: Users report session freezes, but the Network Team says, "Our dashboards are green." You are stuck in a blame game while the user suffers. By enabling "Enable local caching for profile containers" in UPM, you can bypass this discussion.
- The Strategy: The profile disk is fully cached on the VDA. If the storage or network glitches, the user doesn't even notice.
- The Trade-off: In non-persistent environments, the logon takes a few seconds longer (cache hydration). But trading 5 seconds of logon time for a session that survives a file server outage is a deal every admin should consider if the network isn't 100% reliable.
3. Automation: Infrastructure as Code
FSLogix usually requires GPOs and central XML files on a share for control. This creates external dependencies outside the Citrix Site.
Citrix UPM, however, resides directly in the Site Database. The configuration is bound to the Delivery Group and can be controlled entirely via PowerShell on the Controller. The result: No waiting for GPO replication, no maintaining XML files. One script, done.
Conclusion & Download
FSLogix is a powerful tool. But in a pure Citrix environment, there is hardly a technical reason today to maintain an external solution when the integrated stack brings native features like I/O-based Reattachment, Live Migration, and reliable Session Handling. With modern PowerShell integration, UPM is just as fast to set up - and keeps the infrastructure leaner because everything stays within the Citrix stack.
You can find the complete script for automatically creating the policy on GitHub:
👉 GitHub: Create-ModernUPM-Policy.ps1
