Best settings for JSS to control software updates.

[jgwatson]

I am very new to the OSX side of JAMF. I would like my JSS to control when clients get their updates, as in I don't want ARD to do it anymore. Ideally I would like a situation where I don't have to do anything. I would like to know if I have picked the best settings for this to work. I managed to install this on one machine and it worked fine, but the other machines I scoped this to never installed the policy (they were asleep at the time of install), but they have installed other policies since.

In short the trigger is log out, and the execution is once per week.

What settings do you use? Thanks

[MAD0oM]

@jgwatson It all depends on the type of policy. If its a script typically i would do a log out/ log in or a start up. But for updates if its critical ill usually run during the morning time before everyone comes in and do start-up and recurring check in that way once users start getting in they are getting the policy. However, from my JSS in the DMZ for external client i typically would not push out policies as i pay for web hosting for my DP but if i do ill go ahead with check in because i don't know when the user will have a stable connection and usually if they check in to the JSS then zap goes my policy.

[Nix4Life]

echo what @Sherdwain said. When I was using JSS. JG, you stated you were new to the OSX side of JAMF, but if you are comfortable with Linux, you may want to also consider Munki https://code.google.com/p/munki/
or
Patchoo http://patchoo.github.io/patchoo/
I currently use Munki as well as others here in the community. match it with autopkg and jenkins for a fully automated solution. Steve Wood has a great write up on this ( good job Steve ! ) http://osofrio.wordpress.com/