Configure Profile Container to roam the Windows Search database

Windows Search is roamed for single user systems such as WVD Desktop, XenDesktop, or VDI. Search may also be roamed for multi-user systems such as WVD Applications, RDSH, XenApp. In multi-user systems, only the Outlook email search information is roamed.

Changes to enhance native search behavior in Windows Server 2019 and Windows 10 multi-session remove the need for FSLogix search functionality. FSLogix search functionality is not compatible with Server 2019, Windows 10 multi-session, and subsequent multi-session operating systems with enhanced native search capabilities.



The Windows Search Service is included with Windows. The Search Service provides search functionality for a user's files, Outlook email, and so on. The Search Service indexes all information to a single, system-wide database. When a user roams to another machine, all of the information that they expect to search must be reindexed on the new system. Reindexing has significant impact on CPU when a user logs on. Typically Search is disabled in environments where users roam between computers to avoid CPU impact.

Disabling local Search detracts from the user experience. Without local search, users are unable to search as they expect. If the search is sent to a remote server, performance is slow.

FSLogix provides two mechanisms to roam Search information, Single-user Search and Multi-user Search.

Description Supports multi-user systems Supports Outlook Supported Indexing Types Supported Environments
Single-user Search No Yes Yes Windows 7 and later, Windows Server 2008 R2 and later
Multi-user Search Yes Yes (2010 and later) No, Outlook only Windows 8 and later, Windows Server 2012 R2 and later


Single-user Search requires either Profile Container or Office Container be used. Multi-user Search may be implemented with Profile Container, Office Container or any other profile roaming solution.


If both the Profile Container and Office Container are configured, the database into the Profile Container VHD(X).

This feature allows roaming a user's Outlook Search information. This feature can be used on single-user (XenDesktop, VDI, and similar). Multi-user systems (RDSH, XenApp, and similar) are also supported, but only the Outlook email Search information is roamed.

Multiuser requirements and prerequisites

  • Install Windows Search
    • If Windows Search is installed after Microsoft Office, then the Microsoft Office installation must be repaired in Add/Remove Programs
  • Reboot the machine after RoamSearch is set to 2 as documented in Office Container configuration reference.
  • The Microsoft Office components that integrate with Windows Search are installed only if Search is installed before Microsoft Office. If Windows Search was installed after Microsoft Office, repair the Office installation in add/remove programs.

Multi-user configuration

To include the per-user portion of the Search Database in the Profile Container:

  • Set HKLM\Software\FSLogix\Apps (DWORD) RoamSearch = 2
  • Set HKLM\Software\FSLogix\Profiles (DWORD) RoamSearch = 2

To include the per-user portion of the Search Database in the Office Container:

  • Set HKLM\Software\FSLogix\Apps (DWORD) RoamSearch = 2
  • Set HKLM\Software\Policies\FSLogix\ODFC (DWORD) RoamSearch = 2

Force a search reset

To reset the user's database, use the frx reset-user-search-db command