Managed to get a new version of PatchMaster ready for shipping, as version 1.4.

You can download it here on TechNet Gallery.

This one has several enhancements, that should make it more universally adoptable.

I realise that it will be nigh-on-difficult, to make PatchMaster an all-singing-all-dancing highly configurable tool that’ll meet everyone’s requirements; But I can get PatchMaster to meet most requirements, while going some way towards meeting in the middle for the more exotic needs out there.

We’ll go over what’s new using shots.

The Time Machine now has a cool picture that changes when you activate the Time Machine!

The Naming Bar has had some attention, you can now remove the Product button, but Classification has to stay on, or the total patches found and total patches processed will differ.

Rules can now be created that Include then Exclude. This is comma-delimited, so you can build up a long list of things you want to be processed, then begin excluding the wheat from the chaff such as Itanium, ARM64 et al. If you leave Include blank, the Include rule becomes unfiltered and everything is processed just as in V1.3 (Exclude was called Ignore Build in V1.3 and below).

The Available Patches tab has a new checkbox, which allows you to include SUM Maintenance automatically after a Build has completed. Disable so that you can run SUM Maintenance manually, or enable so that it is done for you whenever you perform a build.

And here we are, I’ve wanted to put in SUM clean up since day one, but time limits what I can do.

We now have SUM Maintenance, which removes ANY superseded update from SUG and Software Update Packages (SUPs, collides with Software Update Point, if you  see me say SUPs in reference to PatchMaster, it’ll be the Package not the Point). If a SUG is left empty it will be deleted whether it is a Reporting or Deployment SUG. Content is removed from SUPs but the SUP is not deleted, I will do this in a later version, for now you’ll have to manually delete the Package’s from the SCCM Console after several months of usage.

SUM Maintenance can be triggered post-build using the checkbox on the Available Patches tab.

To run SUM Maintenance manually select Find Superseded Patches, if any show click Remove Superseded Patches and monitor the Log tab (it should switch you there automatically).

SUM Maintenance will log to the Log tab (I will pour this into a log file soon …).

And finally, the page most people don’t click on! About!

I’ve put in a memory, and rewrote the text.

Oh and a top tip for usage, when this tool starts up for the first few times, while you get use too it, you need to look at the log tab, make sure its all working, especially review the output when you’ve done a Build, read it, and confirm what has happened in the SCCM Console.