Software Deployment

I have no experience using the setup.ini. But is there a reason why you cant just create an Administrative Installation Point and patch that one up before deploying?

We do have a recommended streamline policy to chain installs instead of creating AIPs...So the boostrapper via SCCM is the first option to deploy in my environment ..

Just noticed that you wrote "re-install". Are you sure that the Setup.exe takes the PATCH line in the ini-file in considerations when re-installing?

you could try to create a vbscript that installs the MSI first and the MSP's afterwards, if this works i would think that the Setup.exe aren't able to handle Patches during re-install.

/Matias

Yes the bootsrapper installer (setup.exe) is suppose to read the setup.ini file and then deploy all missing acrobat updates listed in the .ini file.
But Thats not working..Its as if the setup.exe is not reading the .ini file..its just running itself only.
By the way, .vbs is not allowed in my environment..


I am having problems deploying msp patches using Adobe Acrobat Pro 9 Bootstrapper install. I am using the setup.ini shown below.
Each time I run the setup.exe it just re-installs the existing orginal Acrobat 9 without deploying the listed msp patches under PATCH below.
Any help will be greatly appreciated.

[Startup]
RequireOS=Windows XP
RequireMSI=3.0
RequireIE=6.0.2600.0
[Product]
msi=AcroPro.msi
PATCH=AcroProStdUpd910_T1T2_incr.msp;AcrobatUpd911_all_incr.msp;AcrobatUpd912_all_incr.msp;AcrobatUpd913_all_incr.msp;
AcrobatUpd920_all_incr.msp;AcrobatUpd930_all_incr.msp;AcrobatUpd931_all_incr.msp;AcrobatUpd932_all_incr.msp;AcrobatUpd933_all_incr.msp;
AcrobatUpd934_all_incr.msp;AcrobatUpd940_all_incr.msp;AcrobatUpd941_all_incr.msp;AcrobatUpd942_all_incr.msp;AcrobatUpd943_all_incr.msp;
AcrobatUpd944_all_incr.msp;AcrobatUpd945_all_incr.msp;AcrobatUpd946_all_incr.msp
[Windows XP]
PlatformID=2
MajorVersion=5
MinorVersion=1
ServicePackMajor=2
[MSI Updater]
Path=WindowsInstaller-KB893803-v2-x86.exe

Tried using quotes as in: PATCH="<Patchsequence>" ?

ORIGINAL: zerville

By the way, .vbs is not allowed in my environment..


Holy hand grenade...

By the way, .vbs is not allowed in my environment..In your packages:
- Assign a new extension and associate it with CSCRIPT.EXE (and WSCRIPT.EXE if you need that, too). I use SVB.
- Extract and run the .SVB
- Delete the SVB
- Remove the association

Your QA people are too stupid to notice stuff like that.

Next stage:
- If you do not already own one, purchase The Packager's Baseball Bat
- Find the idiot who made that ruling
- Begin his (it will be a "he", for certain) education

Not sure about this method but its worth a try:

Try using a renamed INI file and remove your setup.ini then specify

/ini "PATH"
Relative or absolute path to an alternative (different) Bootstrapper INI file. The CmdLine of alternative INI will be ignored.
(got this from http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/reader/pdfs/deploying_reader9.pdf)

This way we can force the setup.exe to check for our renamed INI, if the in a case where setup.exe is not able to read from setup.ini that you created. Kill me if I wrong ;D

Use to pin point the exact problem why setup.exe doesnt take INI that you created
/l
Enable Error Logging. Log file Bootstrap.log will be generated in temp directory.