This message was deleted.

Import this classic adm template file to fix the removed parameters aka "Extra Settings"

Does that mean the RoamSearch is no longer a utilized setting? and how does one "import".. just copy it into PolicyDefinitions folder with a custom name?

RoamSearch is still used, but it has some smarts behind it now in the later releases for Multi-Session. Reading material https://learn.microsoft.com/en-us/fslogix/reference-configuration-settings?tabs=profiles#roamsearch

So since we're running FSLogix on 2019 RDS servers.. should RoamSearch be set to "Disabled" or "Enabled: Disabled"? I'm not even sure it matters.. but the GPO says "Dont use this on newer systems"

To use FSLogix search roaming functionality, you must be using one of the following versions of Windows:
Windows Server 2012 R2
Windows Server 2016
Windows 10 (prior to 1809)

https://learn.microsoft.com/en-us/fslogix/how-to-configure-search-roaming

Also, to reply to your question about disabling it. MS states this. In the same link @Jonathan Pitre posted too. "FSLogix detects the new per-user Windows Search and automatically disable any FSLogix functionality. If you're using FSLogix on these operating systems, you should disable the FSLogix settings that enable search roaming. You should also enable the Windows Search service on these operating systems to allow per-user search indexes to be created and stored in the user's container."

Alright, so same question.. do you DISABLE the GPO setting or set it to Enabled: Disabled? I'm not sure if the end result is the same either way but want to do it correctly

disable just in case, you don't need it anyways

Okay I'll just change to straight "Disabled" vs using Enabled with sub-cat Disabled. How it looks currently just for show:

yeah disable all extra parameters

Do they conflict with the FSLogix GPO settings? i.e. if one is Enabled and the "classic" is disabled?

"Extra Settings" are registry values that were removed from the original policy definitions templates after an update. They are essentially deprecated settings.

I thought they were depreciated as well but when I open the GPO I see the settings present. I'm not sure which update this occurred on as I just noticed it. If I create a new GPO, the settings work and it can read them but if I toggle the settings off and on in the existing GPO, some of them get fixed and some remain as "extra registry" settings. I have screen shots below. I'm actually in the process of creating a new GPO to fix these as it's the only way I could find to fix it so far. I use this GPO as a template for deployments and when I imported into my last customer, it was broken there and that's how I originally noticed the issue. Let me know if you guys have another way to fix it. I've tried rolling back the .admx files as I have backups of at least 3 different versions going all the way back to Jan of 2023 and none of them fixed it either. The first screen shot shows the "Extra Registry Settings". The second one shows when you edit it, the setting is present. Also, in the second screenshot you can see I tried to toggle "Roam Search" to "Not configured" and it still reports it as an "Extra Registry" setting. I found some of them if I set them to "not configured" and then enabled/disabled them, it would resolve and read the setting. It just depended on the setting. I could not get "Roam Search" fixed at all. I decided to create a new GPO and viola it's works just fine. I've never seen this before. I have a third screenshot showing the new GPO and the setting being read successfully. Somethings wrong here... lol.