This message was deleted.
# microsoft-fslogix
s
This message was deleted.
πŸ‘ 4
s
So if search index is not roaming then the index will be created at every logon?
k
The Search Index is located in the user's profile (Somewhere in AppData\Roaming)
πŸ‘ 1
Whether this user based Search Index is reliable/stable is yet to be seen, at least from my point of view
j
Yep - seems to be some angst online
k
It has been a while since I looked at it, but my previous tests showed some instability when roaming the Search Index, without FSLogix. But MS might have fixed that..
I have just run some quick tests. I am still seeing a couple of errors from the Search service when logging on, but it does look like the Search Index is actually working as expected. I can see that the SearchIndex process and Outlook process are using some CPU and data is beeing commited to the Search Index database file in the user profile.
a
for us it is not working
a lot of errors , index corruption and all the good stuff
k
Yeah, I am seeing that also. After 2-3 logoffs/logons I see some instability and corruption
πŸ‘ 1
a
we revert back to 2016
k
Why? Is FSLogix Search Roaming not working with WS2019?
πŸ˜‰ 1
r
There is a topic on the FSlogix forums that state 2019 isnt playing well with FSLOGIX. Being fslogix is trying to do the search function and windows.
k
Wow! How is that still an issue??
It's been more than 6 months since the issue was raised
m
Reliable now ? Still had issues
MS case still open, no Solution
r
Yea im feeling the pain from the fslogix support team as well. Im not sure whats going on over there.
k
I am guessing that this is not entirely an FSLogix issue?
πŸ‘ 1
m
@Kasper Johansen youβ€˜re right
k
Well, if it's a server issue it might explain why it's still an issue and also a bit concerning considering the bug has now "lived" for more than 6 months
@Ray Davis a guy in the forum thread you posted earlier mentions a hotfix that's only 7 days old, which apparently addresses some issues with the Windows Search feature This is the hotfix: https://support.microsoft.com/en-us/help/4534321/windows-10-update-kb4534321 I am currently building a new vDisk with the hotfix installed
πŸ‘ 2
r
I read that as well. We will see how it goes for him
Cant remember if this was the thread on 2019 and fslogix? We had a couple, just curious on how things are coming along. I know @Eric and @James Kindon and maybe @Kasper Johansen seem to have success? I know @Ryan Gallier has a case still.
k
@Ray Davis I am still looking at a workaround where I restart the search service whenever a specific event ID is logged. I have seen mixed repports on the outcome of that. For now it is the only option. The Search Index feature is very unstable even with a local profile
r
Thanks Kasper, I am just trying to log all the notes and issues. So I can have some type of patch when I test.
k
@Ray Davis a lot can happen in 5 days πŸ™‚
I was made aware of this article: https://support.citrix.com/article/CTX270433 And I am currently testing the registry value mentioned and it actually looks like it in some way reverts the per user serach index, to a per machine and if we then have FSLogix roam the search index, it's looking a lot more stable