Now that Microsoft has acquired FSLogix, I'd like to start a discussion around using BOTH FSLogix & UEM together.
One of my pain points with UEM is around Microsoft's User-based setups of OneDrive and Teams... These apps are bloating the User Profile and causing delays. And still have limitations.
Those using VMware AppVolumes can work around some of these issues, but going forward it seems Microsoft will be leveraging VHDs as part of the new modern Profiles.
FSLogix adds the following features to the Microsoft portfolio:
Does anyone use FSLogix along with UEM?
If so, what kind of control do you gain/loose with the use of the VHD? With UEM, you get the benefit of exclusions to control the size.
I know the default FSLogix container size is 30GB...just trying to determine what admins are experiencing out there.
FSLogix Licensing Entitlements are planned to be for the following: (not yet official) Looks like it's easy to qualify for...(From Christiaan's Blog)
We're in the same boat with this. We just started a migration to O365 project that is going to require us to use cached exchange mode in our non-persistent setup. We are trying to avoid writables and are currently attempting to test with FSLogix. We are only using the Office containers portion at this point and not anything with the profile container. All we are looking to get from it at the moment is storing of the OST file and being able to roam the search index.
So far, the OST file portion works great. It's immediately available on login and only downloads the newest email just like it should. Everything else is the problem for us. Search only seems to work about 50% of the time. When it doesn't work, it either has to fully rebuild or we get an error saying 'Something went wrong and your search couldn't be completed' will be displayed. In the case of seeing the error, after about 10 seconds, the search will show results.
We are also seeing increased login times, 15-30 seconds, after adding in the FSLogix agent/driver. Our VHD is stored on a file server in the same environment as our desktops and we are fully HCI, so latency is not an issue. We also see where every so often the shortcuts on the desktop will be changed to the default while file at first. A refresh of the desktop or with enough time and they will change back. None of this occurred before FSLogix was installed.
The sales ppl from FSLogix we are talking to aren't much help. They just pretty much say it should just work and have at this point stopped responding to messages. I'm guessing everyone is sitting around waiting for MS to come in and restructure. They originally told us all the changes for them were coming in June so maybe it will get better after that.
We you previously a FSLogix customer? Just wondering how you worked out the licensing...or did you use a trial.
My Microsoft TAM reached out to someone on the Modern Desktop team that stated:
"You are entitled to FSLogix as it will be included in your SKUs. However, it is still being integrated and therefore if you are interested in POC/Piloting it, we will need to have a bridge Cal provided to you."
The increased login times, 15-30 seconds, has me worried. Especially knowing that the FSLogix support Teams are all "up in the air" while being integrated by Microsoft.
It could be a bumpy ride at first.
We are just using a trial for now. We own E3 licensing which will eventually include FSLogix, but until June it technically does not. They said we could get around it with a 0 dollar PO and some fancy paperwork if we had to have it before then, but with how it's working now, I doubt we will go with it.
I met with our Microsoft TAM, and an engineer from FSLogix. Quick Q&A, some Powerpoint slides, and enough licenses to get me by until the official SKUs exist.
Couldn't have been easier.
Now I just need to find the time to set it up in the lab!
I haven't heard from anyone at FSLogix for quite some time now. I'll probably give it another week and then try to talk to our MS rep and see if I can get any traction that way. In the end, some of the problems we were seeing will probably keep us away from it anyway.
I was able to deploy FSLogix profile containers in a test pool with UEM. After modifying all direct flex configs to sync during login and moving the redirected folder config from uem back to gpo, I logged in once and the new vhdx got populated with my profile. This login and all prior were about 1:30 and direct flex launches were slow. After logging off, I set the UEM GPO for my user to read only so that uem would not apply on my next login. The second login was :30 and every thing launches quickly. It seems like there is an opportunity to turn uem back on for the benefit of providing per app backups and or defaults for certain apps that you might exclude in FSLogix so that we can benefit from both solutions concurrently. This is a game changer!
Did you ever get anywhere with this? I'm curious if anyone had the same problems with using UEM and FSLogix together that we did. Most of what I'm seeing is people moving completely to FSLogix profile containers instead of trying just the O365 containers and still using UEM which is what we tried and failed so hard at.
Here’s a new update from Microsoft: No Licenses Required!!
“FSLogix tools aren't licensed independently. Before downloading and using FSLogix, verify that entitlement requirements are met. FSLogix entitlement is described here entitlement and configuration requirements.
The FSLogix software no longer requires license keys.”
I played around with FSLogix - Office Containers (not Profiles) for a couple of days, along with UEM. I figured I'd see if I can enhance all that's wrong with Office 2016/O365 in a non-persistent instant-clone environment.
Quick Summary - FSLogix - Office Containers.
Trust me, the performance of your Office products will make up for the "Bads" that I have listed. I'm just hoping some of you will test this out, and help document how best to use this with UEM as the primary Profile manager. Knowing Microsoft, it will eventually be baked into either Windows 10 or O365 anyways...
Here are my thoughts on how to deploy this solution side by side with UEM.
Note: This is untested. I merely have been doing research on FSLogix and implying my knowledge on how things work in UEM to see how to deploy both of them on the same VM. Take everything I say with a grain of salt
- It looks like to get both UEM and FSLogix to behave well together you will have to configure DireFlex to only export at logoff all items under "Personalization" just to backup user configurations in case of the vhd disk corruption. Or simply disable all the items. You wouldn't want a user to start completely from scratch in case of a disk corruption. However, in theory you should be backing these vhd disks as part of your solution. One could argue why not just restore the vhd from backup and voila. User is back to working in minutes. Picking up exactly where he/she left off at.
- Importing Personalization items at logon could cause some serious issues as the data already exists on the mounted disk and both UEM and FSLogix may end up importing the same data at the same time.
- I would still use UEM for ADMX-base settings deployments.
- I would disable OST policy from UEM "App Volumes"
- I would still utilize the following: Drive mappings, Environment Variables, File Type Associations, Horizon Smart Policies, Logon Tasks, Log off Tasks, Printer Mappings, Privilege Elevation, Triggered Tasks,
- I am sort of undecided about Application Blocking considering FSLogix has a similar module called "App Masking" that seems to be doing the same thing but better. I do not need to block an application if I am already masking it for those who are not entitled to it. I am a little conflicted but I do however still find some good use cases for Application Blocking. Especially for an environment like where I currently worked at. We block applications like mstsc.exe to prevent users from remoting to another workstation and potentially copy and paste PHI documents. I don't believe I should/can mask an application like mstsc.
- I would use Registry Settings with a condition if key value doesn't already exists.
- I would use shortcut with a condition if folder exists and also check "Skip if shortcut already exists."
- I never used the Windows Settings feature. It is the legacy way of doing things.
- I would still use condition sets
I would say all. The reason is that applications normally store user's settings in registry or %AppData% and in this case the FsLogix volumes will stores the whole user's profile so there really any needs to use personalization for any apps.
Old thread but I was wondering the same thing, using UEM/DEM for application blocking as I don't know of anything else.
For example we have Group A that has Office and LOB App and Group B that just has LOB App, I can prevent the shortcuts from showing up for Group B but I can't stop Group B from launching Office from within the LOB App.
So I was looking at UEM/DEM to do that for me if the user tries to launch an application they aren't entitled to.
Idle to have a couple RDS hosts with everything on them rather than multiple farms with different software bundles consuming more compute resources.
We're currently testing FSLogix with our VDI and UEM environment and will be rolling out to some pilot users in the next week or so. FSLogix is a game changer for us. The biggest improvement we're seeing is reducing login time from 4-5 minutes down to about 45 seconds and up to 1 minute. The application masking will help reduce the number of our master images which is about 50 right now to about 5 or 6. We'll still use UEM for a lot of things that we're pushing down.
How do we SHRINK the Profile container VHD file? I am using FSLogix and like what I am seeing (login times are really great) but having a 3+ GB VHD container for 500+ users is not an option for our organization.
I've used UEM in a non persistent environment just to capture user settings. The the two biggest issues I have with UEM is One, 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 VHDX files which a script can handle. So far, I'm thinking of dumping UEM completely and using FSLogix. what do you guys think?
i have not had any luck using FSLogix profile containers with Windows 10. it seems to breaks the start menu. i have went as far as just adding fslogix and the vmware tools, and horizon agent. I have tried on winver 1809, 1909, and 21h1 all the same result.