Terminal Command in Self Service

You would need to create a policy and use the “Files and Processes” payload. Click “Configure” and there is a line at the bottom labeled “Execute Command”. Put your command in as 

/usr/local/bin/jamf policy -id xxx

No need for sudo, Jamf runs commands as root. 

Then scope it, then go to the Self Service tab and set it up how you like. 

Should be good to go. 

I misread the initial explanation. In order for a policy to run when you do:

sudo jamf policy

You will need a scope (either smart groups or directly assigned to devices) and the trigger “Recurring Check-In” checked off.

Otherwise you can configure the policy to be a Self Service install but it will show as pending until the end user runs the policy from Self Service. 

If you’re not getting a policy execution when running just 

sudo jamf policy

Then most likely the policy itself is misconfigured.  Either your scope hasn’t identified the targets properly, or your trigger mechanism is wrong. Can you provide more details? When you check logs for the policy, does it show the list of workstations you expect to be targeted (ie they meet the criteria you expected whether it’s all, missing XXY rule?, etc).  The other thing to check is what is your trigger and limitations? Are there any pre-requirements to the scoping? IE must have company portal installed, must have AV software, etc, that would delay the policy from running? 

Hello ​@easyedc 

Thanks for your time and suggestion.

Our Device Compliance Policy is 

Once per computer = Execution Frequency 

Trigger = Self Service

Scope = All computers

Its for all new computer who register their devices to meet Company Compliance criteria  however, most of the devices gets the error “ this device is enrolled with another device management provider”.

And when we go to Jamf Portal and check the MS Device Compliance Policy logs for the serial number - its says Policy is pending and it stays on pending until executed with Policy ID on terminal.

`That's the reason I wanted to create another self service policy where policy will be available to execute via Policy ID.

Thank you 

You could add a second trigger to the same policy with a custom trigger name to execute. At that point, you would run 

sudo jamf policy -event “mypolicyname”

and it would execute the same policy, which could also keep your logs organized if you’re trying to track log execution as well. In your policy editor, Under General > Trigger > Custom and give it a trigger word/phrase. Was this policy cloned from another policy? I’ve seen weird things like that happen and once a new policy is created from scratch things seem to magically work as expected.