Adding the MSP file into the Customization wizard (Files and Folders), into the installation directory, and then using command line install (Add application). Running the update MSP file after the customized install This has worked for the last year and a half, until trying to install the latest security update, Version 2015.006.30306 (Classic track).
#ADOBE PATCH INSTALLER EXE LICENSE KEY#
We are using the Adobe Customization Wizard tool, and have set our deployment to Grant Offline Exception (with the enterprise license key added). I think it's the update itself that is resetting the sign-in requirement.
#ADOBE PATCH INSTALLER EXE HOW TO#
I have attempted uninstall and reboot and cleaning the registry of previous installation of Adobe DC Pro without any luck.Ĭan someone provide guidance on how to create a new customized install with the latest patch and still have the Adobe Sign-In option disabled? Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package." However, when I run this command, I get the error: mst file was created by the customization tool. I am trying to use: msiexec /i acropro.msi PATCH="Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst" Ideally I'd like to make a new customized installer package as this allows us to disable the Adobe Sign-In feature, which our agency will never use. I now need to update this package with the latest patch from Adobe to correct a recent security patch. I have used the Adobe customization tool to create a custom install package. We are using a stand alone version of Adobe DC Pro ( 15.006.30033.2205) (no other Adobe products).
0 kommentar(er)
