Windows Server 2019 not allowing me to use Indexing when Remote Desktop Session Host is enabled

Mitch 1 Reputation point
2020-08-27T12:04:15.853+00:00

Hi There,

Can't find much on the internet after doing various searches so have created an account to attempt to find a solution.

I'm having an issue where when I enable the feature Remote Desktop Session Host it doesn't allow me to select the C:\ drive as a indexing option. This is needed for our customers as we do a remote hosting solution so we would need mass people connecting on to a single server at any one given time.

With the feature above disabled (can have all of the other RDS turned on) we can index the main drive (this is on a test server for 2019) but when we enable this feature it then disables the main drive from being able to be indexed.

We are currently using an older version of Windows Server as we are able to have all the RDS services enabled and have indexing on (We use all of the RDS installed except from the RD Virtualization Host) but we want to eventually move to Windows Server 2019.

TLDR:

I'm having an issue where when i enable the RDS service 'Remote Desktop Session Host' it disables the ability to index the C:\ drive. I have the rest of them enabled (besides Virtualization Host as not needed) and they don't cause issues.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,283 questions
{count} votes

10 answers

Sort by: Most helpful
  1. Jon Hardman 1 Reputation point
    2020-10-11T03:14:10.627+00:00

    Happening here too. RDSH seems to break indexing. Service still runs. Help please.

    0 comments No comments

  2. Callum | ☁ Cloud10 1 Reputation point
    2020-12-21T16:35:13.087+00:00

    Anyone have any idea what KB it is which breaks this?

    0 comments No comments

  3. JK12 1 Reputation point
    2021-01-19T22:04:47.703+00:00

    Any update on this? Seems a bit ridiculous indexing does not work on a server using RDP.

    0 comments No comments

  4. magriii 1 Reputation point
    2021-02-12T12:16:04.767+00:00

    Any news on this topic?
    We'd like to migrate 2012 RDSH servers to 2019, but indexed search for local content is essential.

    0 comments No comments

  5. Steve3513 0 Reputation points
    2024-02-07T17:37:22.69+00:00

    This behavior is by design in Server 2019, and beyond, when the RDSH role is installed. The RDSH Role “breaks” the indexing service.   The fix is located here: https://www.ajni.it/2021/04/fix-search-indexing-on-rds-server-2019-and-probably-2016/ If you have users complaining about incomplete search results on RDS Server 2019, especially in Outlook, this registry key might fix the problem. It did fix mine. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search DWORD EnablePerUserCatalog 0 Restart the Windows Search service. This will create the index database under C:\ProgramData\Microsoft\Search\Data\Applications\Windows rather than in the user’s AppData folder.

    0 comments No comments