- This topic has 4 replies, 2 voices, and was last updated 5 years, 1 month ago by .
-
Posts
-
New to BatchPatch and just looking to see if it is possible to require the order of installation for Microsoft patching? Like having patch A install before patch B, C, and D.
Thanks in advance
If a computer has multiple updates ready for installation, it’s the Windows Update Agent on that computer that handles the order that the updates are installed. BatchPatch doesn’t control this when using it normally, and generally this isn’t something that you need to worry about. You should let the Windows Update agent install the updates in the order that it chooses.
However, if you *really* wanted to control the order that the updates are installed, then you could use BP to install only one specific update at a time (using the graphical or textual filter), and then just repeat the installation process one time for each desired update. Or you could download the KBs manually and use the deployment feature in BP to deploy each KB sequentially. But again I wouldn’t recommend doing either of these things. I would recommend just letting the Windows Update Agent handle the ordering.
-Doug
There are multiple ways to automate the process in BatchPatch, but automatic isn’t always better. Automating things can require testing etc to make sure it works as desired, and this isn’t always going to be quicker/simpler, but that’s up to you.
Possible ways to accomplish the task:
1. Instead of a one-step operation to install all updates, you could use a two-step operation where as your first step you install the servicing stack update, and then once you have successfully performed this step, then as your second step you install the remaining available updates. You can use the graphical or textual filter in BatchPatch on the first operation to make sure that only the desired servicing stack update is installed. Then for the second operation you could clear the filter so that all remaining updates are installed. This method would not be 100% automatic. It would require that you set the filter for all rows to include only the servicing stack update, then launch the installation process for the servicing stack update on all target computers. Then when done, clear the filter and launch the update process for all remaining updates.
2. You could follow the same concept as described in option 1 above, but instead of two separate manual operations in BatchPatch, you could link together the two operations into a single operation using the advanced multi-row queue sequence. You would create two rows for each target host in the grid. One of the rows would be for installing the servicing stack update with the textual filter applied, the other row would be for installing all remaining updates with no filter applied. Then the advanced multi-row queue sequence would enable you to ensure that the row that installs the servicing stack update is executed before the row that installs the remaining updates.
advanced-multi-row-queue-sequence-video-tutorial
3. You could create a manual deployment in BatchPatch for the servicing stack update. You would have to download the desired KB from Microsoft, and then create a BatchPatch deployment with that KB. You could then setup a regular job queue that first executes the deployment and then subsequently executes a Windows update download/install operation to install the remaining available updates.
4. You could use scheduled tasks for everything. In this case you would create two rows for each target computer, similar to option number 2 above where one of the rows is for installing the servicing stack update (with a textual filter applied to that row for that purpose), but instead of using the advanced multi-row queue sequence to ensure that the servicing stack row is executed first, you could use two scheduled tasks (one for each row) to schedule the servicing stack row to execute 15 minutes before the row that handles all the remaining updates.
- You must be logged in to reply to this topic.