Monthly deployments, offline targets to heartbeat instead of retry?
Our domain consists of about 85% laptops, 10% desktops, and 5% servers. Our laptops go in and out of the office online and offline at any given time anywhere in the world.
I'm trying to minimize the version disparity that exists in our environment, so I would like to set up a monthly update routine; that way at least most of the time our machines will run the same software versions.
Using Deploy and Inventory Enterprise, I would like to accomplish this in the following way:
- Monthly check for new package versions (I have a nested "Baseline" package consisting of a dozen packages from the library) and approve them automatically, say every last Friday at 8 PM (not sure if possible).
- Monthly deploy schedule, say every first Monday at 9 AM (easy enough).
- For offline targets and other failures, skip the retry queue and use a Heartbeat schedule instead (not sure if possible).
Is this possible, or is there an other clever way to accomplish this?
To be clear, I know I can set an approval schedule, but if new versions come out during the monthly cycle, they'll be deployed to the machines in the "retry heartbeat", in stead of the desired monthly approved version.