), granted SYSTEM user full control of AIP and a few other steps. I've tried this without the TARGETDIR and PATCHAIP variables, enabled logging (/lv*. Here is the command (including prompt) I'm using from a command prompt with D: the selected drive and CD'd to the AIP path:ĭ:\managedsw\acrobatpro\9>msiexec /p F:\path\to\patches\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=D:\managedsw\acrobatpro\9 PATCHAIP=1 Yes, the file exists in that exact location (D: is not a mapped network drive or a substituted drive letter) and I can definitely access the file. Verify that the file exists and that you can access it."
When trying to patch my Acrobat Pro 9 AIP (current version of AIP is 9.0), I keep getting an annoying "Error 1305: Error reading from file D:\managedsw\acrobatpro\9\AcroPro.msi.   Installing from an AIP, it would be about 1,3GB to transfer to each You are talking about an embedded CAB.   However, we use a slightly changed wimakcab.vbs, which puts higher values for CompressionLevel and CompressionMemory into the DDF file.   This reduces the load by more than 1500 files and over 200MB!   Otherwise the patches are only chained up and are applied on That means, i can remove the UpdateFiles safely? I setup the MSP patches to 9.0.0 AIP with PATCHAIP=1. Now to test transforms.Ĭ:\AcrobatPro9>msiexec /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIPĬ:\AcrobatPro9AIP>msiexec /p c:\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1Ĭ:\AcrobatPro9AIP>msiexec /p c:\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install.logĬ:\AcrobatPro9AIP>msiexec /p c:\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install.logĬ:\AcrobatPro9AIP>msiexec /p c:\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install.logĬ:\AcrobatPro9AIP>msiexec /p c:\AcrobatPro9\AcrobatUpd931_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install.log I will likely just rebuild the entire thing.
Thanks for that tidbit I am aware that subsequent quarterly updates will require removal of security patches before application.
Switching to the aip dir before installing patches allowed the AIP to get patched and built. Hope, this gives some input here and there. We tested that and it never worked, because an CA, which checks the certificate in the original MSI, doesn't like that. Installing from an AIP, it would be about 1,3GB to transfer to each You are talking about an embedded CAB. However, we use a slightly changed wimakcab.vbs, which puts higher values for CompressionLevel and CompressionMemory into the DDF file. To reduce the network load, one can CAB that stuff up again. This reduces the load by more than 1500 files and over 200MB!Ĥ. If you want to get rid of all the patch files, you can delete them from the file table or disable the feature UpdateFiles.
Otherwise the patches are only chained up and are applied on the fly, while installing.ģ. To get the AIP REALLY patched, you need to set the property PATCHAIP=1 on the command line! As Joe already pointed out, the correct sequence of patching is crucial!Ģ. To get a useful version of Acrobat Pro 9.3.1, one has to invest quite a bit.