- The Rise and Stagnation of FSLogix
- Mapping the Container Capability between CPM and FSLogix
- References and Documentation
A few years back, I put together my thoughts on Citrix Profile Management (CPM) and FSLogix Profiles and where they make sense. That post is over two years old now, and the world moved on significantly. I have updated the old post with some commentary around the changes, but felt it was nice to keep this historical data.
This post is designed as a brief point in time thought provoker on where I see the same two technology sets and their current state of play.
Again, as per last time, this article is Citrix focused. If you don’t have access to CPM technology, then as you were soldier.
The Rise and Stagnation of FSLogix
FSLogix came to the table with a bang. Office Containers, Profile Containers and AppMasking. All capabilities that were ground-breaking and changed how we could deliver solutions in the EUC space. The Office Container was a huge enabler for customers moving to M365, whereas in reality, a Profile Container wasn’t a new concept, FSLogix just did a fantastic job at executing on it, vs Microsoft’s own User Profile Disk in RDSH.
FSLogix was led by some very cool and massively switched on humans. The company was cool, the technology was great, the trajectory was huge, and the people were fun. Good times ahead. Until they were acquired by Microsoft.
At first things seemed great. FSLogix for everyone effectively. What could go wrong? Read the historical rants I have on exactly what could, and did go wrong with this model. A default lean towards Containers for everything, outages everywhere due to the wrong solutions being implemented in the wrong context, laziness aplenty and a lack of understanding on what was actually being introduced and more importantly, why it was being introduced.
At the same time as this was going, Citrix Profile Management was somewhat forgotten about and pushed to the side for many organisations and consultants. A sad reality given its history, but also somewhat understandable given how much you did_not_have_to_do with FSLogix Containers. Luckily for us, Citrix never appeared to be worried, and kept building, building, building.
The age of file based profiles was dead. Was it?
Citrix CPM is dead, everyone is going to FSLogix. Hrm was it?
FSLogix is free. Within reason sure. But there was always a cost somewhere else.
Without this being a history lesson, two key things happened, or more accurately, continued to happen over the last few years.
- Microsoft did as aptly put by my friend Oz, purchased FSLogix, and “After they acquired it, it was told to sit in a corner and shut up”. Sensational. It’s not like the product got bad; it just didn’t progress. Support was/is horrific, bugs aplenty (but to be fair, it’s software and there are bugs everywhere, the challenge is the time to dignify and fix it), and it appears as if Microsoft’s own support had no real concept of what this “FXLogix” thing was. That is not a typo, that is the common wording used to describe FSLogix by MS support.
- Citrix continued to build CPM. They obviously took a lot of the learnings and ideas from FSLogix, but they built, they supported, they innovated, and they executed continually on new features. Throw them an idea, they built it. File based, Container based, selective use of either, resilience, replication, compaction, GPO processing tricks, the list goes on.
For where we stand now, I struggle to find a reason for any Citrix customer to not use CPM capability, be it Container or Files, in their deployments. Outside of the effort to change, I don’t think (and am happy to be wrong) that FSLogix Containers offer anything that Citrix technology does not.
It is absolutely no surprise, that we have reached a pivot point where the conversations are now back to a CPM lead. Just look at the progression of the solution on a quarterly release cadence.
Mapping the Container Capability between CPM and FSLogix
Whilst Citrix have done a great job at building their capability, they have not done a great job of advertising what they have built. Below is a quick high-level mapping of the cool stuff between technologies where I think it’s relevant:
|Profile Disk Modes||Direct, Try for read write, fallback to RO, RW and RO Profile Modes||RW by default. Excusive Access if enabled ✅|
|Multi Location Resiliency||Cloud Cache||Replicate User Stores and Local Caching for Containers ✅|
|Office Data||ODFC Container||OneDrive Container, Outlook Search Experience ✅|
|UWP||InstallAppXPackages||UWP App Roaming ✅|
|Space Reclamation||VHD Compaction||Compaction ✅|
|Multi Access||Mode 3 Profile Disks with limitations ❌||Multi Session write-back ✅|
|Selective Containerization||Nil ❌||Large File Handling ✅|
|Async GPO Processing||Reverted ❌||Async Processing ✅|
|Auto Expansion||Dynamic Disks||VHD auto-expansion ✅|
As you can see, by my math, there is nothing that FSLogix does, that CPM does not outside of specific Read Only profile disk scenarios.
Note that this is purely related to Container technologies. There is a whole lot more that they bring to the table when you look at file based as well.
References and Documentation
A few handy references hidden away in the Citrix documentation
- A handy list of policies and what applies to container vs files
- A policy version table allowing you to see changes against each version of CPM
- Guidance on improving the logon experience
This write-up is not about down talking FSLogix, but more about raising awareness around the current state of capabilities with CPM, and why it might make more sense. There are so many conversations that we regularly have where people have absolutely no awareness of how fast things are moving in the CPM world, and we still hear misinformation being spread based on concepts from years ago which are simply not true.
Are you going to be in trouble or have a bad experience if you use FSLogix? Absolutely not. It’s a great tool. But if staying supported, having significant innovation and development along with ongoing enhancements is important to you, then CPM is going to look a lot more appealing.