Printable View
I am so pleased that Adobe be familiar with there is a tribulations. It is presently too terrible that they do not care regarding providing a cure. I am forced to install Acrobat 9 onto a numeral of systems in school surroundings. This means that there might be more than a few hundred users of a couple hundred systems and each solitary non-admin user must be authorized to utilize Acrobat 9 by an administrator.
The tribulations were first exposed when we went to Adobe CS 3.3. At that time I was forced to downgrade back to Acrobat 8. That worked extremely well and provided a work approximately for the tribulations. At present I determine to be getting ready for the next semester and CS 4. The tribulations tranquil exist months afterward. Their "cure" does not run by means of these accounts in view of the fact that it tranquil asks for an admin account to create the desirable changes.
This is yet additional tribulations in that there are in addition troubles, as documented in this discussion that managed mobile accounts by means of a home directory on a server do not run. That come into view to be yet an additional tribulations that Adobe chooses to ignore. The similar exact "Admin needed" tribulations in addition exists on local accounts so it does not seem to have anything to do by means of being on a server based home directory. If we, the end users are being extravagance similar to unwanted beta testers, how long previous to we say "To H by means of Adobe".
For doing that you have to do the following. Pressing the "Cancel" switch when this prompt is obtainable determine to cause the prompt to not present itself upon succeeding launches of the submission. Make available the username and password of an administrative user. Then you have to log into the apparatus as the similar account that was used to install Acrobat 9.0. Adobe is conscious of this tribulations and looking for an additional permanent explanation.
I have comprised to install Acrobat Pro 9 and Reader 9 on more than a few Macs in our student system labs at a large state university. I have tried each fix subsequent to researching the net and acrobat forums. At present it is not probable to open and utilize Acrobat Pro 9 (Mac G5 working 10.5.5) when logged into one's user account. Merely when logged in as the admin be able to the software be used. In view of the fact that we have approximately 400 users, it would be insane for me to sit down and log in by means of every account in order to fix these tribulations. And I would not always be there to help a student trying to open Acrobat 9 additional than getting a prompt to enter the admin name: and password. None of the solutions Adobe recommends determine to run. It is predominantly absurd is not that the tribulations.
I am having the similar tribulations in my labs, having installed Acrobat 9 as fraction of the CS4 package. The whole thing works extremely well on the master apparatus, additional than not on several of the additional machines using the similar image (created using Disk Utility, scanned for software restore). Interestingly sufficient, I did not have these tribulations when I installed the version or description of 9 that came as an upgrade to CS3. I am extremely interested in several solutions that might be found, and determine to post several fixes I stumble across. It is frustrating that these tribulations reappeared the entire in excess of again.
You have to Edit AcroEFGPro90.xml and AcroEFGDist90.xml which be able to be originated in Contents > MacOS within the Acrobat and Distiller apps correspondingly. Scroll down until you get to the fraction that references SelfHeal for each line that references SelfHeal, revolutionize the "Requires" tags from "YES" to "NO" for the entire of the file resources. I was capable to substantiate that this fix works (at least for Acrobat Pro have not tried Distiller yet, additional than it be supposed to work), and to apply it successfully to additional apparatus.