Multiple Heartbeat Installs

Follow
Steve G

I am using the heartbeat schedules and love them! However, I am having a issue where multiple things try to install all at the same time. Is there a setting I am missing, or something I can do to workaround this issue? Eventually everything installs, but normally takes 1 or 2 days for shutdowns/wakeups, etc. The error I get on the packages is "MSI Error 1618: Installation already in progress" Any suggestions?

0

Comments

11 comments

Date Votes
  • Brigg Angus

    Hi Steve,

    I know this comes late, but wanted to answer this in case you (or someone else now or int he future) are still having issues with this.

    The best way to ensure that your installs don't happen simultaneously or error out (provide some order to chaos) is to use nested packages. Here's a great (short) video on how to create nested packages: https://www.youtube.com/watch?v=A8t3eaOa7a0

    And here's another short video on multi-step packages: http://www.adminarsenal.com/pdq-deploy/multi-step-packages

    0
    Comment actions Permalink
  • Michael Muni

    Nested packages are great but I don't think this will help with his issue with heartbeat deployment.

     

    I'm guessing he has a setup like I do where several packages deploy via heartbeat so that the updates like java etc trickle out as computers come online rather than one large massive push. (I do have mine do the massive push at the end of the day anyways)

     

    This works great, however when you add a brand new computer to your network, all the heartbeat deployments run at once to this new computer.

    0
    Comment actions Permalink
  • Steve G

    Mmuni,

     

    Exactly! My workaround is to still do a daily push to catch any stragglers, but when a computer hasn't been on the network for a while or it is new, I get a ton of failures from everything shooting off at once.

     

    Not a big deal, just more of a annoyance and something I have to remember.

    0
    Comment actions Permalink
  • Michael Muni

    Easy way to fix this would be to have PDQ check if something is already deploying to a specific computer and if it is, wait until the current deployment finish's befor the next one starts. 

    Like what happens with nested packages, except in this case we don't care about the order we just want them to install one at a time.

    0
    Comment actions Permalink
  • Nate Simon

    Where do you setup PDQ Deploy to check if something is already deploying?

     

    0
    Comment actions Permalink
  • Steve G

    Nsimon,

     

    I believe Mmuni was just talking theoretical and his comment was more to the devs at PDQ. However, with that said I believe this function has actually been implemented in the last few versions. I have not seen this issue pop up for quite some time now.

    0
    Comment actions Permalink
  • Colby Bouma

    I agree with Steve G. Multiple deployments to the same target just get put in a queue. It's possible older versions may have had a bug.

    0
    Comment actions Permalink
  • Mikestoolz

    This issue has since been fixed if i remember correctly.

    it would still be a good thing if we could prioritize package deployment giving some packages higher importance than others.

    0
    Comment actions Permalink
  • Colby Bouma

    In my quick test they kicked off in order of Schedule ID. 1 was first, then 2, etc.

    0
    Comment actions Permalink
  • Mikestoolz

    yeah im talking about all packages in general, being able to assign them a priority #.

    0
    Comment actions Permalink
  • Colby Bouma

    I just created an internal feature request ticket for this. I will let you know what happens.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post