FSLogix Profile Containers a Quick and Easy WIN !
Many of you know that FSLogix has the best solution for combining Microsoft Office 365 and non-persistent environments, such as Citrix VDI – you can read my article about Office 365 Containers here. Although, FSLogix has another great product called Profile Containers. In this blog, I will explain what profile containers are, why it is an easy and a quick win for every business that is struggling with user profile issues. Furthermore, I will quickly explain how to setup the FSLogix Profile Containers.
When a user logs on to their Windows session, the Windows User Profile is loaded. The profile includes everything from the users download folder to their mouse scrolling speed preference and everything in between. So you can imagine that profiles can get big. There are also some programs that create massive profile data like AutoCAD – which – due to Nvidia GRID technology, works great in a VDI environment but easily generates GB’s of profile data. If the users profile is this big a roaming profile solution won’t work. Logon will take minutes or in some extreme cases hours to complete because the FileServer will copy all the profile data to the endpoint. Even “just in time” profile technology like Zero Profiling isn’t able to handle the big application data quick enough for a good user experience because it also just copies the data from a FileServer to the endpoint but not in one big chunk like roaming profiles. So, how does FSLogix Profile Containers help?
FSLogix Profile Containers creates a Virtual Hard Drive (VHD) file on a FileServer and stores the user profile including registry in the VHD file. Sounds relatively simple, right ? Although, why does this improve speed? Well, during logon the only thing that is happening is that the endpoint mounts the VHD file as a Virtual Hard Drive and then the profile is just accessible. So there is NO data copy! This results in lighting fast logons. And eliminates FileServer and network bottlenecks from logon storms.
FSLogix Profile Containers also gives the end user native support for Office 365 products, such as:
- OneDrive for business
- SharePoint folder synchronization
- Skype for Business GAL
Profile Containers Cloud support
It’s worth mentioning that FSLogix Container solutions just received a new major feature upgrade, named Cloud Cache. This new functionality adds the possibility to add multiple storage repositories to the existing products to provide high availability to on-premises and cloud environments.Imagine a workspace scenario where you are running a VDI environment in Microsoft Azure. Typically, you store your profile data on a Windows file share in Azure Infrastructure-as-a-Service. The Cloud Cache Driver makes it possible to provide the store of the Containers directly on much less expensive Azure Blob Storage. This is just one of the significant use-cases which FSLogix is solving with this tremendous new Cloud technology.
Other uses of Cloud Cache include high availability in the event of storage or network interruptions, profile storage server migrations, cloud migrations, offline access to FSLogix containers, and more. To catch up on Cloud Cache, check the following blog, Introducing Cloud Cache.
So, how do you setup FSLogix Profile containers?
First you need to download the software, you can do this by requesting a trial here. Then you need to push the installer to your endpoints, you can use these silent install parameters: “FSLogixAppsSetup.exe /install /quiet /norestart ProductKey=YOURPRODUCTKEY”. With your installation software you also get a FSLogix.ADML and ADMX file. You need to copy these to your PolicyDefinitions folder in \\YOURDOMAIN\SYSVOL\Policies. Now you have to create a new GPO object and set the following options:
Don’t forget to disable roaming profiles and enable local profiles on the endpoint. You can monitor if the Profile Container is working correct with the easy FSLogix Tray application located in:
“C:\Program Files\FSLogix\Apps\frxtray.exe”. And thats it, your users can now logon with lighting speed and you never have to worry about profile issues again. It is an easy and simple quick win!
FSLogix Profile Containers can also easily be combined with User Environment Managers like Workspace Control by Ivanti. The only thing you need to do is go to User Settings and in the Settings tab set Track User Settings to Disabled.
I would recommend watching the video below to learn more about FSLogix Products including Profile Containers. And check out the FSLogix Website here.
Don’t forget to also check out the SBC/VDI Profile Cheat Sheet which also includes FSLogix Profile Containers.
I hope this was informative. For questions or comments you can always give a reaction in the comment section or contact me:
6 thoughts on “FSLogix Profile Containers a Quick and Easy WIN !”
Hi there, for all time i used to check weblog posts here in the early hours in the morning, for the reason that i like to find out more and more.
I love to see this thank for all this nice work
Howdy! This is my first visit to your blog! We are
a collection of volunteers and starting a new project
in a community in the same niche. Your blog provided us beneficial information to work on. You have done a
It there also a best practice manual for managing profiles Containers?vhs
Like If there is a corrupt profile how to handle? rezing vhdx?
If I disable roaming profiles and enable local profiles on the endpoint.. this then still creates a local profile which is a copy of what is in the profile container. This consumes space on the local drive.. so is there any way we can get around this? I find I have to have this enabled as otherwise the roaming profile setting gets pulled Active Directory which I don’t want on this RDS Farm.. but the downside is the local profile takes up space! I’ve got delete local profile after X days enabled but this means I’ll need to reboot the endpoint regularly.
Hi Chopper, The FSLogix profile is a local profile and should not cost extra real disk space because the local user profile is not copied. It’s redirected to the container. If there still is a local copy of a user after you sign out with FSLogix then something goes wrong with appplying FSLogix and you should check out the logs.