This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 51%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
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://learn.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?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 10%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMJ%3C/text%3E%3C/svg%3E)
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.
Can anyone from Microsoft verify this information please?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 87%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETT%3C/text%3E%3C/svg%3E)
+1 would also like to know
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 63%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECJ%3C/text%3E%3C/svg%3E)
I've been testing this today and that appears to be the correct way. You also need to enable the Windows search service (which we would typically disable). The edb files are then stored in the profile container and roamed automatically with the user.
Since Server 2019 (Windows 10 multi user), Windows Search support per-user search indexes, thus enabling search roaming is not advised.
Only until server 2016 this was required. I have set up an amount of RDS environments including windows 10 multi user (AVD).
Article:
https://learn.microsoft.com/en-us/fslogix/configure-search-roaming-ht
Quote:
FSLogix 2201 and newer do not allow FSLogix Search roaming on versions of Windows that natively provide per-user search indexes. Per-user search indexes are natively supported by Windows Server 2019 version 1809 and newer, as well as all versions of Windows 10 multi-session and Windows 11 multi-session.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 60%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
I'm having major delays in logging off and on my FSLOGIX profiles on Server 2022 RDSH farm saying it's waiting for Windows Search and Outlooks keep crashing and freezing and I've ran the frx list-redirects command as I've found in another post but I can't see the search has been redirected ? I have search roaming enabled along with storing the search database in the profile container only (and I've tried it in the O365 container only as well)
Are we saying that that we should disable search roaming and storing the search databases in FSLOGIX on Server 2022 ? I've got version 2.9.8228 of FSLOGIX by the way so I'm assuming that's 2201 or later ?
Search roaming may not be enabled. It is multiuser by default in the userprofile as from server 2019.
Make sure you set RoamSearch to 0 if not done already.
Just enable windows search and make sure to set RoamSearch to 0 if you have enabled it before.
That should suffice to make this work.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 50%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Thanks DirkHaex,
The question still stands from the original poster.
Should we set each of these policies to these settings in the FSLogix gpo. At some point before some of us may had some policies that were different. Setting these this way would ensure that we have it set correctly?
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
Thanks
This really depends on the environment you are managing. If you are unsure of previous configurations (easily checked through registry), you should apply all neccesary settings via GPO).
If you however, are building a greenfield environment only consisting of 2019+ server version, there is no need to specify this.
@Dirk Haex specific to my original question, and also relating to Server 2019+ (Server 2022 in this new customer instance), from the MS article, "Changes to enhance native search behavior in Windows Server 2019 version 1809 and Windows 10 multi-session remove the need for FSLogix search functionality. FSLogix search functionality is not compatible with Server 2019, Windows 10 Enterprise multi-session, and subsequent multi-session operating systems with enhanced native search capabilities."
Therefore, my GPO settings I mentioned above would achieve RoamSearch=0, are all the following settings 100% correct to accomplish this for Server 2019/2022?
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