We are currently setting a a new VDI pool to migrate from VMWare persona management to VMWare UEM. However, looking around and reading about FSLogix, recently acquired by MS and available to all with RDS/VDI CALs, also looks very promising.
However, at first sight, I would say that if using FSLogix profile containers eliminates the need for VMWare UEM and will even be doing a better job in maintaining Office cache & seach index? That is based on my readings, no real life experiences yet! Is anyone willing to share their experiences with either solutions or even using both?
Thanks a lot!
Check out that thread. Lots of good info in there from people's experiences.
We gave FSLogix a look over, but found it did not play well with UEM. We were getting some weird shortcuts and login times were definitely worse. We ended up going with writable volumes and UEM for our stuff.
FSlogix containers, for the most part, are like app volume writeable volumes, hich there are reasons to use them in conjunction UEM beyond just managing the profile. The best thing I can think of is at least my experience with the user profile if you lose the container due to corruption or something similar, the user needs to start over. UEM manages a lot of whats in a profile, but it does more than just handle the profile. this is like saying why drive a car when you have a bike.
@sjesse, I understand what you're saying, which raises 2 other important things:
1) Container corruption: I know it used to happen regularly several years ago when MS started using UPD on terminal server, but is this still the case? Does it still happen often that those containers got corrupted? Real life experiences are very welcome here 🙂
2) The primary reason for us to use UEM would be to get rid of the huge roaming profiles (and their perfomance problems). When using both profile containers and UEM, I'll just add additional overhead and need more storage, cause the profile is there already, so why bother saving each application's settings again somewhere else? (Yes, UEM can do more than just saving settings, but for us that's not the main use case). UEM combined with Office Containers on the other hand seems a better way in my opinion. Unless someone can confirm me that you can save storage space in your container by combining the container with UEM?
I've used UEM in a non persistent environment just to capture user settings. The the two big issues I have with UEM is 1. Long login times and two having to ensure that the application you configure captures the settings correctly which can become a nightmare to maintain. Using FSLogix, I see that the user login is faster and I no longer have to worry about maintaining a catalog of application's configuration files. The only drawback is that I have to maintain the growth of the VD files which a script can handle. So far, I'm thinking of dumping UEM completely and using FSLogix.
I agree with you on both points, I just put in FSLogix today and I am astounded by the Login times, they are so low; so I am gonna slowly roll this out to my user base.
Love the avatar btw!