I know some of you still use the ODFC container just for the OST file in addition to the profile container, I also still like this approach. Now I was surprised after a customer reported, that after deleting the Office container, the Office activation, OneDrive and Outlook settings were gone. I disabled all these settings in the Office container GPO but the registry keys are missing! Example:

OneDrive cache will be included in the ODFC Container.

NOTE:  Default is Enabled (1) which is the same as "Not Configured"

Registry Entry:  HKLM\SOFTWARE\Policies\FSLogix\ODFC\IncludeOneDrive

Type:  DWORD

Values:  0 = Disabled, 1 = Enabled

The policy is set to disabled, but the value isn’t present, so the default value (enabled) kicks in ! Anyone seen this before? FSL version 2.9.8612.60056

Related to this perhaps? https://learn.microsoft.com/en-us/fslogix/troubleshooting-known-issues#enabled-by-default-policies-in-the-ad[…]e-cant-be-disabled-using-group-policy

YES, that’s it! This is not funny, I suggest you all check these settings, this can be really annoying. Thanks @Aaron Parker for the finding, I have to admit I was too lazy to search for it…

What are friends for if they can’t RTFM for you? 😆

BTW, what is your recommendation regarding the Office container? I think it’s okay to use it only for the OST file, so that you keep all other settings when you reset the office profile container. Would you also disable all other settings except these ones? • Include Outlook • Outlook Cached Mode • Mirror Local OST to VHD • Remove orphaned OST files on logoff

Single container is the recommended configuration. If you have to reset your ODFC container frequently, there is a larger issue that should be investigated. We'll be addressing the known GPO issue in our feature release in Q2.

I read somewhere that ODFC will be deprecated. Just don't remember if it was the official statement.

News to me...🤯

Thanks Jason, yes I know. Meanwhile I also prefer to use one container. We have a few customers left with both containers. Sometimes there are issues with the cached mode, but I guess the customers got used to it, having a separate Office container. One advantage is, that if the Office container gets very large, you can easily delete it and let FSLogix create a new one. Sometimes we found that there was a backup file of the OST, so that the profile disk size was huge. It’s easy to find those containers with TreeSize and just delete them instead of mounting the profile disk and cleanup inside 🤷🏼‍♂️

There are some use cases for sure. My POV is based on what I would recommend. There is no "one size fits all" when it comes to an FSLogix configuration and we all have to make decisions based on business requirements and user behaviors.