Multiple jobs/deployments on devices

[ExhaustedTech]

Currently, I have tabs designated for each specific job queue I’m trying to run or software I’m installing on hosts. If I have a device in multiple tabs because they’re offline and I’m waiting for them to come online, the job queues end up erroring out because they are stepping on each with trying to install programs simultaneously.
I tried using the Task Scheduler to have it run multiple jobs but multiple jobs do not work with the “Run task immediately upon detecting host online.”

Other than creating one massive job queue with all of the steps for all 5 deployments, what would be the best way to go about this? The multi-row sequencing looks to be used for when a deployment depends on completion from other hosts but that’s not what I’m trying to do, it’s all on the same host. I just need the jobs to run one at a time when the host does come online so they don’t interfere with each other.

[doug]

I know you said “Other than creating one job queue…” but I don’t understand why you’re looking for a different way. The way to handle this is with a single job queue that contains multiple deployments.

While the advanced multi-row queue sequence could actually also be used for this, it would just add additional complexity over the singular job queue method. To do the advanced multi-row queue sequence you would have to put put each row into a single grid (each row in the sequence would have the same host name, so you’d have multiple rows each with the same host name, and they’d have to go into the same grid because the sequence works in a single grid, not across grids), and then you would have to assign a different sequence position number to each row. Effectively, it would create the same result as putting all of the deployments into a single job queue, but it would do it with more complexity.

[ExhaustedTech]

Each install I have already sits in a job queue with 10-20 different items. If I created one massive one, it would have 20-100 lines for one device and it would be a significant amount of work to be used just one time. I already have my job queues created for each deployment, I was just hoping to be able to say- apply each of these job queues to a host one at a time, when the host is online, as that would be much more effective and efficient. It’s ok, I’ll just do them manually as they come online as that would more efficient and less time consuming than the advanced multi-row or setting up one job queue that houses multiple smaller job queues.

Appreciate the confirmation I wasn’t missing something simple!

[doug]

In that case, one other thing to consider is the basic multi-row queue sequence instead of the advanced. All rows still need to be in the same grid, but you can then just select all rows for a given computer and execute the basic sequence. Each row will execute its job queue one row at a time. Maybe this helps you. Maybe not. Good luck.

[Author]

Posts