Monday, 16 April 2012

Non-English Adobe Reader X reverts to English when using AppSense Application Manager

When you are deploying a non-English version of Adobe Reader X that is managed by AppSense Application Manager, you may notice the language setting reverting to English. Additionally, the text for all menu items inside the program may appear as blank. Providing the user with administrative-level rights, or stopping the Application Manager service, appears to rectify the issue.

This is caused by Acrobat Reader X creating a cache folder within the user's temporary application data folder, then attempting to execute these files. As the files are owned by the user, these are blocked by Trusted Ownership.

There are a number of solutions to this issue, choosing which is a matter of security stacked up against manageability. The model chosen for your application management design will dictate which one is most relevant.

The most secure solution is to add a signature item for each of these files to the Accessible Items either directly, or via a new Group within Application Manager | Library | Group Management, then adding this group to Accessible Items of the relevant rule.

To capture the files required:

1. Logon as an administrator and launch Adobe Reader X (AcroRd32.exe) then close

2. Copy the files from the following folder to a location accessible from the Application Manager Console:

Windows XP / 2003: %Userprofile%\Local Settings\Application Data\Adobe\Acrobat\10.0\Cache

Windows Vista / 2008 / 7 / 2008R2: %localappdata%\Adobe\Acrobat\10.0\Cache

3. Using the Add Signature Item within the Application Manager console, browse the location of the copied files, and change the File Types drop-down from Executable Files to All Files, then add each file.

Note: Using this approach may require additional signatures to be added for each language and each version of Adobe Reader X.

A less secure, but easier to manage approach, is to use a Process Rule for Adobe Reader X as follows:

1. Create a new Process Rule and add the following executable in the Processes list (you could alternatively use a signature of the process itself if required for added security):

%programfiles%\adobe\reader 10.0\reader\acrord32.exe

2. Within the Accessible Items for this process rule, add either the folder, or each individual file within this folder, with Trusted Ownership disabled, or signature items as above. For example on a German OS (for the least secure but simplest approach):

%userprofile%\lokale einstellungen\anwendungsdaten\adobe\acrobat\10.0\cache

One final option, if security is of the highest priority, is to combine the aspects of both of the above, by using a Process Rule where a Signature Item is used within the Processes List, and the signatures for each of the cache files within the Accessible Items list (either directly or via a Group Item from the "Group Management" Library)

Once you have configured this, your non-English application should once more be happily displaying in the language you originally intended it to.

No comments:

Post a Comment