Adobe Creative Suite 2.0 XML Configuration File and Silent Install
Hi,
I am deploying Adobe Creative Suite 2.0 (Windows XP SP1) to multiple users and am using the instructions outlined at: http://www.adobe.com/support/techdocs/331297.html
This works as intended, however is there an option you can set in the xml file (or elsewhere) so that it shows a progress bar for each msi or an overall progress bar?
Because the installation is running in silent mode (by default) the user/s wont be able to see what status the install is at and possibly try to run other apps before the installation has completely finished. I would also like to know if there is a section I can add to the xml file to make the machine reboot once the install is complete?
Thanks,
M
I am deploying Adobe Creative Suite 2.0 (Windows XP SP1) to multiple users and am using the instructions outlined at: http://www.adobe.com/support/techdocs/331297.html
This works as intended, however is there an option you can set in the xml file (or elsewhere) so that it shows a progress bar for each msi or an overall progress bar?
Because the installation is running in silent mode (by default) the user/s wont be able to see what status the install is at and possibly try to run other apps before the installation has completely finished. I would also like to know if there is a section I can add to the xml file to make the machine reboot once the install is complete?
Thanks,
M
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
goosey1
19 years ago
Your best option would be to write a script that monitors the setup.exe process.
You can also monitor the %temp% directory to see which products have completed installing if you want to get a bit fancy.
You can also monitor the %temp% directory to see which products have completed installing if you want to get a bit fancy.
Posted by:
MSI_repackager
19 years ago
Hi goosey1,
I have written a script using WinBatch that launches the setup.exe with the xml file, then cleans up some shortcuts at the end and reboots. At the moment it is just using a time delay during the install part as I'm not sure how to go about scripting monitoring the active process...? setup.exe doesn't stay in Task Manager for very long as it is msiexec.exe that does most of the work. What tool are you using to script with?
M
I have written a script using WinBatch that launches the setup.exe with the xml file, then cleans up some shortcuts at the end and reboots. At the moment it is just using a time delay during the install part as I'm not sure how to go about scripting monitoring the active process...? setup.exe doesn't stay in Task Manager for very long as it is msiexec.exe that does most of the work. What tool are you using to script with?
M
Posted by:
goosey1
19 years ago
I've used AutoIt to execute and monitor the CS2 deployment. setup.exe is an active process for the entire time as it triggers each individual msi and waits for a return code, setup.exe also delpoys the activation related files.
I have found that as long as you install one of the components (say Photoshop) with the suite installer and xml file, then you can deploy any of the other programs as individiual msi's using the following command line.
ARPSYSTEMCOMPONENT=1 ISX_SERIALNUMBER=0000000000000000000000000 SERIALNUMBER=0000000000000000000000000 SUITEMODE=1 ENCSERIALNUMBER=0000000000000000000000000 ENCRYPTED_SERIALNUMBER_INSTALLED=0000000000000000000000000 RUNNINGMCSUITEMODE=1 EULA_ACCEPT=YES ACSPRODUCTID=131 ACSSIFPATH=C:\PROGRA~1\INSTAL~1\{0134A~1\required\Suites.sif REBOOT=ReallySuppress EPIV=1 PP_LANGID=2057 ALLUSERS=1 USERNAME="" COMPANYNAME="" PP_LANG="en_GB" EPIC_EULA_ACCEPTED=1 EPIC_EULA_SELECTED=25 LASTVIEWEDEULA=0
Do a manual install of the entire suite and have a look in %temp%\SuiteInstaller2.0.txt, it shows all the command lines the setup.exe uses to install the msi.
I have found that as long as you install one of the components (say Photoshop) with the suite installer and xml file, then you can deploy any of the other programs as individiual msi's using the following command line.
ARPSYSTEMCOMPONENT=1 ISX_SERIALNUMBER=0000000000000000000000000 SERIALNUMBER=0000000000000000000000000 SUITEMODE=1 ENCSERIALNUMBER=0000000000000000000000000 ENCRYPTED_SERIALNUMBER_INSTALLED=0000000000000000000000000 RUNNINGMCSUITEMODE=1 EULA_ACCEPT=YES ACSPRODUCTID=131 ACSSIFPATH=C:\PROGRA~1\INSTAL~1\{0134A~1\required\Suites.sif REBOOT=ReallySuppress EPIV=1 PP_LANGID=2057 ALLUSERS=1 USERNAME="" COMPANYNAME="" PP_LANG="en_GB" EPIC_EULA_ACCEPTED=1 EPIC_EULA_SELECTED=25 LASTVIEWEDEULA=0
Do a manual install of the entire suite and have a look in %temp%\SuiteInstaller2.0.txt, it shows all the command lines the setup.exe uses to install the msi.
Posted by:
MSI_repackager
19 years ago
Cool, I'll have a play around with my script and see what happens. Thanks for your help.
M
M
Posted by:
goosey1
19 years ago
I would like to retract my previous statement of ....
I have since found that Photoshop does not work in this manner.
ie. Scenario 1. I installed Photoshop using the Suite Installer/XML, I then installed Illustrator with the above command line. Everything worked as expected.
Scenario 2. I installed Illustrator using the Suite Installer/XML, I then installed Illustrator with the above command line. Illustrator works, Photoshop doesn't.
Nice to see that Adobe are consistent.
The problem I am facing now is, say someone wants Illustrator, Photoshop, GoLive. Then later they decide they want to add InDesign and Acrobat. If you run the Suite Installler a second time, it just brings up the Modify/Repair/Uninstall dialog.
I have found that as long as you install one of the components (say Photoshop) with the suite installer and xml file, then you can deploy any of the other programs as individiual msi's using the following command line.
I have since found that Photoshop does not work in this manner.
ie. Scenario 1. I installed Photoshop using the Suite Installer/XML, I then installed Illustrator with the above command line. Everything worked as expected.
Scenario 2. I installed Illustrator using the Suite Installer/XML, I then installed Illustrator with the above command line. Illustrator works, Photoshop doesn't.
Nice to see that Adobe are consistent.
The problem I am facing now is, say someone wants Illustrator, Photoshop, GoLive. Then later they decide they want to add InDesign and Acrobat. If you run the Suite Installler a second time, it just brings up the Modify/Repair/Uninstall dialog.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.