[German]A few days ago a Microsoft developer was talking about the evolution of the Windows search. And Microsoft has changed the search in Windows 10 version 1909 as well as in Windows Server 2019 – which brings collateral damage. Time for a blog post with an outline of the topic.
Advertising
Evolution of Windows Search
The colleagues of deskmodder.de noticed the Microsoft article The Evolution of Windows Search from March 12, 2020, dealing with the evolution of the Windows search. A Microsoft employee is outlining the story about Windows Search, from its start 29 years ago until today. This goes up to Windows 10 and the 'improved' search.
Issues after changed Windows search in Server 2019
I mentioned in the blog post Windows 10 Insider Preview Build 18317: Separating Search and Cortana: Microsoft has made major changes to the search in Windows 10, and thus also in Windows Server 2019. That causes some collateral damages, as the tweet from Thorsten E. indicates.
Windows Search in Server 2019 and Multi-Session Windows 10 – thank you @james_kindon https://t.co/Ag9ur6WKRc
— Thorsten E. (@endi24) March 15, 2020
James Kindon works with Citrix and looks at the collateral damage that Microsoft is causing with its changes to search on Windows Server 2019 and multi-session sessions in Windows 10. There has been this thread in the MSDN Forum since summer 2019, which deals with support for Office 2019 Search Roaming on Windows Server 2019. In February 2020 it becomes clear that a modified search database causes conflicts with FSLogix and Citrix profiles.
In Windows Server 2019, the way search roaming works with supporting technologies such as FSLogix Containers and Citrix UPM differs from Windows Server 2016. The biggest change is that the Windows search index is now located per user in the user profile under
Advertising
C:\Users\%Benutzername%\AppData\Roaming\Microsoft\Search\Data\
Applications\{UserSID}\{UserSID}.edb
At each logon, the Windows search process creates a new instance of the search database for the user, based on the existing EDB. If no EDB file exists, the operating system creates a new one. This then causes problems for users of technologies like FSLogix Containers and Citrix UPM, which are described in the article here.
