Start and stop time with interval type schedule
Adminspx
This would probably solve our problem: killing the browser (or other software) in the middle of user activity. I could create a schedule with a 1 minute interval, start time of 6am and a stop time of 9am, thus having the effect of running the install as soon as they log on in the morning.
As others have noted, PDQ Deploy doesn't have a good solution for this and the new auto deployment feature is pretty much useless for us with Java or any other app quitting package until this is addressed.
0
Comments
Hi,
While having a maintenance window feature would be great, this would require us to have an agent installed to manage this and as you know we're an agentless product.
Using your example of Java, this could be done with a Daily trigger in your Auto Deploy Schedule. There are a few warnings and caveats to keep in mind but should meet your needs.
- Let's say your environment is 2000 computers and you need to get the new Java out without bothering your end users but at the same time setting the schedule up for the long haul and Auto Deployments. If you use the Daily trigger and have it run starting at 6am it can run every day but it might not finish by the time you're looking for so you could add a Once trigger to run after hours and it should pick up the majority of those machines before the daily schedule runs. You can use the option to "Stop Deploying to computers once they succeed so you don't have successful machines being deployed to again. Or if you have an Enterprise license of Inventory then I'd even recommend using the Collection Library and "linking" your schedule to the collection. If the collection is empty, then the deployment schedule won't look for new targets until the next trigger.
I wouldn't recommend setting an interval schedule that close together in time either. If you deploy once to all of those machines, unless you up the number of concurrent targets to as many machines as you have, some of the machines will be queued and ready to deploy once there is an available spot for them so adding another instance of deployment wouldn't help speed them up.