[Casper] User-based shell scripts after self-service installation

[Jeremy Matthews]

Many of those apps write licenses out to the users' defaults - not  
global defaults or the system - unfortunately.

We're limiting those who can see what apps by computer groups.

I suppose my question that, when a policy is executed by Casper, and  
it includes a script to modify user defaults, does it modify the user  
defaults for the person installing it, or root (which is how  
packagemaker works). Same goes for pushing a defaults file after an  
installation via self-service - will it install in that users' home  
directory (say it installs to ~/Library/Preferences) or instead, the  
root user (as in packagemaker).

Thanks,
j



On Aug 14, 2008, at 1:40 PM, Ernst, Craig S. wrote:

> If you use Composer why wouldn’t it just be part of the package, why  
> does it need to be a separate file? Is this more for the security/ 
> licensing aspect so you don’t go over your licenses by everyone just  
> installing it since they see it?
>
> To answer your question, as long as it’s just a file you want to  
> modify with defaults or copy down it should work. Right now there  
> would be no trigger to make that second portion happen. You would  
> have to initiate that unless you do more scripting. =)
>
> Craig
>
>
> On 8/14/08 12:26 PM, "Jeremy Matthews" <jeremymatthews at mac.com> wrote:
>
> Actually, we have volume licensing on everything possible - even  
> when there are only a few licenses....except Final Cut Pro.
> All the consumer stuff doesn't seem to be bound by hardware...so far.
>
> So, is it doable using either of those methods for the non-hardware- 
> bound apps?
>
> -j
>
> On Aug 14, 2008, at 1:20 PM, Ernst, Craig S. wrote:
>
> The problem you might run into here is that the serialization that’s  
> created on one machine won’t work on a another as it is bound to the  
> hardware it was originally installed on. This is the case with many  
> Apple software products. To get around this you typically need to  
> purchase Volume licensing, which is 5 or more. And realisitically we  
> do that to get the media that allows for a non-hardware bound  
> install that can be packaged and deployed to multiple machines. I  
> know that this is what we do for Final Cut Studio as well as Final  
> Cut Express. I imagine that iWork is the same.
>
>  Perhaps this will answer your question.
>
>  Craig E
>
>
>  On 8/14/08 12:09 PM, "Jeremy Matthews" <jeremymatthews at mac.com>  
> wrote:
>
>
> Lets say you have a self-service item, iWork for example.
>  After iWork is installed by the user, you want to serialize iWork by
>  way of either:
>
>  1) writing user defaults to that users' preference file (assume you
>  would choose to add a script in casper and run after the package is
>  installed)
>  2) Deposit a file into the users' /Library/Preferences/ directory
>
>  I can't attempt yet (our Casper is offline) - but need to continue
>  working to deploy these once it is online. Does either method work?
>  They sure don't work in packagemaker as postinstall scripts....since
>  installer runs as root it can't understand the concept of "~" outside
>  of the root user itself.
>
>  Thanks,
>  jeremy
>  _______________________________________________
>  Casper mailing list
>  Casper at list.jamfsoftware.com
>  http://list.jamfsoftware.com/mailman/listinfo/casper
>
>
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20080814/a41a0ab0/attachment.html