Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Auto download and controlling installation time

I have not used auto download before, but am getting ready to for Google Chrome. I would like this auto download package to install when necessary, but preferably not during the day causing an interruption to any users. Is it possible to set auto download to install only at a specific time or during an overnight time window?

I watched the video about attaching an auto download package to an existing schedule but currently I do not have any packages that install on a recurring schedule. What is the best way to let auto download installation function, but restrict it to after hours?

Thanks for your help.

EDIT: Perhaps I've misunderstood something. I also want to have a second package that installs immediately for testing purposes. But, the packages themselves aren't targeting any computers. With that in mind, do I need have a schedule attached to each package that runs at whatever frequency and time I choose, otherwise it won't know what to deploy to anyway?



Date Votes
  • I deploy Chrome in the middle of the day. Chrome will keep working while the update installs and switch to the new version once user close the browser and reopen it. It does not force the browser close or ruin anything that I have noticed. May be worth a shot to deploy on heartbeat.

    Schedules confused me at first too, hopefully this will help.

    Setup a schedule to run daily at night and disable the option to put failed deployments in retry queue. I think anything in the retry queue works off a heartbeat and will automatically deploy once connected. There is not a way to setup a time window right now. This will start deployments and finish. Anything timeout, offline or fail should try deploying again the next day at the same time, unless added to retry queue.

    I don't understand your comment after the edit. Are you trying to install package 2 once package 1 installs? If so, there are a few ways to do this. Easiest way is to create multiple schedules with an hour between them to make sure the previous one finishes.

    If you have Inventory you can try this method. Setup a collection to check if package 1 application or file can be located. Set the package to only install if the device is part of the installed collection. Finally, setup the schedule to deploy Package 2 to the collection.

    Hope that helps. If you need more assistance, please provide screenshots of the schedules, collection and package.

  • Patrick,

    Thank you for the information. I like the idea of not retrying on failure so that only deploys at night, but now that you mention it I recall reading somewhere else that Chrome will update while open without need to force close. If that is the case, then I don't think I'll worry about it too much.

    Regarding the edit, I will have one package set to install immediately to specific test computers and then the other package set to install to all other computers after several days delay. What I was trying to say was that I had come to the realization that the auto download package wasn't going to do anything on its own without me creating the necessary schedules to go along with the packages.

    Thanks again for your help.

  • Think I understand the second part of your question. I'm actually working through a restructuring to help with this. I think this is what you want.

    Week 1: Deploy Google Chrome to test collection. Week 2: (Provided the new Google Chrome deployment is successful) Deploy Google Chrome to standard/live collection.

    You will need Deploy and Inventory to set this up. At least two - three collections. Here is the short version:

    1. [Inventory] Create a collection called group and setup two collections under that for Test and Live.
    2. [Inventory] Create a collection for the application. Setup two collections for installed (Current) and out of date/missing.
    3. [Deploy] Create package and set the option to only run for devices that is a member of the out of date/missing group.
    4. [Deploy] Create two schedules for this package. One for test, and one for standard. Set your standard package to run later than test.

    This will run the schedule against the Test or Live group. The package will only install if that Device is under the out of date/missing group.

    Here is a screenshot of how I have it setup. I can go into more detail if needed.

    Auto Deploy Groups

  • Thanks Patrick. I had linked to a specific collection, but the part about only running if found in the out of date group hadn't occurred to me.

  • I believe I am having the same problem/challenge; I would like to take advantage of the Auto Download of certain applications, but I have a hard time configuring the schedules to match. Is there a way to create dependencies in scheduling? The optimal deployment would deploy to my test group and then after X days the schedule for the rest of production runs. Regurds. Casper