How to deploy Java using Configuration Manager

8997

Welcome to the post that shows you how to deploy Java using Configuration Manager. In this post we will look at the steps for deploying Java using SCCM 1511. While writing this post, my configuration manager version is 1511. If you have configuration manager 2012 R2, you can still follow the same steps to deploy Java. When you download the Java installer, it’s an exe file. But there is a way to get the msi file. We will look at how to do that and deploy the Java using SCCM 1511. If you are not aware of what Java is, Java is a popular programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to data-centers, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere.

First we will download the Java offline installer. Click on the below link to download it.

Download Java 32/64 bit Offline

I have downloaded the 64 bit version of Java. You could download 32 bit or 64 bit based on your requirement.

How to deploy Java using Configuration Manager

Since the java software is downloaded as an exe file, we cannot extract an msi file out of it. To get the msi file you either need to install the java on one of the computer or you just need to run the executable(do not install it). When you install or run the executable, the msi file is found under the path %userprofile%>appdata>Locallow>Oracle>Java. Copy the java msi file to a shared folder.

How to deploy Java using Configuration Manager

How to deploy Java using Configuration Manager

Now we will see how to deploy java using Configuration Manager 1511. Launch the Configuration Manager console. Click on Software Library > Overview > Application Management. Right click Applications and click Create Application. In the create application wizard, choose Automatically detect information about this application from installation files. Provide the path where the msi file is located. Click Next.

How to deploy Java using Configuration Manager

Wait for the information to be imported. Once you see it’s successful, click Next.

How to deploy Java using Configuration Manager

Specify the information about the application such as Name, Publisher etc. For the Installation program, specify the command as

Click Next.

How to deploy Java using Configuration Manager

Complete the remaining steps and click Close.

How to deploy Java using Configuration Manager

The Java application is ready to be deployed. Right click the Java app and click on Distribute Content. Once the content is distributed to the DP, right click the Java app and click on Deploy. Choose the device collection for which you want the Java to be deployed. In this case I have deployed the Java app to a test collection and made it available in the Software Center. You can see in the below screenshot that the Java app is available for Install. Click on Install.

How to deploy Java using Configuration Manager

The Java app has been installed successfully.

[TS_VCSC_Info_Notice panel_type=”success” panel_icon=”ts-awesome-sun-o” panel_title=”Note” font_title_family=”Default:regular” font_content_family=”Default:regular” el_file1=””] The Uninstall option also works fine. If you want to uninstall the Java app, just click on Uninstall. This option is tested and it works fine.[/TS_VCSC_Info_Notice]

 

How to deploy Java using Configuration Manager

If the app fails to install, open the AppEnforce.log file and look for errors. In the below screenshot you can see the command line that we used to install Java worked perfectly fine.

How to deploy Java using Configuration Manager

  • Jonathan

    Have you tried deploying 32-bit Java to a 64-bit machine? I believe its broken.

    • Hey i will give a try tomorrow on my lab setup.

    • @Jonathan – Deployed 32 bit java to 64 bit machine successfully. I believe it works fine.

  • Karol Starukiewicz

    Why did you remove my comment about parameters?

    • Which comment ?. I will check if it has marked as Spam.

  • Hi Karol, I have not removed the comment. I never do that, I checked the spam and the comment was not there in the spam. I am still wondering where did your old comment go.

  • Check this – http://wpkg.org/Java

  • A. Jones

    Have you tried this with update 77 & 91 at all? This method of deployment used to work, but with the last 2 releases when you grab the MSI it seems to be corrupted and will not execute. I have tested it from several machines. Wondering if anyone else is experiencing this issue?

  • Michael Yuen

    the msi file does not run… I think it happens to the latest version of java, which they are trying to charge for msi files download.

  • Meru Otonashi

    There is definitely something wrong with Java’s installers.
    We’re currently using Oracle’s Java Enterprise MSI files, trying to deploy Java 8 Update 102.

    Using a vbscript I developed that will elevate with UAC when needed, it runs perfect with an account with administrative privileges.

    I’ve given this package to my VDI administrator that tries to inject it in with an admin account, the installation fails.

    I try to push out the package via SCCM, it gives me error 1603 (and further investigation in the MSI log file, it gives an error 1722 when the MSI reaches Oracle’s custome action to run “installer.exe” with parameters).

    Making matters worse, this enterprise MSI file fails when you simple double-click on it and try to install with an admin account. It will only install fine when you instantiate an elevated command prompt and run with a silent install with /q. In GUI mode, it simply fails too.

    My hinch is that although the MSI is being run as administrator, Oracle somehow screwed up their custom action and runs it with a non elevated access, which causes it to crash.

    Just follow the sequence well, you will see that the MSI will install Java Installer files to “C:Program Files (x86)Javajre*yourversionhere*” and the installer.exe is the real application that will install Java on the workstation.

    Here’s the exact MSI log about where it crashes:
    MSI (s) (E0:54) [16:55:21:246]: Product: Java 8 Update 102 — Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action installexe, location: C:Program Files (x86)Javajre1.8.0_102installer.exe, command: /s INSTALLDIR=”C:Program Files (x86)Javajre1.8.0_102\” WEB_JAVA_SECURITY_LEVEL=H STATIC=0 WEB_ANALYTICS=0 EULA=0 NOSTARTMENU=1 INSTALL_SILENT=1 AUTO_UPDATE=0 REPAIRMODE=1 ProductCode={26A24AE4-039D-4CA4-87B4-2F32180102F0}