Need Heartbeat deployment on set schedule
Hi,
we are trying to completely automate our software deployments that is made available on the package library. we use an auto download and have it deploy on a schedule first to our IT department and second to the rest of the organization.
Our users are fully mobile and come and go from the network a lot, so machines may not be here when the schedule kicks off. I am trying to get a deployment going there is deploys, then does heartbeat deployment until the new package is downloaded then it repeats the process starting with the IT department only. The only way is see is for heartbeat to just be enabled starting at one time and it stays on.
Does anyone have advice on how to use a heartbeat on a monthly schedule? or a better way to ensure stuff gets patched.
Thanks!
Comments
This post will explain but heartbeat doesn't work on externals. https://community.pdq.com/posts/11112-external-clients-on-a-schedule-never-run
What I did was set a schedule for heartbeat and every 7 hours and 5 minutes that way the heartbeat gets them in the office really well and the interval gets the externals. Since my externals are random times I picked 7hrs 5mins interval because that won't repeat the same time every day. This concept is working really well right now.
Our setup for each software piece:
This gives IT about 10 days to test the version.