question

AndyS-8334 avatar image
0 Votes"
AndyS-8334 asked ThomasT-6977 commented

FSLogix - Correct Search Configuration

With the release of FSL 2201, specific to a Windows 10 multi-session environment in Azure: "Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems", what is the correct configuration to accomplish this?

MS appears to have outdated documentation regarding the fixes in FSL 2201: https://docs.microsoft.com/en-us/fslogix/configure-search-roaming-ht#configure-multi-user-search

According to bloggers, RoamSearch should be ZERO in order to get Search to function, therefore shouldn't the following GPO settings be configured this way:

FSLogix > Enable search roaming > Disabled
FSLogix/Office 365 Containers > Store search database in Office 365 container > Disabled
FSLogix/Profile Containers > Store search database in profile container > Disabled

Are those settings correct, and are there any other settings missed to accomplish what is mentioned in FSL 2201 to configure Search correctly?

windows-server-fslogix
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I've been trying to figure this out as well. When I first set up FSLogix the guide I was following said to Enable "Store search database in profile container" and set it to Disabled for a 2019 server. Looking at the Reg Key this effects on my servers it is set to Zero. But If I look at the actual contents of the Profile VHD it does contain the Search edb file. And this is on a brand new profile.

But some updated documentation or even a statement that says, FSLogix 2201 ignores this setting or something would be great.

1 Vote 1 ·

Can anyone from Microsoft verify this information please?

0 Votes 0 ·
  • would also like to know

0 Votes 0 ·

0 Answers