Spacer http://macenterprise.org MacResource.org - Mac OS X enterprise deployment project Spacer
Site Map Contact Us Site Map About Us Top Background
 
Search
 
 
Fixing Adobe SelfHeal.xml problems E-mail
Written by MacEnterprise   
Monday, 12 March 2007
One of the most common problems when deploying Adobe applications is the ability to "Self-Heal" a broken application.  In particular, this feature can severely impact Enterprise deployments.  Read on for how to fix this in a general way.
  1. Install Microsoft Office
  2. Install each Adobe application as required in your deployment scenario
  3. Search in each Application bundle for a file containing the string SelfHeal.xml
  4. In each file, search for the following snippet:
    							requiredYES

  5. Change it to the following for each occurrence (there may be more than one)

    							requiredNO
     
  6. Do this for each SelfHeal file, for each Adobe application.


Add as favourites (115) | Quote this article on your site | E-mail

Comments (3)
RSS comments
1. 15-03-2007 13:51
Please flesh out this article a little more. How can SelfHeal "severely impact Enterprise deployments"? 
 
Does this have anything to o with repackaging Reader 8? If so could we get a follow-up on properly repackaging Reader 8? 
 
Thank you.
Joe
2. 15-03-2007 17:36
In my experience, SelfHeal is bad for non-administrators, since the application is trying to write to the /Library/ folder, which non-admins can't write to. Acrobat 7 Professional had this problem; the solution was to edit the CS2EnuProSelfHeal.xml file. On startup, the application constantly asks for an administrator's password so that it can "fix" itself.
Mark
3. 26-07-2007 15:10
Has anyone got a tip on how to fix this for version 8.x? 
 
We've tried pretty much every 'solution' we can find, but still no luck...
Daniel Farnworth

Only registered users can write comments.
Please login or register.

Powered by AkoComment Tweaked Special Edition v.1.4.4

Last Updated ( Sunday, 20 May 2007 )
 
< Prev   Next >