Jan 19 2021 09:53 AM
Jan 19 2021 09:53 AM
I noticed when I log off a session host in Remote desktop/WVD, this message displays for about 10 seconds:
And then it finally logs off.
Is this a service I should disable?
The image was Windows 10 multi session host, 2004
Jan 20 2021 05:34 AM
Make sure you are not out of disk space.
Run this query for that WVD
Jan 20 2021 08:17 AM
Hi @Jgq85 - I will always recommend disabling Windows Search in your image unless its specifically needed. Using FSLogix helps, but there is definitely a performance impact and you will come across issues like this.
Jan 20 2021 01:42 PM
Hi Neil - I'm seeing conflicting messages about this which has confused me, there are quite a few articles relating to search in multi-user contexts - this one is very handy - https://jkindon.com/2020/03/15/windows-search-in-server-2019-and-multi-session-windows-10/
The thing is, since Win10 2004, and even with search disabled, I'm seeing loads of FSLogix errors in event viewer like the below.
Search catalog mount failed (The security ID structure is invalid.)
Do you know if these errors should be ignored, or if there is a configuration step to prevent FSLogix attempting to include them? I've looked at the RoamSearch reg entry, but believe this should be disabled by default.
Thanks for any help, one for the WVDUG perhaps!
Sorry for thread hijack!
Jan 20 2021 02:01 PM
Apr 20 2022 12:58 AM
Was this ever resolved? I have had a ticket opened for two weeks with Microsoft with no progress.
Was the solution to just disable both FSLogix RoamSearch and also disable Windows Search? What functionality is lost by doing that?
Jun 27 2022 12:16 PM
Jun 27 2022 12:28 PM
Here is what worked for me:
Our issue started after installing Adobe and it tried to index inside the documents as well. It kept hanging and changing these indexing filter options resolved it.
Jun 27 2022 12:42 PM
Jul 13 2022 11:02 AM - edited Jul 13 2022 11:03 AM
Hi @crshovrd, I'm sorry for the late reply! I've been sick for a while now...
Today I got in contact with the client and apparantly the issue still remains, even after changing the File Types of PDF... So, back to troubleshooting...