You may have found yourself in a situation where you need to set up a System Center Configuration Manager (ConfigMgr) Software Update Management Strategy.
For example, you are tasked to set up a phased approach to deploying Windows updates to your Windows 10 devices. When you first start looking at this, it can seem like a daunting amount of manual steps to run through every month. We are going to show you how to automate the process to get some hours back in your day.
We want to make your life easier setting up Software Update Management over the next few blog posts. You will see how to go from zero to hero with automating a Software Update Management Strategy. We will be diving into automation using ConfigMgr and Microsoft PowerShell.
We will set up a phased approach to automating updates for Windows Workstations, Servers and Endpoint Protection definitions. The Automation will make patch cycles a simple task, not a Windows update hell.
Our Zero to Hero Automating ConfigMgr Software Update Management series breaks down into the following parts:
- Part 1: Introduction
- Part 2: Patch Management Strategy
- Part 3: Connecting to Configuration Manager with PowerShell
- Part 4: Create Configuration Manager Collections
- Part 5: Configure Software Update Point
- Part 6: Create Automatic Deployment Rules
- Part 7: Add Additional Deployments to Rules
- Part 8: Extending with Email notifications
- Part 9: Extending with PowerBI
This series uses Microsoft System Center Configuration Manager Current Branch. You may find that not all code works on older versions such as ConfigMgr 2012. The code uses improvements in ConfigMgr Current Branch such as changes to Automatic Deployment Rules. Please keep your ConfigMgr version in mind if you follow along.
In Part 2 we are going to look at the high-level strategies we will use for Software Update Management. We will give you a walk through of what you will have in place at the end of the series if you follow along.