help with scheduling

• will it re-install the same version everyday or does it check/track the targets version and only install if needed?

I recommend deploying to a collection, that way they disappear once the installation is successful.

• will it run everyday at 5 am or just the once for 180 minutes and never again? 

It will start at 5 am and every time a computer goes from offline to online. The "Stop deploying to remaining queued computers after xx minutes" will only stop the deployment for computers that are in the queue, it will not prevent new computers from entering the queue. 

I would recommend using Daily instead of Heartbeat. 

• Does this mean two triggers in the same schedule can conflict

Yes, I think so. I'm pretty sure multiple schedules can fire at the same time and one of them will just queue.

Thanks Colby,  

I don't really want to use a collection because it seems as though I would have to rebuild the collection with each new version number, I'm hoping to automate this as much as possible. 

After watching it for the last week, using a daily with a retry queue, it appears as though it has not tried to re-install the same version everyday.  As expected, computers stay in the retry queue al day long until they are completed.  

Need a bit of clarification on a few items, thanks for your help.  Enterprise Mode.

We're a school, this is for teacher Java and Flash updates.  I want to try set this up to be hands free for me, and not close the user's browser in the middle of their work.  My thought is I would use auto deploy with immediate approval in the mornings soon after users come online and stop trying by 8am when school starts, repeating each morning because I won't catch everyone in one try. Most of our users have laptops that go home every night.

If I attach a schedule with a heartbeat trigger or maybe a 3 minute interval trigger starting say Sept 16 at 5 am with "Stop deploying to remaining queued computers after xx minutes" set for 180 minutes and no retry queue...

• will it run everyday at 5 am or just the once for 180 minutes and never again? You can tell it on every day by specifying "Run every xx days" in the Interval Trigger.
• If just once then I suppose my only choice is daily with a retry queue , correct? (15 minutes is just too high of minimum though, 5 would be perfect)
• will it re-install the same version everyday or does it check/track the targets version and only install if needed? Deploying to the same machines without using some form of Inventory Collection will in fact redeploy to every machine every day.
• Is there a better way all together that I am missing?

Also, a little clarification on conflicts would be helpful.  From the manual:

• Be careful of creating conflicts when setting frequencies or using multiple triggers. If triggers overlap, only one deployment will start. For example, having two triggers, one for every Monday at noon and one for every day at noon, will not start two deployments every Monday.

Does this mean two triggers in the same schedule can conflict, or that two separate schedules can conflict and only one schedule at a time can run? It means using 2 or more triggers in one schedule can cause conflicting issues. We run multiple schedules, fired at the same time, but to different target groups. Makes reporting/etc easier for us. This may not be your best use case though, so take that as just a friendly tidbit.

You really should be using a Collection and increment the version of your Package, that way you can target the (Old) or (Not Installed) portions of the Collection for your Deployment. You will only have to increment the Version Number of your package and the Collection will dynamically update itself on next Scan.