For info on how to fix the Java Install error 1618 visit this blog post.
Here are two ways to silently install Java to all the Windows computers in your company.
The first way shows the steps to create a Java deployment. The second way is for those who do not want to spend the time on each step. It involves using our pre-made Java deployment package.
Create your own Java installation
If you are using the free mode of PDQ Deploy, or if you are using pro mode but do not have a subscription to the package library, you can still create a Java installation. Just follow these steps.
1. Download the Java update from java.com.
2. The file you download will be an EXE. To get silent installations with some additional features you will need to pull the MSI from within the EXE.
To accomplish this, run the EXE on a test computer. (Just double click the EXE and move to the next step).
When the installation wizard starts, DO NOT proceed. By starting the installation wizard you have caused the Java MSI to be extracted to a special directory on you workstation.
To find this directory open your run command and type in %LOCALAPPDATA% and hit enter. This will open a window to your appdata\local directory. Go back one level and go into LocalLow. Inside this directory you’ll see a subdirectory called Sun. Drill down into the Sun\Java directory until you see the jre1.7.0_25 directory. This directory contains the Java .msi and .cab files needed for the Java installation.
3. Copy the jre1.7.0_25 directory to another directory on your computer. After the copy you can cancel out of the Java install wizard that you started a minute ago.
4. Assuming you have PDQ Deploy installed (if not, you can get it here), right-click on the newly extracted Java .msi and click Deploy with PDQ Deploy.
5. Click “Run” on the open file dialog. This will open PDQ Deploy.
6. Click Step 1. In this window do the following:
Check the Include Entire Directory checkbox (under the Additional Files field).
Enter the following in the Parameters field:
JU=0 JAVAUPDATE=0 RebootYesNo=No
Your window should look somewhat similar to this.
You are now ready to deploy.
Skip all the steps – just deploy Java
If you have PDQ Deploy pro mode with an active subscription to the Package Library you can simply go to the Package Library (from within PDQ Deploy) and find the Java packages that are ready for downloading.
Lex demonstrates using the Package Library to push out Java 7 Update 25.
Killing browsers and auto-updates
ONE VERY BIG note. If you receive an error 1603 when deploying to some computers, that’s a sign that the computers may have had some Java applets running. This is usually the case when they have browsers that are running.
This is a big reason that we provide pre-made Java installations for our Package Library subscribers. We add some steps like killing browsers, removing the Java scheduler, removing from Run, and disabling auto update.
If you hit errors on your deployment you may want to try adding addtional steps (pro mode required) to kill browser sessions. If you are using free mode, you would want to create a new package that calls a batch script that runs the taskkill command (free mode is limited to a single install step in each package).
Java installation errors (1603, 1618)
If you get errors (1603, 1618) then you will want to consider removing older Java entries. This is done by removing the keys in the registry. It’s an involved process that sys admins love to hate.
NOTE: If you are a subscriber to the Package Library we have done this for you already in the Java ALTERNATE package (Basic subscription req’d). The ALTERNATE package goes through the registry and deletes previous entries from earlier updates to Java 7. Our users report a very high success rate when using the ALTERNATE pacakge on machines that failed to install recent Java updates. (Please use the normal Java package first. The ALTERNATE should only be used on those systems that fail).
PDQ Deploy Pro Mode & the Package Library
To use our pre-made Java packages (plus a lot of other common 3rd party apps) requires PDQ Deploy Pro Mode along with a Package Library subscription.