Hi There,

I trying to build a CS4 Design Premium package for deployment through SCCM. I have been following the steps in the following document

When I test my package by running "setup.exe --deploymentfile=install.xml" the installer runs and prompts for our serial number. I have already run "setup.exe --record=1" and entered the serial number during that setup. When I open install.xml in notepad, the serial number is in fact in the xml file as it should be.

If I run "setup.exe --mode=silent --deploymentfile=install.xml" CS4 successfully installs silently, but when I run one of its applications, it prompts me and gives me the options of continuing on my trial period, or entering my serial number.

Obviously I am missing something that is preventing the installer from picking up the serial number from install.xml.

Any thoughts or suggestions would be greatly appreciated.


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi Rosy,

I have worked with Adobe cs3 but not with cs4 hope this information will help you,
try to add the serial number in application.override.xml as per this link http://kb2.adobe.com/cps/400/kb400588.html.

Answered 02/03/2010 by: sunny07
Senior Yellow Belt

Please log in to comment
Another path altogether but you could try the Adobe CS4 Deployment toolkit. We have used this to deploy CS4 Web and Design Standard successfully via SCCM.
Documentation is pretty thorough but I would use a drive letter in the program properties of the sccm package. In doing so you must also change the <InstallerLocation> in AdobeUberInstaller.xml to point to your package id eg "<InstallerLocation>Z:\d0000123\"
Answered 02/03/2010 by: Lurch
Yellow Belt

Please log in to comment
Awsome, thanks for the quick replies. I had actually already attempted putting the serial in the application.xml.override. I gave it another shot this morning, but same old.

I downloaded the developer kit and voila, the installer works....now I just need to figure out the sccm part with the drive letter and having multiple installers for multiple locations with multiple licences....I can hear the ibuprofen calling my name.

Thanks again

Answered 02/04/2010 by: jrosenburg
Yellow Belt

Please log in to comment
In addition to this I found the following software items should be removed via the toolkit.
Adobe Air
Adobe Media player.

If you are deploying via sccm these products appear to attempt to connect to the internet via the default proxy logged in as system admin, if not set the Adobeuberinstaller stops running.
Answered 03/30/2010 by: Lurch
Yellow Belt

Please log in to comment