Deploying FSLogix Office 365 Containers
Have an issue you can't solve? I offer consulting engagements and can be reached here: consulting[а𝐭]amorales[․]org
This search portion of this guide does not apply to Server 2019 since it should roam the Windows search out of the box. However, you can still configure FSLogix to store Office 365 data.
In my experience it is best to avoid mixing FSLogix and UPDs. My recommendation is to go with FSLogix Profiles and FSLogix ODFC.
If you have dealt with User Profile Disks and Office 365 then you might know about the issues with search indexing. Every time a user signs out of the RDS their index is cleared and it has to be rebuilt the next time they sign in. The index will never fully rebuild once you have 5+ users on the server since it throttles itself.
Recently I discovered FSLogix which resolves this issue with minimal configuration. FSLogix creates its own UPD that it uses to store Outlook, OneDrive, and search index data. It then tricks Windows into thinking that it is stored on the local machine rather than on a UPD. The result is the index working immediately for all users.
All Users/New Deployment
UPD ExclusionsI don't recommend running FSLogix and UPDs together. FSLogix profiles will work much better. However follow the steps below if you need to use UPDs.
If it is not possible to explicitly include folders/files in your deployment/scenario then you might be stuck using "Store all user settings and data on the user profile disk". In that case, follow the steps below but keep in mind that you might run into issues with Outlook.
- \\SERVER\*.vhdx (File Server)
- \\EXAMPLE.COM\*.VHDX (DFS namespace)
- L:\*.vhdx (Local drive on the file server)
- C:\Program Files\FSLogix\*