The first thing I will do for my users is blocking the “ First run wizard“. Configure the Intune policies Disable First run wizard Settings which could be done easily with GPO`s, but before ADMX-backed policies couldn`t be done with Intune. In this blog I will show you some examples of policies to manage Internet Explorer settings with Intune on a MDM managed device. When the MDM policy is referenced, this metadata is referenced and determines which registry keys are set or removed. Windows maps the name and category path of a GPO to a MDM policy area, and policy name, by parsing the associated ADMX-file, finding the specified GPO, and storing the metadata in the Policy CSP. Each setting in an administrative template corresponds to a specific registry value. Each administrative template specifies the registry keys, and their values, that are associated with a GPO and defines the policy settings that can be managed. In an ADMX-backed policy, an administrative template contains the metadata of a GPO. Starting with Windows 10, version 1703, the Policy CSP can now also handle ADMX-backed policies.
With those new MDM policies we are able to set a lot of policies using Policy CSP and with the Fall Creators Update (version 1709) even more settings are added.Ī good, short explanation of what ADMX-backed policies are I found on Peter van der Woude his blog: Fortunately Microsoft introduced ADMX-backed policies in the Windows 10 Creators update (version 1703). In the past, Intune was only able to deploy a predefined set of device settings to MDM managed Windows devices.
0 kommentar(er)
