Caching of Installer files for AIP Installation of Acrobat DC using transforms

[xxpluckyxx]

I have created an AIP on the network, and have 2 different transforms to apply to the same AIP for Acrobat Pro DC.

I have used the Acrobat Customization Wizard to create a transform, and want to cache the installer files for future updates.
The install works fine, but the only files that end up in the C:\Program Files (x86)\Adobe\Acrobat 2015\Setup Files\ directory

are a subdirectory with the GUID, an empty Transforms directory, and an 'Enterprise.mnt', but nothing else.

The AIP is an extracted and patched AIP.  The MST does include the setting 'Checkbox - ENABLE_CACHE_FILES - YES'

msiexec /i acropro.msi TRANSFORMS=AutoUpdate.mst /qr

Any help is appreciated!

[xxpluckyxx]

Some quick further information: I just noticed that BOTH Transforms have 'Cache Installer Files' set to True, but NEITHER actually does so.  All other options from the transforms appear to apply correctly, but none of the installer files are copied to the PC.

The AIP was created using the standard:

1. Msiexec /a AcroPro.msi
2. Apply patches with the following command: msiexec /a <msi filename> /p <patch_file>

[Mohd Amish · Accepted solution]

"Enable Caching of installer files" option is specific to Installer caching (Installations done via MSI route or Setup.exe). It will not work for installations using AIP.

If this option would have worked with AIP, it would cache the installer files (package used to create AIP) and not the AIP source files (created via msiexec /a AcroPro.msi)

For Installations done via AIP, actions like product repair etc require AIP source files on the network and not the installer files.

[xxpluckyxx]

Thank you for the answer.
This doesn't seem useful for Enterprise environments that need multiple 'styles' of install?  I may be missing something then, but is there a better method for using a patched install point to install from, some of which will 'auto update' and some of which won't?

[Mohd Amish]

Product installed via AIP (Administrative Install Point) will not "auto update". One has to apply the successive patches using an AIP. For more details please refer to: Administrative Installation Points — Enterprise Administration Guide

[xxpluckyxx]

Thank you for your replies.

That is still most unfortunate that the options settable via the Customization Wizard are dependent on the type of .msi file they are attached to.  After reading the article, this may be the relevant line

'If you previously deployed using an AIP, then you must apply the successive patches using an AIP.'