

With Java 8, though, I had to jump through a lot of hoops to get to the MSI file, and when I tried installing that, I received an error that there was a problem with the installer package. A lot of people online will also suggest trying to extract the EXE file. In the past, I’ve typically tried to extract these files to get access to the underlying MSI file - MSI files play very nicely with SCCM, as well as with PSADT.

The file we downloaded, jre-8u101-windows-i586.exe, is a setup.exe file.

That looks much more likely to include the files we need. The online install checks in at 550KB, and the offline install reads 47.8MB (for the 32-bit version). Instead of downloading from the big friendly red button, look to the bottom of this page for the link that reads “See all Java downloads.” This will provide options to download either an online or offline install. Stub installers like this are typically designed to be friendly to home users installing products themselves, but they tend to be difficult to automate. This downloads a small “stub” installer (in my case, it was about 550KB), and running this installer downloads the real setup files to a temporary location. When installing Java yourself, you’re typically redirected to a generic download page. This part will be pretty unique to each program - some installations take a lot of effort to automate, while others are pretty simple. The first thing we’ll need to do is get the install files and identify the command-line options for installation. The latest version as of this post is Java 8 update 101. We’re going to use a more elaborate example in this case: Java 8.
+–+February+2006.jpg)
Most software applications require quite a few more hoops to install and uninstall interactively than Firefox, and I’ve dealt with several that have made me want to pull my hair out in the past.įortunately, this is what PSADT was designed for! Using a toolkit like this allows us to abstract the steps for installing and configuring software. In my previous post, we went over the basics of the PowerShell Application Deployment Toolkit (PSADT) and built a working software package for Mozilla Firefox, including both an unattended install and uninstall.Īfter working with software packages, though, you’ll quickly discover that very few of them are quite this cut and dry. I’ve taken a new position at a new company, and I no longer have access to an SCCM environment…but I’m still using PSADT to create software packages! 08/18/16 on PowerShell, PSADT Table of ContentsĪfter a bit of a hiatus, I’m back and ready to write the long-anticipated follow-up to Part 1 of this N-part series.
