This message was deleted.
# citrix-vad
s
This message was deleted.
r
All my 1912 are Server 2019 atm, sorry.
r
I am in the process of upgrading. I didnt see this in my test site.
e
We want to move as well to WS19 but had to roll down due to Outlook Search / FSlogix not working. So 2 issues which prevents full scale roll out....
r
How can you tell the Search isn't working ? Perhaps mine isn't as well. 🙂
d
I am scheduling upgrade so - *watching 🧐
e
Check indexing status
r
1 items indexed, indexing complete, but nothing in item's indexed.. ?
k
r
There was supposed to be a patch to fix it.
k
I have done some tests in my lab, and even with a local profile, the search index builds just fine during first logon, any subsequent logons, the search index is corrupt and you have to restart the WIndows Search service, to get the indexing up again
Yeah, the patch doesn't really fix anything, at least that's what I have seen in my lab
r
KB4534321 poop lol
Dang it
k
What I don't understand is that this issue is more than 6 months old, what's going on in Redmond?
r
I had a meeting with the fslogix manager yesterday. He was a super nice guy, but the are limited on support right now. They are expanding, but its taking longer
k
From my point of view this doesn't have anything to do with FSLogix. People are reporting the issue with User Profile Disk in RDS and as mentioned I see the issue with local profiles as well
r
No thats a good point
k
Actually MS change the FSLogix documentation stating that FSLogix should no longer handle Search Index roaming in WS2019. I am trying to find the amended documentation
r
wth is up with that?
r
What that just broke my brain
So it needs to be 0 for "NOTE: Windows Server 2019 and Windows 10 Entperprise multi-session support per user search. RoamSearch should not be enabled in these environments"?
Damn Kasper how the heck did u find this. Awesome bro 👍👌👌💪💪💪
r
what does that actually mean though?
it will work if set to 0?
r
That is how I am reading it.
Sorry Eric
r
Ok, I will test this, post-haste!
k
@Ray Davis someone on Twitter mentioned it @Ryan Gallier configuring it to 0 prevents FSLogix from roaming the search index. It still doesn't work
r
My index says Microsoft Outlook in included locations... it's still not actually working?
now that i actually started the search service...
k
Have a look in the Event Viewer in the application log. You should see ESENT generate a few errors
r
nods
k
at least that's what I see at the second logon of a user
r
I see a lot of ESENT, but no errors. 301/302/105/326/637/325
k
Do you see any events from Outlook?
r
No errors... 45 and 63
k
Hmm...try logging off and log on again
r
nods
@Kasper Johansen I see nothing here that tells me it's broken
e
RoamSearch 0 does not work with latest version, so still no go.
r
So, wtf does mine show Microsoft Outlook as an Indexed location, and I haev no errors
e
In terms of freeze, Citrix have heard no reports so far, so might be FSLogix.....
r
if it's working, someone needs to look at it... haha
e
Are the search icons in the ribbon grayed out?
k
If it is working, you need to share your config 😄
r
which icon specifically?
e
I think a guide for how to check if working is needed, was walking in blinds for weeks
If you rename your profiie to .old and try again. When you start outllok it should show high index status counting down to 0
r
just the profile? I'm saving search in o365 container
if you want to remote in here and look, i'm fine with that too
k
Could you click "Search Tools" and then Indexing Status?
e
Looks okay
r
Indexing status is sitting at Loading...
e
Then its no working IMHO
r
and there might be the indicator that it's not working. 🙂
i would tend to agree.
k
Yes, if it just sits there with the "Loading" message, the search index is toast
You will see that in WS2016 as well if something is wrong
Oh well I was hoping you had the right config @Ryan Gallier 🙂
r
same. oh well. We all were.
My users don't even notice. Outlook still searches nearly instantly
k
Yes, I actually see that too and I don't get how it's possible
I've searched for stuff in my mailbox that I know I have never searched for and it just pops up instantly
Well, I'm off to bed, it's getting late here in the small kingdom of Denmark 🙂
j
hey guys, just saw this and wanted to post my issue with this. I found it to be related to an older Citrix WEM agent. Once I upgraded to a new version of WEM (1911 or 1912) the issue went away