Skip to main content
Question

Feature Request. Triggers

  • June 15, 2010
  • 3 replies
  • 1 view
A
  • Anonymous

We use the same package in different scenarios which currently requires
multiple policies.

Scenarios: One package and companion scripts installed through self-service or a
keyword. Right now we need a policy for each scenario. This gets to be very
cumbersome with so many policies.
So essentially we would like to use more than one of the existing triggers
on the same policy. (In trigger dropdown we can only use 1, we would like to
use a few)

Thanks Again!
Mark Pellecchia
Princeton University

    3 replies

    T
    Forum|alt.badge.img+31
    • tlarkin
    • Honored Contributor
    • June 15, 2010

    Mark,

    Can you please give me some specific examples, and I can probably whip together a script that goes through all these requirements and installs whatever manual trigger policy needed. I know what you mean because we have roaming users, and I don't want my roaming user to move across town and pull certain policies over the WAN, when there is a distribution point in the building they are in.

    I do it through loops and case statements via shell script then trigger the manual trigger policy based on it. I also do it by software version too.

    M
    Forum|alt.badge.img+7
    • Millertime
    • Contributor
    • April 24, 2013

    I was just looking for this very thing... Here's what I'm trying to accomplish.

    I have a policy that is triggered by 'any', once per computer. All it does is create a folder in the /Applications/Utilities folder, where I store some custom images and maintenance scripts. Though I am now writing a utility w/ Applescript where I'd like to be able to trigger that same policy through the use of a custom trigger. I need to do that to be sure the machine has the latest version of the scripts & images.

    It seems redundant to create two policies and clutter up the 'Policies' screen. Any thoughts?

    Thanks!
    Bill

    mm2270
    Forum|alt.badge.img+24
    • mm2270
    • Legendary Contributor
    • April 24, 2013

    Just call the policy in a script by its id instead of the trigger. We do this all the time.

    sudo jamf policy -id <id>

    To figure out the policy id, click the Edit button on the policy in your JSS and look in the addressbar. The last set of numbers in the address after the policy_id= is the policy id, for ex, https://your.jss.server.com:8443/editPolicy.html?policy_id=100

    Note that scope still applies here. If the Mac is not in scope of the policy, when you try to trigger it with the id it will come back with no policies with id <id> were found, or something to that effect.

    Terms & ConditionsCookie settingsAccessibility statement