Loading

Follow Us

Follow us on Spiceworks

Subscribe by Email

Your email:

Browse by Tag

Current Articles | RSS Feed RSS Feed

Install Java Silently - Deploying JRE 6 update 22

  
  
  
  

Install Java silently | PDQ Deploy

NOTE: JRE 6 update 23 has a different method of silent installation than update 22.

Regular Java updates can be a tedious chore for sys admins to deal with. Sometimes the updates can conflict with previous versions, or more likely, conflict with applications that were built for previous versions of the JRE.

Let's tackle the easy part; installing Java silently to multiple computers simultaneously. As we do with most of our video examples, we'll be demonstrating the installation with our free product, PDQ Deploy.

Download the updated JRE. We're using 6 update 22 in this example.

The file that you download is a self-contained .exe. Within the exe is the installation MSI. Oracle is continuing this approach. While it is possible to extract the MSI, it's not recommended. There are other actions that the EXE is taking.

Since it's not a native MSI, you won't be able to use the integrated MSI handling withing PDQ Deploy, however you can still pass MSI parameters for the deployment.

We have a video demonstrating the deployment of Java, as well as the method for determining the out-of-the-box parameters, or switches, that you can use to install Java silently and to suppress any required reboot.

Next step: troubleshooting. A user recently experienced the lovely and ever detailed error 1603 when deploying Java 6 update 22 using PDQ Deploy. As has been discussed on this blog, the 1603 error is generic, but it often means that the installation was expecting something that it didn't have access to, often a parameter or switch.

Be sure to use the correct switches. You can get the dialog for approved switches by running the JRE in a command window and entering a

/?

before hitting Enter.

The switches to install JRE 6.22 are

/quiet /norestart

If you're discovering that the installation is failing on some of your systems, be sure to turn on logging. You can do this using the following:

/quiet /norestart /l* c:\windows\temp\JRE-6.22.log

Java can be a beast to deal with sometimes. Our user discovered in their log file two different errors which had a lot of chatter on the Java forums. There were numerous work-arounds, but all of them had quite a bit of work involved. (Welcome to the world of Java.)

If you have questions regarding installing Java, or if you'd like to see video examples of other silent software installations, please let us know.


Follow me on Twitter @ShawnAnderson

Get your free copy of PDQ Deploy today.

Comments

With PDQ Deploy you can: 
Deploy MSI, MSP, MSU, EXE and Batch installers. With batch installers are included the .vbs script?
Posted @ Wednesday, November 03, 2010 7:11 AM by more
You are correct - within batch simply call cscript vbs_script. Be sure to use the silent //B and //Nologo options. 
 
Thanks for reading, 
 
Shawn Anderson
Posted @ Wednesday, November 03, 2010 10:07 AM by Shawn Anderson
i use the .vbs script to install printer driver and create an ip port. if i run locally the command on the computer all ok. the deploy instead dont'work. it's a xcopy like problem? there is no desktop associated to the service account with pdq is running? with a group policy computer startup script work instead. why?
Posted @ Thursday, November 11, 2010 5:44 AM by more
Correct, there is no desktop associated with PDQ Deploy (since it runs as a non-interactive service). What parts of your script are failing?
Posted @ Sunday, November 14, 2010 8:47 PM by Shane Corellian
the script - goo.gl/wg304 
so the gpo computer script not runs as a non-interactive service? 
i notice that many script i use with gpo don't work if deployed with pdq.
Posted @ Wednesday, November 17, 2010 4:08 AM by more
Depends on the context of the GPO. If it is executed as a user-level GPO then the script is run in the user context (logging on user). Looking at your attached VBS script I see that you are configuring printers. Printers are maintained at the User level not the machine. This script would not work as you expect if you run it from PDQ Deploy.
Posted @ Wednesday, December 08, 2010 12:07 PM by Shane Corellian
i run this script as gpo computer startup script. standard user account cannot install driver for lacks of privilege.
Posted @ Sunday, December 12, 2010 1:14 PM by more
Comments have been closed for this article.