Use Citrix UPM like FSLogix - only better!

Jor years, there was an unwritten rule in the EUC community: „If you want it to be simple, use FSLogix. If you want pain, use Citrix UPM.“
FSLogix was the standard - install agent, set path, run. 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 endless lists and were frustrated by the complexity.

But with the latest releases (CVAD 2402 LTSR and newer), the tide has turned. Citrix has not only caught up technologically (VHDX containers, disk compaction, file system filters), but has also now solves architectural problems where FSLogix reaches its limits. It is no longer a question of „either/or“. The question is: Why use an external tool when the integrated engine can do more?

1. the tie: Setup and „Ease of Use“

The main argument in favor of FSLogix was always the simple setup. With Citrix UPM, you had to click through dozens of guidelines in Web Studio.
Technically, however, the UPM agent (part of the VDA) is already installed - we just have to „switch it on“.

The problem so far has been purely operational: the UPM guidelines in Web Studio are confusing. To eliminate this disadvantage and make UPM just as „one-click-ready“ as FSLogix, I developed a PowerShell script.

It does exactly what we need it to do:

• Activation of UPM services
• Configuration of the VHDX container (incl. the mandatory JSON wildcard routing)
• A clean, modern exclusion list (teams, browser caches, etc.)

This eliminates the „FSLogix is quicker to set up“ argument. The script does this in seconds.

2. the lead: where UPM wins

If the setup is now equivalent, let's look at the features. Both solutions are now good at monitoring and disk compaction. But UPM shows strengths in areas that determine stability in the enterprise environment - areas where FSLogix often requires manual tuning or risky workarounds.

A. In-Session Reattachment (Auto-Reconnect)

Every admin knows the scenario: a brief wobble in the storage network.

• FSLogix: Loses the handle to the VHDX. Although there are retry mechanisms, the session often ends in an undefined „zombie“ state or applications crash because the disk is inaccessible for too long.
• Citrix UPMWith the „Automatically reattach VHDX disks“ function, the UPM service actively monitors the container status. If the connection is interrupted, UPM aggressively attempts to remount the disk and renew the handle in the background. Although this does not save every running transaction, it often prevents the entire session from becoming unusable and saves the user from being forced to log on again.

B. Zombie Sessions & The „RW-Fallback“ Dilemma

A session is ended unexpectedly (network cut, process crash), but the operating system/file server continues to hold the SMB lock on the VHDX container. The user tries to log on to a new server.

• FSLogixThe user runs into a wall. If he lands on a new server, the login fails („File in use“). If you activate the „RW fallback“ to bypass this, the user is allowed in, but only receives a differencing disk (read-only). The consequence: It works, saves data, logs off - and everything is irrevocably discarded, as FSLogix cannot write the changes back to a locked container.
• Citrix UPMHandles locked containers gracefully when „Multi-session support for profile containers“ is enabled. Instead of simply giving up or discarding data, UPM provides a separate multi-session VHDX for the new session. The user receives full read/write access. The key difference: UPM actively tracks these changes and synchronizes them back into the main profile as soon as the lock is released or the session ends. No loss of data.

C. Store Migration „On the Fly“

A file server move is pending.

• FSLogix: Downtimes at the weekend and Robocopy scripts are often necessary here. The paths must be hard-coded in GPOs or the registry.
• Citrix UPMThe „Migrate profile storage“ policy allows the path to be changed during operation. The next time the user logs on, UPM automatically migrates the container from the old to the new storage 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 the handling of simultaneous write accesses is often complex.
Citrix UPM was developed natively for multi-session scenarios (Virtual Apps / Server OS). The logic of how changes from several simultaneous sessions (e.g. desktop and published app) are written back to the profile („Last Writer Wins“ or merging at file level) can be controlled much more granularly in UPM.

? Pro tip: Local caching as „network insurance“

We know the game: users report frozen sessions, but the network team says: „Our dashboards are green.“ You're stuck in the blame game while the user suffers.
By activating „Activate local caching for profile containers“ in the UPM, this discussion can be avoided.

• The strategyThe profile disk is fully cached on the VDA. If the storage or the network is briefly interrupted, the user will not notice anything.
• The trade-offIn non-persistent environments, the login takes a few seconds longer (cache hydration). But trading 5 seconds of login time for a session that survives a file server outage is a deal every admin should consider if the network is not 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, on the other hand, is located directly in the site database. The configuration is bound to the delivery group and can be fully controlled via PowerShell on the controller.
The result: No need to wait for GPO replication, no need to maintain XML files. One script, done.

Conclusion & Download
FSLogix is a powerful tool. But in a pure Citrix environment today, there is hardly any technical reason to maintain an external solution when the integrated stack offers native features such as auto-reattachment, live migration and reliable session handling. With modern PowerShell integration, UPM is just as quick to set up - and keeps the infrastructure leaner because everything remains in the Citrix stack.

You can find the complete script for the automatic creation of the policy here on GitHub:

? GitHub: Create-ModernUPM-Policy.ps1