Multiple Triggers on Single Schedule

Follow
Network Security

We have some systems that I need to start installing an agent to around 5a every morning.  Some fail, so I need to do an interval until they are successful.  The issue is I can't set the interval to happen every day at 5am.  I can set it to start at 5am, but then it quits when successful and doesn't run the next day.  So I was going to try the Daily schedule at 5a and then right under that an interval every 15 minutes until successful.  Is there a better way to do this?  Will the way I'm trying it work?  I understand that the Daily then Interval will double up the install but I'm ok with that if that's the only option.  I'm just not sure the 5am daily Trigger actually gets the interval below it to run as well.  Thanks, Daniel

1

Comments

6 comments

Date Votes
  • Network Security

    1
    Comment actions Permalink
  • Luke Nichols

    Daniel,

    I'm not sure if I fully understand what you're trying to do, but it sounds like you have an agent you want to push to every computer that doesn't already have it installed, and you want this push to occur beginning at 5:00AM and then every 15 minutes after until successful?

    In that case, you should set up a dynamic collection in PDQ Inventory to contain only computers that do NOT have the agent installed.

    Then, create a schedule in PDQ Deploy to install the agent's package on every computer in that collection.

    Set up your triggers like this with an interval trigger of 0d0h15m and only run between 5:00 AM and whatever end time you want:

    Keep in mind that your deployments could actually keep running after your end time specified here since they could start at your end time and run until that package's timeout is reached.

    I also recommend that on the Options tab you disable all three of the "Stop deploying to..." settings. I generally recommend always disabling the 1st setting when you are controlling the deployment via a dynamic collection and you also don't want to have the 2nd and 3rd settings enabled because you want failed deployments to re-try until they succeed and you want to control the deployment window using the trigger instead of that setting.

    1
    Comment actions Permalink
  • Network Security

    Hey Luke!  

    Thanks for the input.  I'll clarify whats happening.  So I need a recurring every day (os image gets wiped every night) at 5am.  What I'm finding is for some reason its only successful around 25-50% of the time due to other applications from other systems getting applied.  So I also need it to occur when it fails every 15 minutes until successful.  So I can do the recurring, but that will stop once successful and wont restart again since it was successful.  I'll do an example (might be easier to follow).  

    At 12am servers 1-10 get new images applied wiping out all other applications.  I set recurring at 5a for every 15 minutes and stop when successful.  Good there.  But at 12 am the next morning its wiped again.  Since the recurring has ran, and all were successful, it doesn't run.  I need it to run again though.  So my thought was if I put in a daily at 5a along with a recurring, that it would solve it.  I might just need to test it and see what happens.

    Thanks,

    Daniel Betz

    1
    Comment actions Permalink
  • Mike Kercher

    You probably need to induce a scan to run after the new images are deployed to find the machines with the missing packages you want deployed.  You would probably also want to deselect the option on your schedule to Stop deploying after success.

    1
    Comment actions Permalink
  • Luke Nichols

    Daniel,

    In that case I would advise against relying on the "Stop deploying to targets once they succeed" setting and instead rely on dynamic collection membership. That way you can just run a 15-minute interval forever and computers will automatically fall out of the dynamic collection once they get the agent installed to prevent double installations.

    You could also set a condition on the package like:

    File > Does Not Exist
    Directory: %ProgramFiles%\Agent
    Filename: Agent.exe

    That way if a double-deployment is attempted it will fail because the agent has already been installed. This will result in a lot of false negatives in PDQ though, and it will be a pain to sift through the failures to determine which ones actually failed and which ones failed because the file already exists.

    May I ask why you can't just install the agent in your golden image or deep freeze image or whatever it is that you're using?

    1
    Comment actions Permalink
  • Network Security

    Luke we only open the image once every two weeks for our change cycle.  The previous version of the application was causing issues and was removed from the image.  The new version of the application is being tested on a subset of servers to determine if the bug has been fixed.  Once we've determined it has, then it will be added to the image during the change cycle. 

    I'll go through and try a pdq scan to determine which are missing and then fire off the pdq deploy job to install.  I've only had 1 fail over 4 days on the second attempt. 

    Daniel

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post