I’m at the tail-end of the development of PatchMaster to bring it up to version 1.5.
The driver for this code release was silent running mode, headless mode. And instead of releasing once done, I kept the project back longer than I normally do, several weeks in fact, so that I can return to the code here and there to tweak, finesse and add in more features. It has worked out quite well, things I would have tutted over post-release are getting handled.
Here’s what is already coded and fully working:
And I’m just finishing up with this:
July mentioned because I’m testing … it is June’s content
Some great suggestions from Philipp Buchwald on my blog for PM, thanks a lot Philipp you rock! While out in the USA for MMS 2018 I met Josh, who also rocks, and uses PM like a boss!
I know there are quite a few of you out there using this tool, almost all of my active customers are using PM, it doesn’t have to be all of you, some of you already have scripted solutions, or rely on ADR’s and manually handle the out of cycle releases which are frequent not infrequent.
With PM patching goes from a chore to a button click, matters not if it is patch Tuesday, taco Tuesday or titanic Thursday, when patches are released PM introduces them into your environment seamlessly, all you need to do is raise a change control to track them going through your system, as it should be, and then kick back and monitor the show using the provided reporting Software Update Groups. With PM, you can liberate lots of back-end time, and project it forwards to the client-end, troubleshoot them, bring compliance up.