Forum Discussion
Outlook Search Not Working - WVD/FSLogix
Hi Everyone,
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.
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.
Hey mate,
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.
Thanks,
Nick
we having the exact same issue with WVD & FSLogix (2.9.7205.27375)
AT1991 by any chance has anyone found the solution to this?
I have the same issue.
I have found you can resolve the issue by making the following change;
File -> Options -> Search -> Uncheck "Improve Search speed by limiting the number of results shown"Does anyone know a way to make this unchecked by default through group policy or registry?cjpf_1 thanks ill give that a shot.
- Anyone have any success with this? I am also running into this issue.
Windows 10 multisession hosts using FSLogix- Yes, I came across that article. My understanding is Windows 10 multisession already has Multi-user search enabled so no changes are required in FSLogix GPO settings.
I have the same error\problems:
Failed to get the Crawl Scope Manager with error=0x80070005.
Failed to determine if the store is in the crawl scope (error=0x80070005).
Outlook is not indexing, I guess there is still no official fix for this problem?
I had contact with MS support. The Windows Search per-user indexing should work fine now.
It has been fixed in KB5007254.
Also, FSlogix is no longer supporting per-user indexing "the FSlogix way" as of FSLogix v2201 (2.9.8111.53415)
https://docs.microsoft.com/en-us/fslogix/whats-new
Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server. Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems.
We have just rolled out one AVD customer with this new (fixed) Windows Search version (running Windows 10 21H1 AVD), and seems to be working fine.
Marco Brouwer Great, I will check my customer if they miss this update. Thanks for the follow up.
