Here in his post, we will help you in understanding how to Configure Registry Processing Policy using Intune. We will apply this policy using Intune’s Configuration Profiles. Our main purpose here is to help you in acquiring knowledge of how to Configure Registry Processing Policy Using Intune.
Configure Registry Processing Policy Using Intune policy controls the update behaviour of registry policies. It applies to all policies in the Administrative Templates folder and other policies that store values in the registry. It supersedes any customized settings made by the program implementing a registry policy during installation.
When this policy setting is enabled, you can use the provided checkboxes to modify the options. If you choose to disable or not configure this policy setting, it will not impact the system.
The “Do not apply during periodic background processing” option prevents the system from updating affected policies in the background while the computer is in use. If background updates are disabled, policy changes will only take effect upon the next user’s logon or system restart.
The “Process even if the Group Policy objects have not changed” option updates and re-applies policies even if there have been no changes to them. Many policy implementations specify that they are only updated when changes occur. However, enabling this option allows you to apply unchanged policies, which can be useful for reapplying desired policy settings in case a user has modified them.
- Let Apps Access Background Spatial Perception Policy using Intune
- Prevent Device Metadata Retrieval from Internet Policy using Intune
Windows CSP Details CSE_Registry
We will see Windows CSP Details for this Policy setting CSE_Registry. Registry policy processing is one of the essential parts of Group Policy in a Windows environment. With the help of this, administrators can define and enforce specific configurations on computers and users through the manipulation of registry settings.
This policy setting can be very useful in environments where standardized configurations are critical. It helps in maintaining consistent settings across multiple machines, even if users have attempted to modify them. This policy is applicable on both OS i.e. Windows 10 and 11.
CSP URI – ./Device/Vendor/MSFT/Policy/Config/ADMX_GroupPolicy/CSE_Registry
Configure Registry Processing Policy using Intune
To set Configure Registry Processing Policy Using Intune, follow the steps stated below:
- Sign in to the Intune Admin Center portal https://intune.microsoft.com/.
- Select Devices > Windows > Configuration profiles > Create a profile.
In Create Profile, I select Windows 10 and later in Platform and select Profile Type as Settings catalog. Click on Create button.
| Platform | Profile Type |
|---|---|
| Windows 10 and later | Settings Catalog |
On the Basics tab pane, I provide a name for the policy as “Configure Registry Processing Policy.” Optionally, if you want, you can enter a description for the policy and then proceed by selecting “Next.
Now in Configuration Settings, click Add Settings to browse or search the catalog for the settings I want to configure.
In the Settings Picker windows, I searched for the keyword Registry Policy, and among many, I found the category Administrative Templates\System\Group Policy and selected this.
When I select that option as stated above, I see one sub-category, Configure registry policy processing. After selecting that, click the cross mark at the right-hand corner, as shown below.
Now, after enabling Configure Registry Processing Policy in the Administrative Templates, two additional settings will appear:
- Do not apply during periodic background processing (Device)
- Process even if the Group Policy objects have not changed (Device)
Both of these need to be set as false, as shown below in the image.
Using Scope tags, you can assign a tag to filter the profile to specific IT groups. One can add scope tags (if required) and click Next to continue. Now in Assignments, in Included Groups, you need to click on Add Groups, choose Select Groups to include one or more groups, and click Next to continue.
In the Review + Create tab, I review settings. After clicking on Create, changes are saved, and the profile is assigned.
Upon successfully creating the “Configure Registry Processing Policy,” notification will appear in the top right-hand corner, confirming the action. You can also verify the policy’s existence by navigating to the Configuration Profiles list, where it will be prominently displayed.
Your groups will receive your profile settings when the devices check in with the Intune service. The Policy applies to the device.
Intune Report for Configure Registry Processing Policy
From Intune Portal, you can view the Intune settings catalog profile report, which provides an overview of device configuration policies and deployment status.
To track the assignment of the policy, you need to select the relevant policy from the Configuration Profiles list. By reviewing the device and user check-in status, you can determine if the policy has been successfully applied. If you require more detailed information, you can click on “View Report” to access additional insights.
Intune MDM Event Log
To verify the successful implementation of String or integer policies on Windows 10 or 11 devices through Intune, you can leverage event IDs 813 and 814. These event IDs provide valuable insights into the application status of the policy as well as the specific value assigned to the policy on those devices. In the case of this particular policy, the value is String and is linked to the event ID 814.
By analyzing these event IDs, you can gain a clear understanding of the policy’s application status and the corresponding value associated with it on the devices in question.
To confirm this, you can check the Event log path – Applications and Services Logs – Microsoft – Windows – Devicemanagement-Enterprise-Diagnostics-Provider – Admin.
MDM PolicyManager: Set policy string, Policy: (CSE_Registry), Area: (ADMX_GroupPolicy), EnrollmentID requesting merge: (1A661A16-302C-46D4-81F0-AA73244850D8), Current User: (Device), String: (<enabled /><data id=”CSE_NOBACKGROUND10″ value=”false” /><data id=”CSE NOCHANGES10″ value=”false” />), Enrollment Type: (0x6), Scope: (0x0).
So when I open the above Event log, I found that the policy I have applied to the device it is successfully implemented. By reviewing the log entry shown in the above image, the Event Viewer, I came across essential information, including the Area and Enrollment ID. These details play a significant role in identifying the corresponding registry path. To locate the specific information, please consult the table provided below:
| Area | Policy | String | Scoped | Event ID |
|---|---|---|---|---|
| ADMX_GroupPolicy | CSE_Registry | Enabled | Device | 814 |
The details presented in the table above for the Configure Registry Processing Policy Using Intune can be employed to access the registry settings that hold the group policy configurations on a specific computer. To accomplish this, you can execute “REGEDIT.exe” on the target computer and navigate to the precise registry path where these settings are stored.
- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\providers\1A661A16-302C-46D4-81F0-AA73244850D8\default\Device\ADMX_GroupPolicy
When you navigate to the above path in the Registry Editor, you will find the registry key with the name CSE_Registry. Also, when I navigated to the above path, I saw that the Registry Key is created, but there are two values associated with it which are as follows:
- <data id=”CSE_NOBACKGROUND10″ value=”false” />
- <data id=”CSE NOCHANGES10″ value=”false” />
And both of these are set to False as we set them previously while configuring in Intune Portal.
| Registry Name | Value |
|---|---|
| CSE_Registry | Enabled |
Author
Abhinav Rana is working as an SCCM Admin. He loves to help the community by sharing his knowledge. He is a B.Tech graduate in Information Technology.