There as several ways to achieve a Windows desired state configuration baseline and several approaches. Windows gecko is built upon the requirement to provide a default configuration baseline, or a desired state configuration, and is not meant to stop the end user to install a previously removed app, or circumvent a desired setting, purely to allow device administrators to provide a default baseline, or corporate baseline, to the end user as part of a Windows Autopilot scenario.

The goal of Windows gecko is to provide a consistent desired state configuration to end user devices in Windows Autopilot scenarios.

The mindset of the solution will aim to allow to limit and/or combine the functionalities best suited for the task, meaning if Windows feature configuration were to be applied, this should be achievable without the Windows Registry configuration. Also, very important, is to be able to apply Windows baselines configuration in one or multiple packages in either system or user context, without changing the code – which is why all configurations is achievable using configuration files (json). This will help ensure minimal effort to create a new Windows desired state configuration, being easily completed without any code changes or re-signing the provided code.

Source: https://github.com/dotjesper/windows-gecko/

Target Audience: This session is intended for IT administrators, system engineers, and Windows deployment specialists who are responsible for managing and maintaining Windows environments within their organizations.
Attendees should have a basic understanding of Windows Autopilot scenarios and familiarity with Windows feature configurations. This session will be particularly beneficial for those looking to streamline their desired state configuration processes and minimize manual efforts in deploying and maintaining consistent configurations across end-user devices.