Acrobat Pro DC (installed via CCP) requesting sign-in

[Ric5]

Acrobat Pro DC is requesting a sign-in when it's part of a package build by CCP. The sign-in prompt is popping up about 15 seconds after Acrobat DC launches.  As with KuNiT21, I have an msi call to install the main group of apps with a second to install Acrobat DC and apply my customized mst file. Per this help file: Creative Cloud Help | Using Adobe Exceptions Deployer I tried running the Acrobat installer in the Exceptions folder first, but it then gives me a "[serial number] Error" error when I do.

start /wait msiexec /i "Exceptions\APRO15.0en_US\Adobe Acrobat\AcroPro.msi" /qb TRANSFORMS=AcroDC-CCpcc.mst

start /wait msiexec.exe /i "Build\AdobeCC2015_fullW64.msi" /qb

When I try running the same Acrobat install after the main install, I don't get the serial number error but Acrobat requests  a sign in to CC. Because this is for a college computer lab installs, the sign-in prompt is pretty much a show-stopper for us.

Could somebody please clarify this paragraph from the helpx file linked above?

For Acrobat DC, Exception Deployer Application is not required. For Acrobat DC, you only need to run the setup.exe, which ensures Acrobat DC is installed. However, for the EULA, registration, and updates suppression on client, you need to run the main CCP package msi after running the Acrobat DC setup.exe.

Thanks,

Ric

[adam_bise]

Try uncheck the option for creative cloud application in the first page of the packager.

Also try..

"Exceptions\APRO15.0en_US\Adobe Acrobat\setup.exe" /sAll /rs /msi EULA_ACCEPT=YES TRANSFORMS="path\to\transform.mst"

msiexec /i "Build\AdobeCC2015_fullW64.msi" /qb

(If any additional apps in the exception folder)

"Exceptions\ExceptionDeployer.exe" --workflow=install --mode=post

You can disable all online services in your transform, but removing the CC app from the packager should do the trick.

[Ric5]

Adam,

Thanks for the quick reply. I gave this a try interactively, replacing the transforms path with mine. I'm still getting the serial number error as before. The error message again displays displays the correct Adobe CC serial number. (The only way I can get this to show up is by changing one of the switches to /sPB.) The last time I saw this error was with the standalone installer I built and it indicated that the msi I had wasn't valid for our ETLA license key.

Ric

[adam_bise]

Only other thing I can think of is maybe you had specified a serial in the transform.  Try removing that, or removing the whole transform.

I don't remember where, but somewhere in the documentation it said to not enter a serial in your transform.

[serewrw]

I've got the same problem. I used the CPP to create silent setups for Acrobat DC and Photoshop. I then ran the exception deployer (in pre-install mode), the MSI and the exception deployer (in post-install mode). When I start Acrobat DC, I'm getting the "sign into Creative Cloud" popup. We've got an educational license, our students/teachers don't have to sign in to CC.

What's the fix?

[TisButaBatch · Accepted solution]

If you plan on installing just Acrobat DC, create a separate package only select Acrobat DC. Although I'm using SCCM 2012r2 to deploy these packages, I opted to use a simple batch file to run the installation from the distribution point rather than downloading over 5GB to the local drive. Below is an example of the batch file for installing Acrobat DC only....you will note I'm first running the Acrobat DC setup.exe from the deployment package “Exceptions” folder and then running the setup.exe from the “Build” folder. This is necessary to ensure the enterprise licensing is applied. If you only run the setup.exe from the exceptions folder, the licensing will not be applied and you will be prompted to log into the Creative Cloud and prompted again for a serial number.

Acrobat DC

@echo off

"\\(Deployment path)\Exceptions\APRO15.0en_US\Adobe Acrobat\Setup.exe" /sALL /rs /msi EULA_ACCEPT=YES

"\\(Deployment path)\Build\Setup.exe" /sALL /rs /msi EULA_ACCEPT=YES

exit

The process is similar for installing the other applications. You must first install all applications in the “Exceptions” folder and then run the setup.exe from the “Build” folder. Here is an example of our batch file for installing Acrobat as well as other core applications.

Acrobat Dc and Dreamweaver

@echo off

"(Deployment path)\Exceptions\APRO15.0en_US\Adobe Acrobat\Setup.exe" /sALL /rs /msi EULA_ACCEPT=YES

"(Deployment path)\Build\Setup.exe" /sALL /rs /msi EULA_ACCEPT=YES

exit

Note: You can still customize Acrobat DC using the “Acrobat Customization Wizard DC”, but do not enter a serial number.

I hope this helps. I've deployed the entire CC suite this way.

[Ric5]

tis,

This looks good to me (and I marked it Correct), though I wound up going about things slightly differently. I still don't have a good grip on the use cases for setup.exe vs msi (to be honest, I'm mostly a Mac guy) but I did get the following to work in my tests:

1. start /wait Exceptions\APRO15.0en_US\"Adobe Acrobat"\Setup.exe /rs /sPB /msi EULA_ACCEPT=YES TRANSFORMS="Exceptions\APRO15.0en_US\Adobe Acrobat\[my-mst].mst"
2. start /wait msiexec.exe /i "Build\[my-built-package].msi" /qb
3. start /wait Exceptions\ExceptionDeployer.exe --workflow=install --mode=post

I used the Acrobat Customization Wizard but did not enter a serial number.

We're not using a deployment tool like SCCM. Basically, the techs will use the installer to put the software on a prototype which is cloned to labs with Ghost. They like seeing a progress bar to know that something is happening. The only way I could get line 1 to run without an error in a script was to quote only "Adobe Acrobat" in the path.

Ric