BatchPatch Forums Home › Forums › BatchPatch Support Forum › Advanced multi-queue task delays
Tagged: advanced multi-queue
- This topic has 3 replies, 2 voices, and was last updated 3 years, 11 months ago by doug.
-
AuthorPosts
-
December 6, 2020 at 1:30 pm #12602T3KJVParticipant
Hi – I am using the advanced multi-row job queue sequence with 1,000 computers. My steps include:
1) adding 1000 host names
2) added a job queue task which is just 1) download and install updates and then 2)wait 10 minutes” to all hostnames.
3)created a “fake” host name to start the advanced multi-row queue execution via task scheduler.
4) the task scheduler starts and the first 100 machines get checked for WSUS updates.
5) PC #10 (for example) has 50 updates and it takes ~30 minutes to download and install. Once done the 10 minute timer starts and the job continues to the next 100 machines.All of this works great, except, everything is in limbo until a machine takes 40 minutes as described. Is there a way for me refine the advance multi-queue tasks so that, no matter what, the job kicks off every 10 minutes to my groups of, regardless of the state of the machines prior? thank you.
December 6, 2020 at 5:38 pm #12603dougModeratorHello – The entire purpose of the advanced multi-row queue sequence is to create a sequence where groups of computers are inter-dependent. It is designed intentionally to have one group only begin when the previous group is 100% done. From what you’re describing, it sounds like you don’t actually want to be using the advanced multi-row queue sequence at all. It sounds like you should be using scheduled tasks that kick off your groups at the specific times desired. So if you want the first 100 machines to start processing at 10PM, and then you want then next 100 to start processing at 10:10PM, followed by the next 100 at 10:20PM, then you should not use the advanced multi-row queue sequence. Instead create a scheduled task for each row to run that row at the desired time. Or… if you still really want to use the advanced multi-row queue sequence, you could create a separate sequence for each group of 100. Then have each sequence only contain a single position for that entire group of 100. In this way, each group of 100 is not dependent on any other group of 100. In this case you won’t actually be creating a “sequence” in the sense that nothing will be happening sequentially. But you’d be using the advanced multi-row queue sequence feature as just another way to schedule a group of 100 targets without applying the scheduled task to all 100 targets. Instead you would apply the scheduled task to the dummy row that starts the sequence, and it would then be responsible for launching the 100 members in the group. But each 100 members would be part of its own advanced multi-row queue sequence, and each 100 would get started independently of the others because each advanced multi-row queue sequence would have its own scheduled task to launch it at the desired time.
December 6, 2020 at 8:06 pm #12604T3KJVParticipantOkay, great, thank you for the reply. I did originally start with the scheduled task by time and, to be honest, I actually have closer to 5,000 PCs; I wanted to keep my example simple. Using the scheduled task required a lot of up front work, essentially creating 50 of them. I will try that again though. I am hoping I can set that up and then save the bps file in case of a crash or reboot on the host/licensed machine. Thanks again.
December 6, 2020 at 9:50 pm #12605dougModeratorYeah unfortunately I don’t think there is a better way to do what you’re trying to accomplish. Good luck.
-
AuthorPosts
- You must be logged in to reply to this topic.