Update Windows Deferral Settings
Purpose
The goal of the solution is to check and update the deferral feature update registries if any mismatch found using the NinjaOne platform.
Associated Content
Custom Field
| Content | Type | Available Options | Function |
|---|---|---|---|
| cPVAL DeferFeatureUpdates | Custom Field | Enabled, Disabled | This custom field is used to store the values for DeferFeatureUpdates. It contains two possible values: 1 = Enabled, 2 = Disabled. |
| cPVAL BranchReadinessLevel | Custom Field | 16, 32 | This field controls the Windows Update Branch Readiness Level. Select the appropriate channel to determine which feature update builds the device will receive. |
| cPVAL Feature Update Configuration | Custom Field | Disabled, Windows, Windows Servers, Windows Workstations | This Custom Fields Controls the Configuration of Feature update deferral on the machine based on the selected operating system. Choose Disabled to skip applying this setting to the current Client, Location, or Computer. |
| cPVAL DeferFeatureUpdatesPeriodInDays | Custom Field | 0-365 | Specifies the number of days to defer Windows feature updates. Accepts values between 0 and 365 days. |
Automation
| Content | Function | Type |
|---|---|---|
| Update Windows Deferral Settings | Controls the Windows Update deferral configuration for the device, including feature update servicing channel and deferral period. These settings determine when feature updates are made available after release. | Script |
| WinUpdate Deferral Audit | Reads current Windows Update deferral registry values and compares them against Ninja Custom Field desired values. Exits with 1 if drift is detected. | Script |
Compound Conditions
| Content | Function | Type |
|---|---|---|
| Feature Update Defer Configuration Workstations | Triggers the Automation: WinUpdate Deferral Audit and if the drift equal to 1 then it run the automation Automation: Update Windows Deferral Settings on Windows Workstations to update the registry values. | Compound Condition |
| Feature Update Defer Configuration Servers | Triggers the Automation: WinUpdate Deferral Audit and if the drift equal to 1 then it run the automation Automation: Update Windows Deferral Settings on Windows Servers to update the registry values. | Compound Condition |
Implementation
Step 1: Create the following Custom Field
- Custom Field: cPVAL DeferFeatureUpdatesPeriodInDays
- Custom Field: cPVAL DeferFeatureUpdates
- Custom Field: cPVAL BranchReadinessLevel
- Custom Field: cPVAL Feature Update Configuration
Step 2: Import Automation Scripts
Import the following automation scripts:
Step 3: Configure the following Compound Conditions
Create three compound conditions targeting the appropriate device policies:
- Compound Conditions: Feature Update Defer Configuration workstations
- Compound Conditions: Feature Update Defer Configuration servers
FAQ
Q1: What is the purpose of this solution?
A: It ensures Windows feature update deferral settings are applied consistently on all managed devices. The solution audits registry values and updates any mismatches based on the NinjaOne custom fields or variables.
Q2: Which devices are affected by this solution?
A: Both Windows Workstations and Windows Servers are supported. Separate compound conditions ensure the correct settings are applied for each device type.
Q3: How is the desired configuration defined?
A: The desired values are stored in NinjaOne custom fields:
- cPVAL DeferFeatureUpdates
- cPVAL BranchReadinessLevel
- cPVAL DeferFeatureUpdatesPeriodInDays
Q4: What happens if the current registry settings already match the desired configuration?
A: The audit script will detect no drift, and the update script will not run, avoiding unnecessary changes.
Q5: Can this solution be customized for different update channels or defer periods?
A: Yes. You can configure the branch readiness level and defer period in the respective custom fields for each device or client.
Q6: How do I verify that the solution has applied correctly?
A: You can run the WinUpdate Deferral Audit script manually to check if any drift is detected. Logs and audit results can be reviewed in NinjaOne Activity Logs.
Q7: Will this solution interfere with other Windows Update policies?
A: No. It only modifies feature update deferral settings and respects the configurations defined in the NinjaOne custom fields.
Changelog
2026-03-06
- Initial version of the document