This message was deleted.
# microsoft-fslogix
s
This message was deleted.
m
So this won't cause any issues with a customised start menu.xml e.g users will still be able to search for applications?
p
@Mark Child - Multi users roam search only supports outlook, searching applications probably will work but it will be stored on the OS. But test between different servers with he same user and check the search database is index correctly
m
Thanks Peter.
You wouldn't happen to know why you see this in the event log for search. The Windows Search Service is being stopped because there is a problem with the indexer: Recovery phase failed. Context: Application, SystemIndex Catalog Details: The gatherer is shutting down. (HRESULT : 0x80040d23) (0x80040d23) We seem to get this on certain RDSH boxes more than others. It has also caused issues with logins, where the user is met with a black screen as services such as FSLogix are waiting for Startshell and as the search service is having a fit, they don't see the desktop.
p
Sounds like the search database for the server is corrupt - get all the users off it then try - resetting the search -hopefully the picture comes through - make sure corecount it set too
Registry key which has had a very good impact. Please set the following key before a reboot or restart of Frxsvc and WSearch (first) Name : CoreCount Type : DWORD Value : 1 Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows SearchWhat this does is it causes Windows Search to run single-threaded and it does not appear to negatively affect CPU or responsiveness of Windows search.
m
I have reset the database already using the key, but will look at applying a GPO to restrict search as per the KB article. I'll get the CoreCount applied tonight. Thanks again.
If users are not logging off properly, could that upset search. ie they stay disconnected and the fslogix ODFC vhdx container is still attached to the RDSH?
p
Yes, it will cause problems. Maybe get a script to shut down the vhdx and disconnect them from the server