MicrosoftHi - we've had issues with our Windows Server 2016 farm since the rollout of this version to our servers; Windows Search roaming now appears to be broken for many folks, and it is causing all kinds of logon issues that seem to get worse every day (this seems to point to repeated index corruption). Despite deploying the latest ADMX files, we continue to see that the Group Policy Management console views the RoamSearch configuration as an "additional registry key setting", despite the fact that I am able to configure it within the policy itself. This feels like something might be amiss with the policy to begin with...? Thank you for your attention to this.
