Acrobat/Reader enterprise deployment troubleshooting tips

Troubleshooting tips

If you are deploying Reader or Acrobat across an enterprise to Windows clients or Terminal Servers and are encountering issues during the deployment, then this article will be useful for debugging such issues.

Adobe proivdes a tool called Tuner (Acrobat/Reader 7) or Customization Wizard (Acrobat/Reader 8+) to build transform files in MST format.  These transform files can then be bundled with the standard MSI installer package from Adobe, and when the installer is run, it will apply the custom settings in the MST to the standard installation.

If you are encountering problems with your MSI and MST files, then here are some troubleshooting tips: 

  • use install mode on terminal servers:
    • change user /install
    • change user /execute
  • check drive mappings for terminal servers:
    • Very often some other drive like “M:” is used as the boot drive (it would be drive C: otherwise). This is so that users can still see their local drive C: when in the WTS session.

  • put MST in same folder as MSI and run it using the command line:
    • for example: msiexec /i AcroRead.msi /t Custom.mst
  • check OS language versions as paths may differ i.e. C:\Programme instead of C:\Program Files
  • rebuild the transform file on the same OS as the target OS you are trying to deploy to
  • check the transform MST with ORCA as this will validate it and show the differences to the standard install

Additional Information

Interesting sites about deploying Reader in an enterprise and customizing with Customization Wizard:

http://www.adobe.com/products/acrobat/solutions/it/

http://kb2.adobe.com/cps/837/cpsid_83709.html

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)
Acrobat/Reader enterprise deployment troubleshooting tips, 10.0 out of 10 based on 1 rating

Comments are closed.