[Casper] Acrobat Pro

[Smith, William]

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.

-- 

bill

William M. Smith, Technical Analyst
MCS IT
Merrill Communications, LLC
(651) 632-1492


On 12/8/08 11:04 AM, "Miles Leacy" <miles.leacy at themacadmin.com> wrote:

> That sounds like it should work.  Of course, test, test, test.
> 
> Be sure to remove /private/tmp from the exclusion list in Composer before
> building your package.
> 
> 
> 2008/12/8 Nichols, Jared <jared.nichols at ll.mit.edu>
>> I'm also wondering about this, though more in a general sense.  The updater
>> is a .app.  Can I deploy that as is into /tmp and then run a script to launch
>> it? 
>> 
>> j
>> 
>> 
>> On 11/5/08 10:53 , "Matsuno, Matt" <Matt.Matsuno at Mattel.com
>> <http://Matt.Matsuno@Mattel.com> > wrote:
>> 
>>> Hey everyone, quick question: How are you guys running the Acrobat Pro
>>> updates? Added the AcroProUpd813_all.dmg through Casper Admin and it's
>>> complaining that it's not a Valid Adobe Installer or Adobe Updater...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20081208/7ed7919f/attachment.htm