Patch Tuesday ADR Process/Question

[RLC-Andrew]

I have a Patch Tuesday ADR than runs late in the day EST on the 2nd Tuesday of each month.  This ADR grabs all the various update classifications I selected (critical, security, Service Packs, Update Rollups, Updates) for the "Last 1 Month".  The "Last 1 month" is a hard coded setting from the drop down box.  It downloads all the updates that match the criteria and last 1 month into my deployment package, and then creates a new software update group.

I'll ask this question first:  Is this generally how most have this set up for the patch Tuesday process?

 

[itrider]

I typically have them check every day for clients (servers have their own policies).   This is what I have setup.  I add the "custom severity - none" option so that if there is a patch released that needs to be blocked, I can change that field on each individual patch to block it.  Much easier and cleaner.  Here aremy properties.

[YPCC]

2 months sounds about right. Although that assumes your clients are all patched to a level within 2 months release

[RLC-Andrew]

When I set this up years ago, all updates that were available were put into one of the "Base Set of Updates" groups and an underlying associated deployment package.  So these hold mostly old updates at this point, as I do not add to them.

Each month, the Patch Tuesday ADR described in my original post runs and create a new group (Patch Tuesday - 2019-01-18) as last months example.  As it stands now, this group contains anything released or changed in the last month.  This Group that is created is deployed to the various collections (Test Groups, Servers, Workstations etc.)

Every few months, I move the updates contained in those ADR monthly groups into the "Yearly - Current Year" group to keep things cleaned up.

I set this up based on some published instructions that were available online at that point in time (2015).  I was curious if anyone had setup a similar style for the patching process.