You actually don't need the smart groups at all. The Installomator script has a parameter that will check what version is currently running. If the latest version is already running, the script will exit
Mason, that is partially correct. Yes the script does check for that, but the Smart Groups in Jamf are leveraged for scoping the policy out. If you don't have a scope, the policy won't know what endpoint to run on.
@@masoncrouse9569 It narrows the focus to just the groups that need it. It you mass blast all computers with a policy to update an app that is not all computers you are needlessly running policies for all apps all the time. It’s not efficient or best practice imo.
@@masoncrouse9569 that’s not really best practice to run that on all computers. You would want to narrow your scope to only update the app if it is on the computer. No need to run an update script on a computer that doesn’t even have the app in question.
Fantastic presentation by Jared Young!
Thanks Jeff!
You actually don't need the smart groups at all. The Installomator script has a parameter that will check what version is currently running. If the latest version is already running, the script will exit
How?
Mason, that is partially correct. Yes the script does check for that, but the Smart Groups in Jamf are leveraged for scoping the policy out. If you don't have a scope, the policy won't know what endpoint to run on.
@@Mobofixer81, why not just run it on all of them? It'll exit if it doesn't need an update
@@masoncrouse9569 It narrows the focus to just the groups that need it. It you mass blast all computers with a policy to update an app that is not all computers you are needlessly running policies for all apps all the time. It’s not efficient or best practice imo.
@@masoncrouse9569 that’s not really best practice to run that on all computers. You would want to narrow your scope to only update the app if it is on the computer. No need to run an update script on a computer that doesn’t even have the app in question.