hi all,

i think this is a good place for my question.

i have a package for office 2003 to which i need to add the sp3. but i have a problem with it.

the way we are distributing packages does not allow me to use /qn for a silent install for a msp file. is there some other way to run it silently? a command line option perhaps?

i can pass parameters to the patch, but i cannot use the msiexec switches. as an example, i already pass REBOOT=ReallySuppress to it.

i was wondering if there is a property i can use, something like SILENT=True or similar.

thanks!
0 Comments   [ + ] Show Comments

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.

Answers

0
i can pass parameters to the patch, but i cannot use the msiexec switches. as an example, i already pass REBOOT=ReallySuppress to it.Eh? Those statements are directly contradictory. Either you can pass parameters to MSIExec (as in 'REBOOT=ReallySuppress') or you can't!
Answered 02/24/2010 by: VBScab
Red Belt

Please log in to comment
0
i can pass parameters but not switches

parameters are properties, but switches are what follow the /

in this case, no way to add /qn

thanks!

look here
Answered 02/24/2010 by: kardock
Second Degree Green Belt

Please log in to comment
0
You can use the below code for installing the msi without passing any switches.

set obj = createobject("WindowsInstaller.Installer")
obj.uilevel = 2
obj.InstallProduct("path to your.msi")

I guess this may not be the solution but just a try.
Answered 02/25/2010 by: joseph
Orange Belt

Please log in to comment
0
unfortunately no, it's not the solution.

as you can see in the printscreen i have attached, the only thing i can do to update office with our distribution tool, is to have command line options.

this is a major downside for our distribution tool, but since it was bought for quite a few bucks, i have to live with it :(

thanks!
Answered 02/25/2010 by: kardock
Second Degree Green Belt

Please log in to comment
0
my hopes of having an answer were low. very low. i'm sure there is no answer to my question but i needed to ask, just in case.

i'm totally screwed!

thanks anyway!
Answered 02/26/2010 by: kardock
Second Degree Green Belt

Please log in to comment
0
Kardock - why not just use a customization?? For example (and i'm going off memory here, so bits may be wrong):

Go to the customizations tab
Create a new customization, give it a name at the top, say 'installOffice2003SP3'.
There is an 'Add' button (or similar) next to 'Exe/Bat' - click add, and add your MSP.

Now......(Assuming the msp is called MAINSP3.msp)

Change the 'Exe/Bat:' field from 'MAINSP3.msp' to: $SYS.SYSTEM\msiexec.exe
...and in your arguments field, set it to: /p MAINSP3.msp /qn

and schedule it after update or whatever.....to be safe, i'd flag the 'ignore return code' box.....

[:)]
Answered 02/26/2010 by: captain_planet
Second Degree Brown Belt

Please log in to comment
0
the only thing i can do to update office with our distribution tool, is to have command line options. You could create a script which contains (the correct) installer commands and run THAT from the command line, though, couldn't you? As in, CSCRIPT whatever.VBS?

@Joseph, the Op wants to patch an existing product, not install one so would have to use the patch application method of the Installer object, ApplyPatch.
Answered 03/02/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity