![]() So you just enable this policy and you’re all set, right? Not exactly!ĭespite this policy setting’s name and its promising description, it does not “set Outlook cached mode” but rather performs a little FSLogix kung fu (explained below) that results in cached mode being enforced, assuming the following steps have first been taken: Step 1 – Enable cached mode for everyone online mode depending on whether or not a profile container was successfully created or reattached at logon, thus avoiding the creation of a mailbox cache for users excluded from FSLogix profile handling or for any user whose profile container failed to attach for any reason at logon. Makes perfect sense: let FSLogix decide whether Outlook uses cached mode vs. VDI environments or elsewhere, you’ll likely have come across this FSLogix (not-really-a-)policy setting, “ Set Outlook cached mode on successful container attach”. If you’re among the many who’ve jumped on the FSLogix bandwagon to manage user profiles in your Microsoft WVD, Citrix CVAD, etc.
0 Comments
Leave a Reply. |