Deploying 32-bit Java silently to both 32-bit and 64-bit Windows via MI

This works as of Java 7 update 21. I've been using this method since early versions of Java 7. 

--Edit-- I found that a small percentage of users were having issues with Java appearing to  be missing in Firefox and Chrome. I have found the culprit to be Java FX 2.1.1. It is necessary to remove Java FX 2.1.1 to get Firefox and Chrome to work for these users, but it can be done before or even after Java 7 update 11 is installed. Using the Un-Install Wizard under Scripting > Configuration Policy and keeping everything on default worked flawlessly for me. ----

When I first started playing around with Java deployments using managed installations, I came across the issue of getting 32-bit Java deployed to 64-bit machines. I found a few workarounds, but they required scripts or too much manual work. I wanted the convenience of a managed install. This is what works for me. 

  • Download the Java x86 offline install.
  • Start the installation.
  • Browse to folder: C:\Users\currentuser\AppData\LocalLow\Sun\Java\jre1.x.0.xx
  • Zip together the following files: jre1.x.0_xx.msi and Data1.cab
  • Create a new managed installation. 
  • Upload the zipped file.
  • Set the installation command to configure manually and use this string: msiexec /i "jre1.7.0_21.msi" /qn AUTOUPDATECHECK=0 IEXPLORER=1 JAVAUPDATE=0 JU=0 MOZILLA=1

Note: The string above installs silently, turns off auto update and update notifications, and registers java with all browsers.Also, since new versions of Java come out more frequently than I update this post, make sure the installation command matches the version of Java you are using.

  • Check the box for "Don't Prepend msiexec.exe".

That's it! Happy deploying!

Pro tip: We use the "Execute after logon (before desktop loads)" managed action to prevent the install from corrupting due to Java being in use on the target machine when it is pushed out. If you want to execute immediately, you can zip up a .bat file with the msi and cab files and then replace the installation command with "filename.bat" (still have it set to configure manually). In the .bat file, you should have:

taskkill /f /im java.exe

taskkill /f /im jusched.exe

taskkill /f /im jp2launcher.exe

msiexec /i "jre1.7.0_21.msi" /qn AUTOUPDATECHECK=0 IEXPLORER=1 JAVAUPDATE=0 JU=0 MOZILLA=1


  • Ashlea,
    Great post and thank you for sharing. - KACE_Mary 11 years ago
  • Ashlea,
    UAC seems to block/break the silent install? How would one get around that? Can you "run as Administrator? - Kace_jar08 11 years ago
  • we are seeing this issue with IE-can it be applied there too? - dkurz8814 11 years ago
  • If you are testing the install on a local machine, you will need to run command prompt as an administrator to be able to run the install command. However, managed installs should always be run as "SYSTEM" user, which has admin rights, so you shouldn't run into any problems with UAC. We have UAC enabled in our environment and don't have any problems with it interfering with our managed installs. - ashlea 11 years ago
  • I have not attempted to install IE through a managed install. We use the patching part of the K1000 to install/update IE. - ashlea 11 years ago
  • This is great. I hope it actually solves the java update so that users do not get prompted when a new version comes out. Using these steps it solved an issue for me where our laptops are on a Radius Authenticated Network so it was hard to get Java installed on the computers because they were not visible to the KACE on the network until after the user logged in and authenticated.

    Much Thanks for this.

    Also on a side note what does the checkbox "Don't Prepend msiexec.exe". do? Forgive my ignorance but I am not certain on the difference is if you prepend msiexec or if you do not. - bwilkerson 11 years ago
  • When the box for "don't prepend msiexec.exe" is checked, it will add msiexec.exe to the front of what you put in the "installation command" box. Since I already include msiexec.exe /i as part of my installation command, I don't want it there a second time or it won't work. I found that when I am configuring the installation command manually, I like to put the full command in there and check that box because it's easier for other people to look at and understand what is happening.

    I have not had any reports of users receiving the java update prompt anymore after I started doing the updates this way. However, since the browsers we use now block out-of-date java plugins from running unless you specifically tell it to allow, as soon as a new update comes out, the users are complaining about it. The now know that when a new update comes out, I'll have it ready, but they need to log off and back on to receive the update or they'll keep getting the blocked message.

    Our environment relies heavily on Java since the product we sell (web/audio conferencing) requires Java to be the host of a web conference. The majority of our users need Java every day. Other environments might not be impacted as much as we are when a new version comes out. - ashlea 11 years ago
  • Ashlea, Thank you for posting this I was running into the same issue on my 64 bit systems. Your solution works great. - BigRed2012 10 years ago
  • It took me some time to figure out why this was not working for me. I used the "default" installation and therefor I could not select "Don't prepend msiexec.exe". Thanks for this guide, it really helped deploying Java 7 update 67! - Cavemen 9 years ago
  • Thanks for the article, solved jre deploy probs - anonymous_102124 9 years ago
  • Hi All,

    Im trying to install two different McAfee packages but both are same version with different configuration, one frame pkg for Region1 and another for Region 2, how i can do this MI ?

    when I create new managed install im able to associate only one file at a time, any idea how can i perform this ? as i need to perform the two installation with different configuration at a time..I have zipped both the frame pkgs, and trying to call as below

    Managed Install 1:

    Override Default Installation
    Full Command Line:

    Managed Install 2:
    Override Default Installation
    Full Command Line:

    would this work? - rahimpal 7 years ago
This post is locked

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ