none
Windows Server 2019 RDSH correct roamsearch configuration RRS feed

  • Question

  • I test a new Windows Server 2019 RDSH environment with Office 2019 profile and office container configuration.
    I am having a hard time with the correct roamsearch configuration.

    I've configured in GPO
    Store search database in Office 365 container: enabled: multi-user seach and store search database in profile container: enabled: multi-user seach

    The following registry keys are there and created for users who log in:

    [HKEY_LOCAL_MACHINE \ SOFTWARE \ FSLogix \ Profiles]
    "RoamSearch" = dword: 00000002

    [HKEY_LOCAL_MACHINE \ SOFTWARE \ FSLogix \ Profiles \ Sessions \ <UserSID>]
    "RoamSearch" = dword: 00000000

    Is this the correct configuration for Windows Server 2019 environment?

    Thursday, October 15, 2020 10:31 AM

All replies

  • No it's not.

    https://docs.microsoft.com/en-us/fslogix/configure-search-roaming-ht

    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.

    That being said, search roaming is broken on Windows Server 2019. There are a couple of workarounds. See the topics here or follow this post: https://jkindon.com/2020/03/15/windows-search-in-server-2019-and-multi-session-windows-10/

    Friday, October 16, 2020 7:49 AM