Posted on 05-06-2015 08:24 AM
Can I pre-enroll iMacs, add these per-enrolled iMacs to a static group? if so how ?
I have a policy that I want to run that is 'triggered' by 'enrollment', the 'scope' for this policy will be this static group?
(the policy installs a network printer)
Solved! Go to Solution.
Posted on 05-06-2015 10:01 AM
Hi @tcandela,
I've done something similar in imaging workflows, although rather than calling the policy by it's ID, I prefer to assign the policy a custom trigger (you can call this anything you want, like 'printer') and then call it in my script like this.
jam policy -event printer
Hope that helps!
Posted on 05-06-2015 08:40 AM
It just popped in my mind to do this;
this is for a computer lab; that uses a standard and smart configuration, I will stick an additional script in the smart configuration
I will create a simple script that runs at reboot calling the policy
jamf policy -id *
has anyone tried or is doing such a thing?
Posted on 05-06-2015 10:01 AM
Hi @tcandela,
I've done something similar in imaging workflows, although rather than calling the policy by it's ID, I prefer to assign the policy a custom trigger (you can call this anything you want, like 'printer') and then call it in my script like this.
jam policy -event printer
Hope that helps!
Posted on 05-06-2015 10:17 AM
@kitzy i've used custom triggers on other policies, my syntax is
jamf policy -trigger mytriggername
Posted on 05-06-2015 10:35 AM
q
Posted on 05-06-2015 11:10 AM
@kitzy using a custom trigger or jamf policy -id * does a scope need to be set to specific computers?
if the configuration is telling it to install, then it shouldn't need a scope ? it does what the config is set to do?
Posted on 05-06-2015 11:22 AM
@tcandela you'll still need to scope to something. The beauty of a policy that uses only a custom trigger is that you could conceivably scope to everything since the only way the job gets called is by trigger.
However, you could scope to a Smart Group and assign these machines based on some criteria.
Posted on 05-06-2015 11:33 AM
@tcandela jamf policy -trigger was the verbiage used in in older JAMF Binaries. While jamf policy -trigger still works I would recommend using jamf policy -event moving forward. If you do a jamf help policy that will show the current options.
Posted on 05-06-2015 01:06 PM
@stevewood understood, thanks
@Joel.Peasley Thanks, I'll make the syntax change to -event