https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-fslogix
s
This message was deleted.
r
Indexing shows just a status and is blank?
I get the same results in 2016 more yellow though. In my experince it wouldnt show nothing. But lets see what the Fslogix experts say.
Go down and look for......... James has some good stufff Here we can see some pretty nice problems 1. The search database is located in the container, however 2. It cannot be mounted for some reason – this is the great unknown in some of these deployments. What happened to the index to break it so that FSLogix cannot mount it? 3. Despite the fact that the catalogue fails to mount, a basic ICACLS is again run on the WSearch folder to grant the user full permissions
j
This is the status of index search
l
Per user Search is automatic in 2019. A few folks had an issue with it. It automatically is stored in the profile disk. Don't set any redirect settings.
j
Perhaps it's normal ? Outlook does not show up in the windows indexing options when FSLogix is virtualizing Outlook Search. This behavior is intended (from https://docs.microsoft.com/en-us/fslogix/fslogix-trouble-shooting-ht)
j
Article needs to be updated for 2019 search - once I understand it and have it consistently working :-)
Turn off all search settings for fslogix - OS should handle it but it’s buggy from what I’m seeing
👍 2
k
Microsoft updated the documentation for search roaming with FSLogix when using WS2019 and Windows 10 Multi-session:
👍 1
j
For my perspective it seems to work because search is quick and words are highlighted. Is it enough to confirm this is working?
k
I see that too, and I am not entirely sure what's actually going on. However I do see a lot of ESENT errors and warnings during second logon and that usually indicates Search Index corruption
j
I dont't see any error or event ESENT for users who use FSLogix Office 365 containers at logon but one at logoff Seach-ProfileNotify, 2, -Unable to remove Windows Search Service indexed data for user... I will send a message to my customer to make more test before make users migration
👍 1
e
IMHO Search does not work on WS19, even though it seems like it. My power users says its broken, so we rolled back to WS16. Though have not try with a fresh container, using the same for WS16 & WS19 testing. New project nxt week starting fredh, lets see how that goes
k
Keep us updated Eric. I have a new setup started this week on WS2019, we will hopefully start testing a bit next week
e
Goody, I might have two depending on progress.
r
Seems like MS is having a hard time on 2019 search function combined with fslogix. One reason why i haven't went to 2019. So many answers and testing and results are strange.
k
Yes, maybe MS should just revert to the machine based indexing and let FSLogix handle the rest?
r
Seems that way. Its a tuff one now. I appreciate them doing it in the OS but i think when they developed that the had no idea on terms of Fslogix and its operations. Plus support is still immature as they are taking on some big cases now.
e
This is what we should see when indexing works
👍 2
r
What os?
Assuming 2016 for u
e
Yes 2016 where it works
m
I just see indexing complete 0 items indexed.
also get "Something went wrong and your search couldn't be completed"
and then next log in we get "waiting to receive indexing status" forever
I tried restarting the search service but it does nothing
l
Check your FSLogix search log in program data.
e
What OS @Mike Streetz (O_P)
m
server 2019
e
Thats why it doesn’t work 100%
m
I'm seeing people saying they have it working with the scheduled task to kill wsearch at logoff but I think I have issues before that. It's a client environment and they've given up playing with it and just turned search off.
Open in Slack
PreviousNext
Powered by