Feb 05 2020 01:39 AM
Feb 05 2020 01:39 AM
We use a multi-session win10 environment, for a number of users we have an issue where they cannot search outlook.
It states that the windows search is unavailable despite the service running.
My profile however has no issue with searching, would it make any difference that my mailbox is migrated to Exchange online whilst the others are on-prem? We use Outlook for Office 365 desktop client.
Clearing the user's FSLogix profiles does not seem to resolve the office, I have not tried to clear a user's 365 container yet. Other users can search despite the message but returns searches in a non-sequential order.
If anyone can assist that would be amazing.
Feb 11 2020 08:21 AM
I have the same issue. I have read a few things in regards to this. One is you have to have ROAMSEARCH=2 option set for FSlogix. It does not work. I have also read that With windows 10 MS and Windows 2019 the search service is built in and the option should not be applied. I have tried both. Interesting thing is that I manage these settings with a GPO on all WVD Session host and I can sometimes log into a SH and it works fine, then log off and back onto the same SH and it does not work. Did a complete uninstall and reinstall of most recent FSLogix version. Attempted to manually add settings in registry and use GPO.
I have reached out to MS support and I get two different answers form them as well.
Feb 26 2020 09:01 PM
Are you noticing events in the event viewer logged by outlook in application logs, event IDs 34 and 35.
See message bodies below:
Event ID 34: Failed to get the Crawl Scope Manager with error=0x80070005.
Event ID 35: Failed to determine if the store is in the crawl scope (error=0x80070005).
I have two customers with new WVD implementations and both are plagued with Outlook searching issues in Outlook on the WVD session hosts.
I've tried everything I can think of, and I'm tearing my hair out here.
Jan 27 2021 07:22 AM
I have the same issue.
I have found you can resolve the issue by making the following change;
Aug 09 2021 06:32 PM
Aug 09 2021 09:28 PM
Aug 10 2021 12:44 AM
Microsoft has to confirmed to us that the multi-user search indexing currently has a bug / is a known issue. ETA on a fix is not yet given by MS.
However, we received a private fix from them which fixes the problem for testing purposes. In the meantime, we are using this workaround:
- Disable Windows 2019/10 user-based search indexing (HKLM:SOFTWARE\Microsoft\Windows Search "EnablePerUserCatalog" DWORD 0.
- Enable FSlogix search indexing (searchroam = 2 = multi-user search enabled).
Although FSlogix search roaming is not supported for Windows 10 / 2019, it works like a charm and fixes Outlook search indexing issues.
When MS release a public fix for the bug, we can revert back to the Windows feature. Only inconvenience will be that every user will need to rebuild his search index, but I don't really care.
Aug 18 2021 01:18 AM
Aug 19 2021 11:04 AM