Upon creating an automatic Software Update strategy in your organization, you will need to configure Automatic Deployment Rules.
This blog post describes in short Automatic Deployment Rules and how these are deployed to clients in different phases.
As with everything, it is easy once you understand it.
AUTOMATIC DEPLOYMENT RULES
Automatic Deployment Rules are used to automatically accomplish the following tasks:
- Filter out Software Updates according to a set amount of criteria from the database.
- Add the filtered out Software Updates to a Software Update Group
- Download the Software Updates to a Deployment Package
- Deploy the Software Update Group to a collection
As highlighted above, this blog post describes the deployment of the Software Update Groups using the Automatic Deployment Rule.
I have previously created a blog post which describes how to add multiple deployments for one Automatic Deployment Rule.
The different options that you can configure are defined by Micorosft here: https://docs.microsoft.com/en-us/sccm/sum/deploy-use/automatically-deploy-software-updates
This is what the Deployment Schedule page looks like in the Create Automatic Deployment Rule Wizard:
Above we can see that Available Time is 2 days. This means that after 2 days, the Software Updates will be available in Software Center on the Client.
Installation Deadline is configured for 7 days, which means that after 2+7 days, the Software Updates will be forcefully installed on the clients.
What you should take away from this is that the deadline is the sum of Available time + Deadline time.
I hope this short explanation can help someone!
- How To Install .NET Framework 3.5 on Windows Server 2012, Windows Server 2016 and Windows 10 968,507 views
- Issue with mounting new ISO files from TechNet in Windows 8 and Windows 8.1 Preview 63,986 views
- Solve SCCM Error “sending with winhttp failed; 80072ee7” in Windows PE 31,935 views
- Powershell: Script to set Outlook 2010/2013 signature using information populated from Active Directory 32,304 views
- How To Enable PXE in Hyper-V for Legacy Boot 109,458 views
- How to force specific sites to always run in Compatibility View using Group Policy 145,167 views
- How to change between a Full Installation (GUI) and Server Core in Windows Server 2012 64,345 views
- How To Solve WDS Issue with DHCP Port Conflict 12,350 views
- Hyper-V: Issue when starting virtual machine from downloaded ISO file 7,553 views
- How To Check Bitlocker Status using the Command Line 120,122 views
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell
What are Intel Modern Drivers for Graphics? https://t.co/h2d2GJOyJY #ConfigMgr
New blog post: How to deploy HP BIOS settings using SCCM and Powershell: https://t.co/JVKHBN86pN #sccm #configmgr #PowerShell
@miketerrill On topic of this, this might help with the initial clearing! https://t.co/2NnFlDU6lm @SCConfigMgr @modaly_it thank you for sharing
Friday #WaaS Tip: Record full Build Number Key during IPU. Helps support teams know which patch level was installed at time of upgrade to help correlate if any upgrade issues correspond to a specific patch level of the upgrade build. Blog Post Update coming soon (SetOSDinfo)3