[Casper] Dummy Receipts and Custom Triggering a Policy

[Miles Leacy]

Oops, I realized that I forgot to mention the second thing to do to use
custom triggers.  Ryan mentioned it further back in the thread, but here it
is again...
After you save your policy that is triggered by "other", for example, let's
say that other="customTrigger".

You call the custom-triggered policy via the jamf binary like so:

sudo jamf policy --trigger "customTrigger"


----------
Miles A. Leacy IV

 Certified System Administrator 10.4
 Certified Technical Coordinator 10.5
 Certified Trainer
Certified Casper Administrator
----------
voice: 1-347-277-7321
miles.leacy at themacadmin.com
www.themacadmin.com




On Mon, Jan 12, 2009 at 10:11 AM, Miles Leacy
<miles.leacy at themacadmin.com>wrote:

> Gents,
> I'm taking this back on list because there may be others in the community
> that would benefit from this discussion.
>
> To Recap, there are two questions: how to use custom triggers and how to
> create dummy receipts.
>
> To use a custom trigger there are two things to do:
> 1. Create a policy and in the General tab, choose "other (Manually specify
> the run at action in this field) -->" from the "Triggered by:" drop down
> menu and enter your custom trigger in the text field next to this drop down
> menu.  I use Apple-esque run-together phrases with caps, such as
> "memberAccountingComputerGroup" for my custom triggers.  I'm not sure what
> the upper limit is for custom trigger length, but I haven't hit it yet, and
> I like to be descriptive with my triggers.
>
> Re: "Dummy receipts"
> The so-called "dummy receipt" is a receipt from a payload-free package.  I
> create empty prebuilt Apple .pkg files using Composer like so...
> 1. Create an empty folder with the same name as your intended package (and
> receipt) in /Applications/The Casper Suite/Temp/ (see attachment "Picture
> 1.png")
> 2. Open Composer, choose this prebuilt package and save it as an Apple
> .pkg.  (see attachment "Picture 2.png")
>
> Some may find that using these "dummy receipts" creates clutter, but if you
> integrate the concept into your workflows, document your work, and maintain
> clear and consistent policies (in the general sense, not Casper Policies)
> and naming conventions, use of receipts in this way can be a very efficient
> and effective method to extend your management capabilities.
>
> ----------
> Miles A. Leacy IV
>
>  Certified System Administrator 10.4
>  Certified Technical Coordinator 10.5
>  Certified Trainer
> Certified Casper Administrator
> ----------
> voice: 1-347-277-7321
> miles.leacy at themacadmin.com
> www.themacadmin.com
>
>
>
>
>
> On Fri, Jan 9, 2009 at 5:39 PM, Ryan Harter <rharter at uwsp.edu> wrote:
>
>> I haven't used dummy receipts before, I've been trying to avoid them if
>> possible because it seems like more for me to keep track of.  Miles might be
>> able to give you more help with that.
>> As for the custom trigger, you've got it all figured out.  when you set a
>> policy you can set triggered by to custom (I think it even has an ascii
>> arrow ----->) and enter the trigger in the text box.  Then you call sudo
>> jamf policy --trigger "custom trigger" and it will run that policy.  I
>> currently do it as a workaround to get my adobe installs to run after boot
>> time.
>>
>> Hope this helps,
>>  *
>> Ryan Harter*
>> UW - Stevens Point
>> Workstation Developer
>> 715.346.2716
>> Ryan.Harter at uwsp.edu
>>
>> On Jan 9, 2009, at 4:30 PM, Cyrus Vahhaji wrote:
>>
>> Miles, Ryan,
>>
>> I've been following "Computer group from AD" thread and you brought up
>> dummy receipts and triggering custom policies and didn't want to hijack the
>> thread with my question.
>>
>> What is the best way of creating a Dummy Receipt? Would it be an empty
>> folder created in Composer?
>>
>> What do you mean by "custom trigger" here?
>> - if desired group is found, issue a custom trigger of "receipt exists".
>>  Is it triggering a policy to add the dummy receipt that the machine is in
>> AD? If so, are you using something like "sudo jamf policy –trigger "desired
>> policy"
>>
>> Thanx,
>>
>> *Cyrus Vahhaji
>> **Accenture
>> Best Buy Technology Group
>> *desk – 612.291.3643
>> fax – 952.430.4260
>> email – mailto:cyrus.vahhaji at bestbuy.com <cyrus.vahhaji at bestbuy.com>
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise private information. If you have
>> received it in error, please notify the sender immediately and delete the
>> original. Any other use of the email by you is prohibited.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20090112/35700732/attachment.htm