https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# _general
s
This message was deleted.
m
MS support strongly recommended we not index OneDrive when I had a support call with them about all the weird search index errors we were getting with FSLogix...
👀 1
n
Did that also apply to stuff like Documents when redirected to the OneDrive location?
If we can't index any of OD stuff, there is literally no need to bother turning on the Windows Search service.
m
Yeah, we asked about that and they said we shouldn't index redirected stuff. Once we turned off indexing our desktop icons stopped flickering because we were indexing the redirected desktop too.
our search service would also go to near 100% CPU trying to index all the stuff in OneDrive
This was Server 2019 though
n
JFC
If I kill the Search service, then delete the Windows.edb file and start the service, it seems to work fine
This is in a fresh profile, mind you. Shouldn't have to do that.
m
Search in general is just awful in the Win10/2019 code
n
Hell, searching in general just doesn't work. I can open File Explorer and search for anything in the top right, nothing.
m
is there anything in the logs saying the index is corrupt?
Maybe something messed up the index in the default profile?
I had weird issues on 2019 where something I did to my image killed the index for everyone who logged in, and then it went away on the next image build and I never really worked out what it was. It's so touchy.
n
Nothing that I can see. If I rebuild the index, it starts to work right away, too.
I really wish there was a PS cmdlet for rebuilding the search index.
Also, for the default profile, not even sure what would be in there that could hose up the search.
especially since the DB is in ProgramData
m
I wonder if @James Rankin knows about default profile and search indexing, this seems like something he would know
is your service set to Automatic and not Delayed Start?
n
Yeah, Automatic. Everything I read says to not do Delayed Start, even though I still wonder if that's part of the issue - Search indexing before FSL can mount and OneDrive launches.
m
All the stuff I've read on FSL says not to delay it though
n
Yep
m
it might be getting hung up on not being able to instantly find the documents folder if it's in Onedrive
n
Requiring admin rights to rebuild the search index makes no god damn sense
m
anything useful in the FSL search logs?
n
Nope, FSL search logs all show it finding the setting, then doing what it needs to in order to use it and roam. All success.
m
can you do it with the frx reset tool? That probably needs admin too
n
I can try that next, though I imagine that it needs admin rights.
Yep, needs admin rights.
And WEM on-prem doesn't yet have the automatic elevation feature. Even so, still doesn't explain why searching is just broken in general. Taking OD out of the equation, it's stull busted.
Weird, I no longer get the Search tab up top when you click inside the Search field, either.
I think it's related to FSL. If I kill the FSL service and then login, once OD launches I can search for those folders and files. At least, some of them. I bet I can search for all after that OD sync finishes.
And the index shows more and more items added.
Which begs the question: If roaming the index is the issue, is it worth disabling roaming and allowing it to rebuild each time?
m
Does it only do all this on first logon?
n
No, it's broken full time.
And I've tried the latest FSL build (currently in Prod), and the previous build. Same issue in both.
m
Might be worth playing with delayed start then of the search service and see what happens, probably can't make it worse
if it's waiting for that onedrive sync maybe you can start it with a scheduled task
n
I guess I can give both of those a shot. Delayed start, and disabling roaming.
When I rebuild the roam index, it literally takes seconds to finish, so I'm not entirely opposed to that right now. If OneDrive is fully sync'd, the CPU shouldn't be getting hit up.
Actually, I don't see how Delayed Start would matter here, since that service starts with the machine, so it's always going to be running before a user logs on.
Hmmm... WSearch set to auto delayed, OD sync starts, and I can search OD content in File Explorer, but not the Search bar in the taskbar. May have to wait a little for that, but at least I am getting results. Still weird that the indexing options only shows 466 folders (5000+ were there without FSL enabled).
m
that is weird
n
I'm going to try not roaming it and seeing how it goes. I don't trust that delayed start setting.
Roaming disabled, service set to Automatic... no results anywhere, lol.
@James Kindon: You wrote a blog on index roaming, and you called out not to use Delayed Start. Ever see the nonsense I'm dealing with now before? W10 20H2 VDAs on 1912 CU3.
j
Never encountered issues with indexing from a default profile, no
j
I don’t even pretend to know where search is up to these days - whole thing breaks my brain
✅ 1
n
There's just so much conflicting info. MS has a troubleshooting doc for FSL and Search, and they say to change the service to Delayed Start (https://social.msdn.microsoft.com/Forums/en-US/2b4b271a-c29c-44c5-b5a7-b28f5a809be6/outlook-search-troubleshooting-guide?forum=FSLogix). I'm going to have to continue to tinker.
Testing is so inconsistent. I was able to search in File Explorer at the start of my OneDrive sync. I leave for an hour, OneDrive has finished syncing, and now I cannot search for anything in Explorer. Logoff, logon, OD fully syncd - can't search for shit.
I should clarify that if I have "This PC" selected, I get no results. I have to actually navigate to my OneDrive folder and then search in order to get results. And I literally mean the OneDrive folder - not the subfolders (Documents, etc.). If I go to a subfolder, I can't search for anything there.
5 Views
Open in Slack
PreviousNext
Powered by