Hi Gregzy,There's two options I can think of:1. You can set policies to
be once per machine, this means that once installed via Jamf they will
not show up in self service. This will only be useful for machines built
and managed by Jamf as it may not ...
@stephanpeterson - If it's the same user on all the machines just create
a login script scoped to that user that logs the date of the login into
a file and another script which counts the lines that are above the
specified date and echoes this into a...
I agree with @Foster , scoping based on Java is the easier option. As
mentioned above you are defining the SoftwareLocation with a trailing /,
which is then input again in your script. You need to remove the
trailing / when defining the path.
Step 1: Create Smart group to define those eligible for update- Not
currently running latest OS/Cached copy of latest OSX updates- Machine
is new enough- Machine has the spaceStep 2: Create a policy to cache the
OSX installer on to the machines in th...
