https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-rds
s
This message was deleted.
k
Is the Windows Search service running? This service is disabled by default in server operating systems
b
yes, it is.
d
Cached Exchange Mode is on?
d
Do u search for a mail from yesterday or for aspecific one that is older then three months
j
@James Kindon I found a post where you discuss something similar.. is it working for you? 2019 RDS (4 hosts).. using FSLogix with profile and office containers.
Also of note, the "Filter email" option on the outlook ribbon is grayed out for RDS users
j
I gave up trying to make up from down on Windows Search a long time ago
j
95% of our users work from home and use RDS since covid.. so inclined to fix outlook search but if its not possible... I can't seem to make heads or tails if folks have fixed it or not. I see some might've fixed by setting a registry key to store all index files in c:\programdata but that doesnt really work for fslogix/roaming users, unless im misunderstanding
j
the problem is that there seemed to be patch after patch after patch which would simply change the type of problem people were seeing. It all got messy when Microsoft moved the search index to user specific using their own tech rather than the way FSLogix was hooking into the machine index and inject bits and bobs - I had some success a while back in mitigating one issue where the index would corrupt, but that's about it.
j
Dont think I've hit that issue.. probably because theres no indexes to be had šŸ™‚ .. all works fine on a workstation of course. Have to imagine theres a ton of folks suffering from this.. or they've figured it out
does indexing etc work fine on an RDS host without fslogix?
j
you should be getting indexes. Windows Search Service Enabled, Features on (can't recall offhand which ones), Office installed after search enabled (or repaired), FSLogix Installed, do NOT enable Search Roaming in FSLogix, if it ever was enabled, disable it
and yes, to your direct question above, it should work with or without FSLogix - FSL was just their to roam/persist the user index, which MS now does natively
j
Wait.. I have "Enable Search Roaming = Enabled" in GPO.. I also have "Store search database in office 365 container" and (apparently) "store search database in profile container" both set to Enabled.
Without those enables.. where are things stored? assuming they're in the FSLogix containers currently although I'm not 100% if they exist
j
You want to disable all of those - https://jkindon.com/windows-search-in-server-2019-and-multi-session-windows-10/ check that for config. Long and short, you need to turn that stuff off from an FSLogix Standpoint
d
Yes this is your problem. With 2019 u must kill this FSLogix stuff
To roam the index
j
If you dont tell FSLogix where to store it, where will it store the index? :)
Upon looking further at my policies. I have the Policies ENABLED, but the settings set to "DISABLED". So I guess that means I have it how you're suggesting, eh?
d
Yep this looks good....
j
Kinda wish it didnt.. that means I already had it set up the way ya'll suggested and its still not working right
j
fslogix config looks fine, time to focus on search itself, windows logs search like a beast so Iā€™d suggest starting there (my post above should give you a start)
j
I'm looking now.. assume in Application logs.. seeing a lot of "2" events 
Unable to remove Windows Search Service indexed data for user 'mydomain\jdoe' in response to user profile deletion. Error code 0x80004002. No such interface supported"
finished reading your post.. so basically anytime an Event 2 happens, you need to restart the windows search service. Okay, can try. but how does one know that search is working properly? Should the "filter email" button no longer be grayed out in outlook?
the part I'm a lil curious about.. this is saying that indexes should work fine until the error happens, which triggers the restart of the service. What if the index is/has never worked on the RDS servers?
This is strange. So this morning I have the Filter Email button not grayed out, but still 0 items indexed
j
Welcome to why Iā€™m glad I no longer deal with search :-)
j
Its actually awful šŸ™‚ its so weird that restarting the service seems to get things "started". Also, possibly related, some users were unable to login to RDS and it gave a "resources are low" type message. I checked out the server and it seemed fine.. shrugs
since yesterday was first time I enabled the scheduled task... we'll see how today goes (users 2nd login since enabling)
I only see 7 users out of about 25 that have gotten EDB files created in their \appdata\roaming\microsoft\search... folders šŸ˜•
Open in Slack
PreviousNext
Powered by