This message was deleted.
# microsoft-fslogixs
Slackbot
05/17/2023, 6:03 AMThis message was deleted.
l
Leee Jeffries
05/17/2023, 10:39 AMThe search API changed from 2016 to 2019/2022.
Check out @James Kindon article here:
https://jkindon.com/fslogix-containers-search-index-considerations-and-troubleshooting/
Leee Jeffries
05/17/2023, 10:40 AMThats the original but has a caveat to read this one:
https://jkindon.com/windows-search-in-server-2019-and-multi-session-windows-10/#
Leee Jeffries
05/17/2023, 10:42 AMYour settings in FSLogix will probably still be multi-user search you'll want to disable this. Have a read though, should answer your issues.
r
Robert Berggren
05/17/2023, 10:44 AMHi Lee! I Thanks, but I know, I've read it all and are up to date on this. On this setup nothing with Fslogix settings regarding search roaming is configured, just left to the OS itself to manage.
l
Leee Jeffries
05/17/2023, 10:45 AMOh.... that is odd then. Perhaps all the details James has around troubleshooting will assist in nailing the problem.
j
James Kindon
05/17/2023, 10:49 AMI do not miss the days of chasing those ghosts around
r
Robert Berggren
05/17/2023, 10:58 AMIf I go the Citrix way with UPM and containers it's working. But Citrix relies on this: "To let the search index roaming feature work on Microsoft Windows 10 1809 and later, and on Windows Server 2019 and later, add a DWORD value EnablePerUserCatalog = 0 under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search". This reverts the search index to be the old way I guess and are probably not supported... This key and this with EnablePerUserCatalogFileIndexing = 1 with Fslogix and the index seem to work but not roam making it unusable. Even tried with the "old" Roam settings in Fslogix, to no avail.
j
James Kindon
05/17/2023, 11:16 AMIf it works it’s a win - user experience wins
👍 1
3 Views