I am testing ways to roll out java updates. I looked at the package KB for java 6 update 22 and there are two entries under the command lines section.

Entry 1
jre-6u22-windows-i586-s.exe /s /v "/qn ADDLOCAL=ALL IEXPLORER=1 JAVAUPDATE=0

Entry 2
msiexec /i jre1.6.0_23.msi /Passive

I understand what each entry is executing. How is it executing each entry, a batch file or command file? How are you applying the batch file to the clients? Are you adding the batch file to a logon GPO?

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
When you need to deploy a msi then I would prefer to deploy it with a Software Installation Policy (GPO). There are multiple articles that can be found on the internet on how to do that.

When installing an exe you can use a Startup Script or Logon Script. You can use a commandfile but a vbscript won't display that ugly black cmd-box during installation.

I assume you don't have tools such as SCCM or SMS. That tools are far more advanced.

Regards,
Peter Baars
Answered 03/17/2011 by: pjbaars
Orange Belt

Please log in to comment
0
The EXE extracts and executes an MSI anyway. The '/v' switch passes arguments to MSIExec so the arguments you see after the '/v' can be applied to the second command line example (but minus the '/v', obviously).

Bear in mind also that the JRE MSIs are not "proper" MSIs but merely containers for a bunch of ZIPs and Custom Actions to extract files from those ZIPs.
Answered 03/18/2011 by: VBScab
Red Belt

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