https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-fslogix
s
This message was deleted.
k
Nice!
I will test that with FSLogix ASAP
👍 1
n
i wonder if this applies to 1809 as well?
k
I am waiting for some test results 😄
j
Set the following registry value if not present or already set to 0 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search] "EnablePerUserCatalog"=dword:00000000 That doesn’t sound right
Setting to 1 was what enabled multi user search in 2016 - does the article mean to say set to 0 (turn off) if set to 1 maybe?
I have a Q in to UPM devs around this at the moment given that upm search roaming must also be effected by the changes in 2019 - my guess is they are saying turn it off
s
@James Kindon Does this article is applies for WS2016?
n
it doesnt mention 2016, only 2019
s
James mentioned in above msg 2016
r
1809 is kinda 2019 in my opinion.
s
Ok
r
"does the article mean to say set to 0 (turn off) if set to 1 maybe?" I agree with what James said.
r
Anxiously waiting results here
r
🙂
s
If it helps multisearch in 2016 was 2 for on 1 for single and 0 for off. https://docs.microsoft.com/en-us/fslogix/configure-search-roaming-ht
i phrased that wrong. 2 for multi , and 1 for single was the default. I dont think there was a 0
k
Yes, there is a 0, it's disabled :)
s
@James Kindon or anyone else. is the _HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\WindowsSearch\Preferences\EnablePerUserCatalog(REG_DWORD still valid in 2016 for FSlogix multi-user? I dont even have that in my registry for 2016 boxes._
k
I think it's for 2019 only
r
The article did say 2019.
But I can understand the confusion
s
Sorry, Im just talking about the dword EnablePerUserCatalog itself in 2016 boxes. Per James statement above he notes that for 2016 VDAs this dword was set a certain way. In one of his blog post in 2018 he also noted the dword for 2016 boxes. However, my testing shows I dont have the dword at all. I dont want to derail the topic so I will take it elsewhere. If you have a 2016 box and use multi user, let me know if you have the dword.
k
I have never seen or heard of this dword before today, that doesn't mean it doesn't exist in 2016 :) However maybe @James Kindon is referring to the RoamSearch value?
s
Im sure most of you here have read this, but just in case. (This is where I heard of that dword) https://jkindon.com/2020/01/06/fslogix-containers-search-index-considerations-and-troubleshooting/
k
Well, I'll eat my word about @James Kindon referring to another reg. value. I have just gone through the article, I don't know how I missed it, and James is on whole other level 😯
r
LOL, James is good. But Your very Smart to Kasper
k
Yeah, well James is on another level :D
r
So.... Set it to 0 fixes 2019? I'm confused
k
Hopefully
Will test later
r
i would love to test, i just have a datacenter i'm trying to get live... swamped atm..
k
Spending time with the kids :)
r
better idea
k
:D
g
Will test this first thing tomorrow:-)
j
That article wasn’t just me - that was with some very clever lads including Nigel from fslogix directly, it was a long time ago so maybe things changed but that key was definitely at play (can’t recall who did that bit of the post)... Looks to me like Citrix are simply doing the same as fslogix have done in relation to roamsearch in 2019 - leave defaults (disable) and let windows handle it natively - but could be wrong
👍 1
r
I have everything at default and it's still broken
j
@Ryan Gallier dude what are your break points - any pattern? - I’m still trying to consistently break it and map the process (at the moment testing windows with no other components such as outlook - introduction of that for the next round of testing)
r
i'm not exactly sure WHEN it broke, sadly. My two production environments are broken, and have never been fixed. I also have not had a chance to test the "workaround" microsoft gave me.
e
Testing...
k
Me too 🙂
#metoo
I am seeing some changes to the positive
still testing though
I am no longe seeing any windows search errors what so ever
I just need to verify that FSLogix is able to properly roam the search index
r
So you think this is BINGO "EnablePerUserCatalog"=dword:00000000"
k
Yes, for now
s
@Kasper Johansen is there a way to test verifying that its roamin the search? Besides looking at the local edb on the machine?
k
I am currently looking at Outlook indexing my mailbox. What I do is let it finish the indexing, and then log off and log on again, if it is still 0 and the indexing doesn't start at a really high number, it is roaming
This is awesome!
Search Roaming is now working in 2019 exactly as it did in 2016
will test some more, but it is looking really good
e
I check if indexing is not stuck (showing 0), search ribbon is nit grayed out & file - options - search
I’ve had false positives before so also include some reboots, delete profile etc
No luck with 7117, testing 7237 now
r
7237 has fixed some issues for me. But they don't have a timeline on it. Or so that's what I was told.
s
@Kasper Johansen with WS2016 u have tested? or only WS2019
k
@Salim Hurjuk as far as I know 2016 does not have search roaming issues. But only tested this reg. value with 2019.
s
Ok
k
I will try to do some more tests today
s
And the above CTX Article points to Citrix UPM - are u using Citrix UPM or FSLogix
k
I am using FSLogix, the article actually points to the Windows Search service WITH UPM, so I was just testing to see if that change also affected search roaming with FSLogix
s
Okay
6 Views
Open in Slack
PreviousNext
Powered by