This message was deleted.

Yes have a case open with MSFT on it

Try set

Outlook cached mode on successful container attach

to Disabled for Profile Container and Enabled for Office Container and see what you get

Seeing this aswell, I had it double configured initially, logs were showing Outlook cached mode policy rule already exists for user in OFDC logs. After disabling it for profile container last week, logs were fine, but it still didn't go into cached mode on container attach. I'm only getting it to work at the moment if I force cached through user policy/Ivanti

What version are you seeing that in? I just logged in with my O365 test account and it all looks normal on v2.9.7117.27413. I only have the 'Outlook...container attach' setting configured in the O365 container GPO, not the Profile container.

2.9.7205.23375, cached mode is not triggered unless specified from something outside of fslogix for us.

Considering the other existing issues with that version and the Search index, this doesn't really surprise me.

I'll check with that version if it behaves nicer , thx 😉

@Nick Panaccio Do you have a link to that version?

Give me a few minutes and I'll throw it in my Google Drive

Same behavior with v2.9.7117.27413 in this environment, still no cached mode on container attach.

Thanks!

Interesting. Is that behavior consistent across your environment? We only have a few 365 users, so it's hard to gauge past my own test account. FWIW, we're running FSL on W10 1709 VDAs.

it's a new environment , consistent on about 10 test accounts, regardless of 365/onprem mailbox using O365 C2R in image. Server 2016 with 7.15 CU3 & CU5 VDA's. At the moment we're just forcing cached mode for production users. Since we don't have any vdisk locking etc. It's just a failsafe of a failsafe since we don't want to disable logging in with temp profiles. But it would be nice if it worked as advertised.