ADR for Windows Feature Update
Create an Automatic Deployment Rule
From the console, navigate to Software Library ► Software Updates ▶︎ Automatic Deployment Rules.
You may need to further expand the Automatic Deployment Rules node if it's necessary to pick a specific folder.
Click the Create ADR button in the ribbon to start the wizard.
Make sure to prefix the ADR Name with your Official Department Code.
General
Select the collection you would like to deploy this update to and make sure "Add to an existing Software Update Group" is selected otherwise this will generate a new SUG every time the rule runs and finds new updates.
This process may not work to upgrade collections with unsupported Windows versions. Some systems may need to be manually upgraded or re-imaged.
Deployment Settings
Required or Available?
The choice is up to you. Required means that if the upgrade is applicable the endpoint will install it. Available means the upgrade will be visible in Software Center however it will require user interaction to install it. For an automated approach, required would be the desirable choice.
Property and Search Criteria
Check Product, Superseded, Title and Update Classification.
Click on <items to find> in order to set your criteria.
Architecture = x64
Product = Windows 11
Superseded = No
Title = 25H2
Updated Classification = Upgrades
Product and Title listed above are examples, be sure to change accordingly for future versions.
Once you have set all the necessary search criteria, click on Preview to verify which updates would be selected and verify that your search criteria is correct as it should lead to only one upgrade.
Example:
Evaluation Schedule
The default schedule should not be used. The Software Update Point synchronization is configured to run every 6 hours.
Choose a schedule appropriate for deploying the updates you're interested in. In this particular case change the schedule to monthly and it should be set to a time after Microsoft publishes updates such as the afternoon.
Schedule
If you want updates to be seen out as soon as you finish creating this deployment, then choose "As soon as possible" for both the available time as well as the deadline.
When will it install?
As soon as possible, does not necessarily mean this update will install across your fleet as soon as you complete the wizard. There are various factors such as whether this was create as required or available, your Maintenance Window or the User Experience in the following step.
User Experience
These settings may be configured depending on what you selected (Required or Available) as well as the experience you want users to have.
For example, if you made this an "available" update, then you will not want to hide it. Set the other behavior options as desired.
Alerts
The default generates an alert when the rule fails. You can uncheck or even set an alert for compliance.
Do not set any alerts for Operations Manager.
Create Deployment Package
This part is both unique to and important to Microsoft updates.
Select No deployment package.
Download location
Set Deployment options to Download. The metered internet setting is up to you, however it may result in higher charges for an enduser using a hotspot (metered connection).
Summary
Verify everything looks good before completing the wizard.
Related Information
-
-
-
Creating a Custom ADR and deploying the SUG (Endpoint Management)
-