If you want to know how I deployed Java using ConfigMgr and PowerShell then you will want to read this post…

In my last podcast I spoke about a PowerShell script that I wrote that uninstalls all instances that it can find of msiexec installed applications. I called this script Invoke-ApplicationRemoval and you can find it in my Github repo here.

In the same podcast, I also opined the virtues of using PowerShell to deploy applications using Config Manager.

Today I wanted to remove all installed versions of Java and then install both the 32bit and 64bit versions of the latest Java version using ConfigMgr.

To do this, I used my Invoke-ApplicationRemoval script with extra added sauce to install both versions of Java as well. You can find the script here. It’s called JavaVersionManagement.ps1.

All you need to do is to create a new Application in ConfigMgr and choose to make it of type: Script Installer.
Then, for the Installation Program field in ConfigMgr use the following:

powershell.exe -executionpolicy bypass -file .\JavaVersionManagement.ps1

And season with whatever detection rule you wish to use. I normally use the Java.exe version number. In my case I detect both the 32 and 64 bit versions of Java.exe to signify a successful deployment:

Ensure that you place the .ps1 and your extracted msi java file(s) in the same directory where you normally store your ConfigMgr source files.

The only modification you need to make to the script is the name of the msi files on lines 101 and 102. If you are only installing one version of Java, simply comment one of those lines out.

Once that’s done, deploy to your computers and sit back as all current versions of Java are swiftly removed and your new version installed. (And how easy is this as a repeatable deployment when the next Java version comes out, eh? Suh-weet!)

I’m assuming a few things here:

  • You know how to extract the Java msi file from the downloaded offline exe installer.
  • You know how to create an Application of type Script Installer in ConfigMgr.
  • You know how to deploy an application.

If you need me to explain any of this in more detail, please let me know via comments below or twitter: @ozthe2


Get my book:

ConfigMgr - An Administrator’s Guide to Deploying Applications using PowerShell