Predeployment configuration in an enterprise environment can be a complex process. Use the following checklist prior to modifying and deploying the installer.
If you already know the details below (e.g. your product track and license type, downloads you need, and so on), you can probably skip this guide.
Product type and track¶
There are three DC products:
Acrobat Pro and Std require a license.
Acrobat Reader requires a distribution agreement.
… and each belongs to one of two tracks: Continuous or Classic:
Continuous track: Recommended. Offers frequent updates and new features.
Classic track: The legacy method. Quarterly updates. No new features.
License options include the following:
Named user licensing (NUL) Recommended: Signing in with a supported ID type licenses the product. You manage users and groups via the Admin Console.
Serialized: License the product with a physical key. The Continuous track does not support serialized licensing, and license keys are gradually phasing out.
Feature restricted licensing: An alternative to serialized and NUL which is useful when end users either don’t have access to the internet or are not allowed to use online services.
Your organization has likely already selected a licensing program. Each program supports different tracks and features which may have ramifications for your deployment.
If you’ve received the Acrobat installer as part of a Creative Cloud package, customization may require extracting the MSI or downloading a standalone installer.
New install, upgrade, or update?¶
Recommended: Install new, major versions on a clean machine.
Verify download authenticity¶
If you need to verify the installer’s authenticity, check its signature using third party tools.
Back up the installer¶
As a best practice, backup your original installer and any related files. For example, if you use the Wizard and deploy with an .mst file, save the .mst along with your original .msi.
Expand the installer?¶
Some deployments use the .exe installer which is essentially a compressed package containing an .msi and other files. Some installs require .msi access. For example, using the Wizard involves loading the .msi into the app. To access the .msi, use 7-zip to expand the .exe package.
Security and update bulletins¶
Subscribe to the security notification service to receive an email whenever a scheduled update or patch is available.
You are now ready to (optionally) configure the installer.