This message was deleted.
# microsoft-fslogix
s
This message was deleted.
j
was having issues with outlook index hanging, identified search redirection at play - turned if off and things much healthier
p
did you get this working James?
j
certainly did (as far as i am aware) - killed search redirection (yuk) and indexing started. I know @Kasper Johansen has been having some problems with 2019 though - i need to check back in with customer and see how its hanging for them
k
Yeah, it seems like the issues I had wasn't exactly issues, it was just the indexing feature in Outloook/Windows acting different compared to Windows Server 2016
j
so your email search basic tests play nicely enough?
k
Yes, it does actually
However I never see the Indexing Service in Outlook counting up or down, but I do see the Windows Search Index .edb file is populated with some sort of data
j
Now I'm going to have go and confirm and see if the same thing happens in my environments - always something else to check with windows search 🤬🤬🤬
k
Yes, please do I would like to hear if anyone else has the same experience as I have
p
I believe Microsoft may have put some security protection around the searchindexer.exe process being hooked (most solution handling the Outlook search indexing do this). it's a security measure to stop it being hooked. AFAIK (as an example) Citrix UPM don't currently support Win10 1809+ and Server 2019 for this reason, see the note in this article https://docs.citrix.com/en-us/profile-management/current-release/configure/enable-native-outlook-search-experience.html
the best way to check is ProcessExplorer and check the dll's against the searchindexer process to check it is being hooked.
k
Well, the WSearch folder within the profile container does have different NTFS security permissions defined compared to other folders in the container, so that may be the case
However I do see the search index getting redirected and I do see data go to the .edb file