As most of you know, last week brought us Microsoft’s Patchocalypse, where we became Microsofts test subjects for their new patching bundle. And this week we’re asking how you liked it?
Microsoft’s new patch bundle was their idea to make the patching process more streamline and simpler for the average user. No more individual patches that you had to sift through to determine which ones you wanted and which ones seemed like a complete waist of time. Now they all come as one. And for most, this is a much cleaner and user friendly process.
There are some drawbacks though. In the past, if a patch decided to not play nice with the machine, all I had to do is go back and roll back that particular patch. And I had the choice to NOT patch singular features or applications that I knew would have issues with a particular patch number. I could just “Skip” them. But now, under the new bundle, I’m forced to rollback the entire bundle (ALL the patches). This leaves me unable to patch vital components with the Critical patches, because of a single patch somewhere else.
So, in the end, does it do what it was meant to do? For the most part, Yes, it does. It streamlines their process for pushing patches to their users. Does it fulfill the basic needs of security options in the patching process. Yes and No. Yes in the sense that it adds patches to everything across the board for best practices, and no, because you’ll lose ALL patches in the event just one of those patches has an issue.
So far, we’ve had NO issues.