adobe dc pro install patch update to customized install

Report · Mar 28, 2017

We are using a stand alone version of Adobe DC Pro (15.006.30033.2205) (no other Adobe products). Windows 7 32-bit environment. I have used the Adobe customization tool to create a custom install package. I now need to update this package with the latest patch from Adobe to correct a recent security patch.

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 am trying to use: msiexec /i acropro.msi PATCH="Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst"

The .mst file was created by the customization tool. However, when I run this command, I get the error:

"This patch package could not be opened. 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."

I have attempted uninstall and reboot and cleaning the registry of previous installation of Adobe DC Pro without any luck.

Can someone provide guidance on how to create a new customized install with the latest patch and still have the Adobe Sign-In option disabled?

Report · Mar 28, 2017

[moved from Installing, Updating, & Subscribing to Acrobat to Enterprise Deployment (Acrobat and Reader)]

Report · Mar 28, 2017

http://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/Customization%20Wizard%2011%20for%20Windows...

Report · Mar 29, 2017

Try this syntax:

msiexec.exe /i [UNC Path]/acropro.msi PATCH="[UNC Path]/Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst"

Report · Mar 30, 2017

Read through the customization document and it did not help with adding the msp to the existing mst.

Also just tried the command Steve Cordero provided:

msiexec.exe /i \\[servername]\IRM\Software\Software (Documented)\Adobe\Adobe Acrobat Pro DC\Adobe Acrobat\acropro.msi PATCH="\\[servername\IRM\Software\Software (Documented)\Adobe\Adobe Acrobat Pro DC\Adobe Acrobat\Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst"

When I ran this, I get the Microsoft dialog box with the various switches as if the syntax is incorrect.

Report · Mar 30, 2017

Tried something different. I copied the installation folder to my C:\ and ran the command line below. This appears to have worked. The About Adobe now shows the version as: 1500630280.

msiexec.exe /i C:\AdobeAcrobat\acropro.msi PATCH="C:\AdobeAcrobat\Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst"

Need to test for a few days to make sure the Online features don't kick in as I have seen happen before. I will keep you posted.

Report · Mar 31, 2017

Almost there. The install worked and it is updated. However, when I created the customized install (prior to the update) I disabled the Adobe Sign-In features. After I ran the msiexec command and installed the update, I get the sign-in prompt. If I say no, then Adobe just closes.

How do I disable the Adobe Sign-in prompt?

Report · Apr 04, 2017

You are talking about the Sign-in to Activate the software. This needs to be disabled in the original deployment package by using the Grant Offline Exception. If you have already deployed, then you can use the Adobe Provisioning Toolkit to do this, but it is a bit more involved a process and scripting would be involved.

Report · Apr 21, 2017

I did the following:

1) Created customized installation with serial number and suppressed Adobe Sign-In

2) Ran the msiexec.exe /i C:\AdobeAcrobat\acropro.msi PATCH="C:\AdobeAcrobat\Acrobat2015Upd1500630280.msp" TRANSFORMS="AcroPro.mst" in order to get the deployment updated

After step two the Adobe Sign-In has returned, even though the registry settings indicate it is suppressed.

I think I will need to steps for the Provisioning Toolkit and scripting you mentioned.

Report · Apr 26, 2017

I'm running into the same problem.

I think it's the update itself that is resetting the sign-in requirement.

We are using the Adobe Customization Wizard tool, and have set our deployment to Grant Offline Exception (with the enterprise license key added).

This has worked for the last year and a half, until trying to install the latest security update, Version 2015.006.30306 (Classic track).

I've tried:

- Running the update MSP file after the customized install

- Adding the MSP file into the Customization wizard (Files and Folders), into the installation directory, and then using command line install (Add application).

- Since the provisioning XML file also streams from command line in the Customization wizard, I've tried running the update before and after the provisioning file streams.

- Letting the application update itself on the application machine before capturing and deploying it.

All of these methods will update the application. They also all generate the Sign-in prompt after deployment.

Report · Apr 29, 2017

Glad to know I am not the only one with this issue. I too tried the before and after the provisioning file streams. No luck. Hope to find an answer from Adobe, soon.

Report · May 03, 2017

Now, I've tried:

- Re-generating the offline exception

- Streaming the provisioning XML file after application deployment (batch file)

- Setting the Customization wizard to delete the previous version of Acrobat

None of these worked either.

I have learned some things, though:

- I can deploy Acrobat with the update, and not get the sign-in prompt, to a machine that does not already have Acrobat (most of our deployments are to replace an existing version).

- The sign-in prompt is now an annoyance, not a complete stop. I can close it by clicking on the red X, and Acrobat will stay open.

Since I really have to get this update out, I have a decision to make. Remove Acrobat completely from all of its users (and deploy the update, or deploy it as, and warn them about the annoying sign-in popup.

Report · May 08, 2017

Interesting. The popup for sign-in happens for us. But if we click the red X to close that window, then it also closes Adobe entirely.

Report · Jun 29, 2017

I did the customized install, but after doing the patch update, the adobe sign-in kicks back on even though I have it completely disabled in the registry. So, Using the Adobe Creative Cloud, I created a generic account. Not ideal, but this appears to be the only way to get this to work in VMware virtual desktops.

Report · Oct 29, 2018

Hi there,

This might help...

https://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/Customization%20Wizard%2011%20for%20Window...

Page 2, section 1.3

1.3 MST usage
Once an MST is applied during an install another MST can't be used later during an update (say, to change one setting).
The way the Windows Installer Technology works is that during an update or repair, the installer references the MST file that the installation used when it was first installed.
The only way to use another MST it to uninstall the product and then reinstall with a new MST file.

So, by the sounds of it...

You have previously deployed a version of Acrobat with an MST applied?
You are trying to upgrade that previous install with a new patch?
While you are attempting the upgrade, you are also attempting to apply a new MST?

According to the docs, this isn't possible and you might need to run an uninstall/reinstall with the new MST.

I haven't tried this myself yet, but hoping that the above info helps.