Open ChrisH82 opened 4 years ago
Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .
@Heidilohr @ChristianMontoya Please check this issue and update the doc if needed
@jakaruna-MSFT : Forwarded internally, to get the right folks involved.
@jakaruna-MSFT : Forwarded internally, to get the right folks involved.
did we get an update here? Get this question regularly in customer calls Seems to be a duplicate of #45664
@ChrisH82 This is a best practice recommendation that is applicable for large percentage of our customers. There are scenarios where that will not be applicable. From our research majority of IT professionals (~80%) lock down the environment.
@stgeorgi I agree on locking down the environment but I was more interested in the logic for the best practice as it seems hyper-aggressive restricting to only 1 month by default, perhaps worryingly so as the default in Outlook out of the box is I think 1 or 2 years. This level of best practice lock down starts to ring alarm bells around scalability with OST files, search indexes or something in FSlogix? I have certainly not found any customer who is happy with so little readily accessible mail.
The second part of my comment relates to the viability to disabled cache mode entirely on the basis so users get to see their entire mailbox in online mode (clearly subject to the provisioned WVD VM regions for users aligning as closely as possible to the Exchange Online region set for them so the mailbox servers are "local" - or as local as possible)
The best practices is optimized for many things not only scalability but cost and security.
For the second option we are evaluating but no comment at the moment.
Please explain the reasoning/need for the very restrictive Outlook Cached Mode/sync settings which set them (locks them so they can't be edited rather than default them) to only 1 month without the user having ability to override/edit.
reg add "HKU\TempDefault\software\policies\microsoft\office\16.0\outlook\cached mode" /v enable /t REG_DWORD /d 1 /f reg add "HKU\TempDefault\software\policies\microsoft\office\16.0\outlook\cached mode" /v syncwindowsetting /t REG_DWORD /d 1 /f
Is it viable considering both the WVD infrastucture and I assume the O365 CAFE servers are so local to run in Online Mode instead of apply a onerously sync restriction if there is an issue with Cached Mode?I though this is what FSLogix was meant to fix so that Outlook worked the same in WVD as it does on an endpoint device locally?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.