Posted on 03-11-2010 11:14 AM
I want to install iWork on 36 computers today at 3PM.
I created a policy that has the trigger of "iwork" and set that to run
"Once per Computer" and scoped it to the lab.
I created a Scheduled Task for:
On the hour
3 PM
Every Day
Every Month
1 Minute
And scoped that to the lab as well.
So this is my first time creating a scheduled task in this way ( I have an
"any" triggered Software Update that is restricted to run within a certain
time frame ) and I am unsure what will happen exactly.
If I leave this scheduled task in place are they going to run the same Task
tomorrow? Will the "Once per Computer" limit in the triggered policy itself
prevent iWork from installing again ( the desired outcome )? What takes
precedence?
Ryan M. Manly
Glenbrook High Schools
? ACSP ? ACMT
Posted on 03-11-2010 12:57 AM
This is an inaccurate statement.
Setting a policy to run once per computer will do exactly that regardless of
the trigger/scheduled task you tell it to run with.
Once the computer has effectively run the policy it will never run it again
unless you delete the policy history for that system. The only policies that
will keep attempting are those that have an execution frequency of ongoing
or that start with the word 'Every'.
JAMF may need to correct me here. The only thing to keep in mind is that if
a system wasn't online at that schedule time and it comes on later it will
attempt to catch up with policies that have become enabled unless you've set
a specific expiration time or run on these days between these times options
for the policy. So someone fires the box up at 5PM it will eventually
attempt to run the policy then.
What can also gum this up is if some other policy is hanging up everything.
You'll see the lovely "this policy will run when the current policy
finishes" or something like that.
Craig E
Posted on 03-11-2010 11:27 AM
Ryan-
once per computer will nip it for the day, but it will run the policy every day of every month.
I would just set up the policy to run after 3pm today and leave the scheduled task out of it.
it will start out as a Red ball for status, at 3pm it turns green and will contact as many users as it can starting at 3pm.
Scheduled tasks are better suited for repairing permissions or running software updates on laptops every wednesday of every week.
(just a couple of examples scheduled tasks can handle much more)
Does that make sense?
Dan
Posted on 03-11-2010 11:48 AM
Yep! Thanks
Ryan M. Manly
Glenbrook High Schools
? ACSP ? ACMT
Posted on 03-12-2010 01:29 PM
Craig is correct in that a policy with an execution frequency of "once per computer" will only execute once on a particular piece of hardware, regardless of the trigger (Scheduled Task).
To clarify a little about how launchd works, launchd items (which is what Scheduled Tasks are), will execute on wake if the Mac was sleeping when the task was scheduled. If multiple instances of the same task were missed, it will only occur once on wake. Tasks missed while the Mac is powered off do not get "caught up" when the Mac is powered up.
My personal take would also be to leave the scheduled task out of it and use the date and time limitations to get the desired timing.
I hope this is helpful.
--
Miles Leacy
Technical Training Manager
Mobile (347) 277-7321
miles at jamfsoftware.com<mailto:miles at jamfsoftware.com>
....................................................................
JAMF Software
1011 Washington Ave. S
Suite 350
Minneapolis, MN 55415
....................................................................
Office: (612) 605-6625
Facsimile: (612) 332-9054
....................................................................
US Support: (612) 216-1296
UK Support +44.(0)20.3002.3907
AU Support +61.(0)2.8014.7469
....................................................................
http://www.jamfsoftware.com<http://www.jamfsoftware.com/>
Posted on 03-12-2010 01:31 PM
Thank you. And that’s why I said JAMF may need to clarify. =)
Craig E
Posted on 03-12-2010 01:38 PM
No offense taken.
The triggers can get confusing
at the least we pointed him to the proper solution! :0)
Dan
Posted on 03-12-2010 01:40 PM
Exactly. =)