Concurrent deployment limit for specific package?

Comments

3 comments

  • James D

    I believe concurrent deployment settings are only global. One recommendation I've heard for staggering deployment is to make multiple collections of the computers being targeted in PDQ Inventory. Then make a different schedule targeting teach collection changing the scheduled times accordingly. i.e. schedule 1 on Tuesday, schedule 2 on Wednesday, etc.

    0
    Comment actions Permalink
  • Colby Bouma

    Another option is to set up another instance of Deploy that only handles this task. Licensing is per admin, so you can have as many instances of Deploy and Inventory as you want.

    0
    Comment actions Permalink
  • kelemvor

    Thanks for the ideas.  Based on something I saw online, I ended up creating a new Package called Random Delay that just has a single Powershell line of: Start-Sleep -seconds (1..600|get-random).  I can then create a schedule or a deploy once that uses that package first and then actual package second.  Can just change the 600 to whatever number you want if you want a longer timespan.

    Seems to work pretty well so far.

    0
    Comment actions Permalink

Please sign in to leave a comment.