From sean.hansell at jwt.com Tue Oct 14 09:02:00 2008 From: sean.hansell at jwt.com (sean.hansell at jwt.com) Date: Tue, 14 Oct 2008 12:02:00 -0400 Subject: [Composer] Acrobat Self-Healing Message-ID: I'm having an issue with packaging Adobe Acrobat Pro. I need to disable the self-healing, as my users are not admin and can't authenticate to self-heal themselves, but at the same time, I want the apps to work properly, and when self-healing is completely disabled Distiller doesn't work consistenly well until the Self Healing is run. Has anyone had any success finding a balance between useability and functionality when packaging Acrobat Pro 8 or 9?

This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender.

-------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20081014/9c456028/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 15781 bytes Desc: not available Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20081014/9c456028/attachment.jpe From Kurt.Tappe at chase.com Tue Oct 14 13:06:47 2008 From: Kurt.Tappe at chase.com (Tappe, Kurt (Card Services)) Date: Tue, 14 Oct 2008 16:06:47 -0400 Subject: [Composer] Acrobat Self-Healing In-Reply-To: Message-ID: I am having the same problem. The best solution I?ve been able to come up with so far is to create an AppleScript that does nothing, name it Adobe Updater.app, and replace the real updater with it. I set its permissions so that it cannot be replaced with the real one. Kludgy but seems to be marginally effective. Though for some reason it does seem to get replaced with the real version on some Macs, though not all?I?m still investigating. Adobe claims there is a way to turn off the checking for updates, but it only seems possible if you use their distribution method, which involves replacing an XML document somewhere with one that turns off the updating. Since we use Composer, we can?t replace that file. Perhaps there is a way to turn the option off elsewhere? It?s frustrating. Glad to hear I?m not alone and eager to hear others? solutions, -Kurt On 10/14/08 12:02 PM, "sean.hansell at jwt.com" wrote: > > I'm having an issue with packaging Adobe Acrobat Pro. I need to disable the > self-healing, as my users are not admin and can't authenticate to self-heal > themselves, but at the same time, I want the apps to work properly, and when > self-healing is completely disabled Distiller doesn't work consistenly well > until the Self Healing is run. > > Has anyone had any success finding a balance between useability and > functionality when packaging Acrobat Pro 8 or 9? > > > > This transmission is intended solely for the person or organization to whom it > is addressed and it may contain privileged and confidential information. If > you are not the intended recipient you should not copy, distribute or take any > action in reliance on it. If you believe you received this transmission in > error please notify the sender. > > > _______________________________________________ > Composer mailing list > Composer at list.jamfsoftware.com > http://list.jamfsoftware.com/mailman/listinfo/composer ----------------------------------------- This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20081014/31162594/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 15781 bytes Desc: not available Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20081014/31162594/attachment-0001.jpe From sjhinding at isd194.k12.mn.us Tue Oct 14 14:34:40 2008 From: sjhinding at isd194.k12.mn.us (Sandy J. Hinding) Date: Tue, 14 Oct 2008 16:34:40 -0500 Subject: [Composer] Acrobat Self-Healing Message-ID: Hi Sean, I have made all the Adobe selfheal.xml files (/Library/Application Support/Adobe/Acrobat/* SelfHeal.xml ) read / write for everyone. This allows the applcation to write to those files when any (non-admin) user opens the application. So far I have not discovered any down side for my environment. I created a package containing the selfheal file for every adobe product we use, and then either push it w/ a policy or allow users to install using "SelfService" (another app in the Casper Suite) Those are probably the files that Kurt is referring to, and maybe there is a way to edit them to turn off the self healing function.... Sandy HInding Lakeville Schools sjhinding at isd194.k12.mn.us -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20081014/8ec6ee4d/attachment.html