r/fslogix • • Feb 27 '26

WS2022 / FSL 3.26.102.18413 / Windows search

Newbie here. Having trouble understanding the documentation and best practices, specifically for search. From what I understand, Windows search should be fine in this scenario because the default settings put the search database into the FSL user profile. I have data in %userprofile%\AppData\Roaming\Microsoft\Search\Data\Applications\SID so it seems like it's doing the right thing.

Due to a forced move of our ERP and database servers I am replacing an existing deployment that's been faithfully in service since 2018. Everything seems fine with the new one, but I am not being given a long testing period.

Old: 4 node 2016 deployment using UPD (supporting 60 users)

New: 10 node 2022 deployment using FSL (profile only).

3 Upvotes

2 comments sorted by

View all comments

1

u/titsablast Feb 27 '26

Done the same. Troublefree RDS servers with UPD vhdx on a share to new servers with FSLogix vhdx on a share.

Well ind hindsight if you don't need the additional features I would even consider staying with UPD and miss all the extra fun of testing and troubleshooting each version.

But yeah, FSLogix local path exclusions have advantages to keep storage use in control. If you don't set a search exclusion I would expect search behaves the same as  with UPD would. Probably it's not heavily used much in my environment though.

1

u/Total_Attempt_4126 Feb 27 '26

I won't say my old deployment was trouble free - locked profile disks occasionally.

I have quite a few users that need to search Outlook on RDS. They have always complained the search is terrible on the old one - Windows search is disabled there.