- #Outlook 2016 indexing keeps breaking how to
- #Outlook 2016 indexing keeps breaking update
- #Outlook 2016 indexing keeps breaking windows
#Outlook 2016 indexing keeps breaking update
#Outlook 2016 indexing keeps breaking windows
#Outlook 2016 indexing keeps breaking how to
Learn how to configure cached exchange mode in Outlook 2016 OneDrive for Business The recommendation for pooled VDI and RDSH deployments would be to use Outlook 2016 in cache mode with network connectivity to allow service search. Outlook might fall back to using the local search indexer in some scenarios, but most searches would use this new service search feature. This uses service search results against the local cache (OST). Outlook 2016 has a solution to tackle this in cached mode by providing a new service search experience for mailboxes hosted on Exchange 2016 (or hosted in Office 365). Learn more about the difference between cached and online mode Using an Online Mode account profile would work around this, but overall performance would suffer due to the lack of a local cache. Search would not only be slow but might not produce results. OST file, the indexer could take a long time to complete and use up resources needed for other apps. That would mean, if we enable local search, the indexer will run every time the machine ID changes (when the user is on a different VM). It is possible that every time a user logs into a pooled VDI infrastructure, they are directed to a new VM. Search indexing depends on the machine ID, which is different for different VMs. In pooled VDI and RDSH deployments, using search within Outlook has limitations. Use the following information to plan how best to integrate Office 2016 into your Remote Desktop (RDSH) and VDI deployments.įor more information about integrating Office 365 with your RDSH or VDI environment, check out Microsoft Office 365 for Citrix XenApp and XenDesktop 7.x.