windows 10 outlook 2016 search not working

Yes, there is currently a bug with Windows Search, but this has nothing to do with FSLogix. FSLogix is not the reason why Windows Search is not roaming, it's a bug in Windows Server 2019 probably related to the change MS made moving the Windows Search index from being machine based to a user based search index that is saved in AppData/Roaming. Well, the basic functionality of FSLogix IS working in WS2019 I know that for a fact. For the users where it's not working, i can see many accesses (lines) - see attachment.Īccording to i checked the registry entries (they are OK).Ĭreation and use of the OST-file works fine.ĭid you ever get FSLogix to work correctly for server 2019? We have many errors with search roaming since moving to 2019. When a not-working user opens outlook, the following two Outlook-errors show up in the Windows Event Log:Įvent ID: 35 - Failed to determine if the store is in the crawl scope (error=0x80004002).Įvent ID: 34 - Failed to get the Crawl Scope Manager with error=0x80004002Īdditionally, I can see with Process Explorer, that for the working user, the Search Index Database (edb) is getting accessed by SearchIndexer.exe only 1 time. This may be caused by mounting the VHDX for OST and Search Index.įor one user, even Search Index Roaming is working, for all others it's not. Since it's configured, the login takes extraordinary long time.

It's Windows Server 2016, Outlook 2016 (32bit) and VDA 1811, Profile Management 1811. I recently configured Outllok Search Index Roaming for the new server-environtment.

Windows 10 outlook 2016 search not working