[Casper] Acrobat Pro

[Miles Leacy]

Ok, I was under the impression that the reason /tmp couldn't be deployed to
is because of the exclusion list in Composer.  Perhaps I was mistaken or
there is a bug.
What I have done that works is to create a folder in /Library for such
purposes.

I typically name it /Library/NameOfCompany and populate it with any files or
folders that I need to use for deployment or management.

You should be able to deploy the installer to /Library/NameOfCompany/Adobe,
and then call it with a script.  However, I believe someone on this thread
mentioned that this particular update won't take the -silent switch.
 Perhaps some UI scripting can get around this limitation?

My next question is why do you have to deploy this Installer from Adobe?
 Why not take a Composer snapshot, run the update and package the changes
(including undoing any Adobe "repairs" you don't like)?

----------
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, Dec 8, 2008 at 1:14 PM, Nichols, Jared <jared.nichols at ll.mit.edu>wrote:

>  My exclusion list is empty
>
> j
>
>
> On 12/8/08 12:50 , "Miles Leacy" <miles.leacy at themacadmin.com> wrote:
>
> Did you remove /private/tmp from the exclusion list in Composer preferences
> *before* building your package?
>
> ----------
> 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 <http://www.themacadmin.com>
>
>
>
>
> 2008/12/8 Nichols, Jared <jared.nichols at ll.mit.edu>
>
> Is there a best-practice way to run these updates then?  I just tried
> deploying to /tmp and I don't seem to see it anywhere in there.
>
> Hrm.
>
> j
>
>
>
> On 12/8/08 12:28 , "Smith, William" <william.smith at merrillcorp.com <
> http://william.smith@merrillcorp.com> > wrote:
>
> The problem I've seen with Adobe's Acrobat 8.x updaters is that they are
> not scriptable like those for the other CS3 applications. Those .app
> updaters can be called with a –silent switch but not Acrobat's. :-(
>
> These Acrobat updaters also require that you select the Acrobat application
> to patch and also may ask you to "repair" the installation, which is
> Adobespeak for "let me put back my Safari and Office plugins and set myself
> to default again." These prompts must be manually dismissed.
>
> Also, JAMF may have a difficult time getting CS4 to work because the
> –silent update for those suites wants to connect to the Internet to download
> updates as part of the install process. In our environment our Macs must
> authenticate to our proxy (no free love access) and that just hangs the
> install.
>
>
> --
> Jared Nichols
> ISD Infrastructure and Operations – Desktop Engineering
> MIT Lincoln Laboratory
> 244 Wood St.
> Lexington, MA 02420-9108
> (781) 981-5500
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20081208/3b3c0d34/attachment.html