Monthly deployments, offline targets to heartbeat instead of retry?

Comments

4 comments

  • Christian Bacher

    I would always link the schedule to a (old) collection in combination with the heartbeat trigger, this gives the best result.

    To prevent a wrong deloyment, copy the official old/latest collection and build a custom one and link the schedule to this one.

    Example: I have a custom "Firefox esr (old)/(latest)" collection, because PDQ offers the wrong language for us. If a new Firefox ESR version comes out, i download the right language version and i replace the .exe in the package. Then i change the version number in my custom collection.

    This way the heartbeat trigger don't kicks in if PDQ says there is a new version, it kicks in after i changed the version number in my custom collection.

    0
    Comment actions Permalink
  • Dennis Heijnemans

    Hi Christian, thanks for the ideas.

    Sounds like a good workaround; although I would still love to see a "move failed/offline deployments to a Heartbeat" as an option.

    How do you make sure your heartbeat schedules don't interfere with each other? Installing multiple new packages at the same time results in errors. Or do you use 1 heartbeat schedule with all the relevant packages attached to it?

    0
    Comment actions Permalink
  • Christian Bacher

    How do you make sure your heartbeat schedules don't interfere with each other? Installing multiple new packages at the same time results in errors. Or do you use 1 heartbeat schedule with all the relevant packages attached to it?

    Heartbeat schedules don't interfere with each other because only one package can be run on a device at the same time. The other deployments are queued and processed in a sequence until all are deployed.

    As long as there are no dependencies between the packages, everything works automatically.

    If you have dependencies like "you need Net Framwork 4.7 before you install paint.net", build a custom package with nested package steps (first Net Framework, second paint.net) or use the "pre-Steps" option inside the original paint.net package to make sure you have the right install sequence.

    0
    Comment actions Permalink
  • F V

    I would love to have a heartbeat retry trigger for offline computers too, 

    would be very usefull for laptops and would make more sense than retrying again and again.

     

    0
    Comment actions Permalink

Please sign in to leave a comment.