HOME




© 2017 Adobe Systems, Inc. All rights reserved.

Updated Aug 21, 2018.

Deploying Customized Installers

Once the project is saved, your modified installer is ready for deployment. For example, you can simply run setup.exe. The EXE reads the setup.ini file which contains references to your transform file (MST) and any needed updates.

Supported workflows include AIP-GPO, bootstrapper installations, and SCCM/SCUP. For details, refer to the Enterprise Administration.

Generate a transform file

A transform (.mst) file contains your modifications and any files added to the project (.msi) file. The Wizard updates the associated transform file every time you save a project.

To create a Transform file:

  1. Choose Transform > Generate Transform.
  2. In the Save dialog, browse to the desired location.
  3. Enter the transform file name in the Filename box.
  4. Choose Save.

You can generate a copy of an open transform file and then apply it to another project. In order to apply the new transform file to another project, you must open the new project and load the transform file.

Bootstrapper installation

You can use your customized MST for bootstrapper deployments. The bootstrapper Setup.exe file uses setup.ini as its configuration file. As you customize the installer with the Wizard, the Setup.ini file automatically updates. The Setup.exe file uses Setup.ini as it’s configuration file. Before deployment, open Setup.ini, verify it contains all the properties you need, and edit it as neccessary.

Setup.ini contains two sections:

  • [Startup]: Setup.exe first executes the Adobe flags for CmdLine. Do not place Adobe properties or MSI switches here; for example, you can use /sAll but not /qb!+ in this section.
  • [Product] Setup.exe then reads the [Product] section. There may be multiple [Product] sections depending what the EXE should invoke (other MSI’s or EXE’s). The CmdLine should only contain values supported by the item the EXE invokes. For example, when invoking an MSI (msi=AcroPro.msi), you can only use space-separated Adobe properties (flag/value pairs connected by an = sign) and MSI switches; for example, you can use /qb!+ but not /sAll in this section.

MST usage in Setup.ini

[Startup]
CmdLine=/sAll /sl "1031"
RequireOS=Win XP

[Product]
CmdLine=TRANSFORMS="AcroPro.mst" /qb!+
msi=AcroPro.msi
Languages=1033;1031
1033=English (United States)
1031=German (Germany)

AIP installation

You can use your customized MST in AIP workflows. Simply add the TRANSFORMS property to your command line call to msiexec.

For details, refer to the Enterprise Administration Guide at www.adobe.com/go/acrobatitinfo.

MST usage: In an AIP

msiexec /a PRODUCTSOURCE\<ProductName>.msi /p PRODUCTAIP\AdbeRdr1101_en_US.msp
msiexec /a PRODUCTSOURCE\<ProductName>.msi /p PRODUCTAIP\AdbeRdr1102_en_US.msp
msiexec /p AIPPath\<ProductName>.msi TRANSFORMS=PRODUCTSOURCE\<ProductName>.mst