Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

Problem with Java 1.8 update 31 deployment

$
0
0

It seems like I have to re-invent my SCCM Java deployment process each and every time Oracle comes out with a new update. I am currently attempting to deploy Java 1.8 update 31 and am having little luck. While this is an SCCM-centric question I am still in the testing process prior to actually deploying the software. I getting an installation error as follows with the 32-bit installation:

MSI (s) (50:CC) [11:52:09:663]: Product: Java 8 Update 31 -- 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:\Windows\Installer\MSI79FF.tmp, command: /s INSTALLDIR="C:\Program Files (x86)\Java\jre1.8.0_31\\" WEB_JAVA=1 REPAIRMODE=0

The installer creates the installation directory and copies the files but the installation ultimately fails with the generic 1603 error.

The command line that I am using to install Java is being passed through Powershell Deployment Toolkit as:

Execute-MSI-Actioninstall-Path"jre1.8.0_31.msi"-Parameters"JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q"

Which I tested manually as:

msiexec.exe /I "jre1.8.0_31.msi" JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q

When manually run the install completes just fine without complaint so I know the switches are correct and are fully functional. I have even run the actual .com installer using just the "/s SPONSORS=0" arguments and that works just fine too when run manually.

I have never had an issue where a command line that works when run manually under and admin context won't work when run through Powershell. I read through the related thread at: http://www.edugeek.net/forums/enterprise-software/143767-java-8-update-25-silent-install-via-sccm-8.html however it doesn't seem to come to a definitive conclusion as to what could be done. I am not using config files as I have never had the need to before (passing the switches always worked until now). I am also able to completely uninstall all previous versions of Java using the Remove-MSIApplications PDT commandlet (which also works fine if I manually install 1.8 u 31 before running the PDT process again).

I am just getting fed up with the mess that is Java. It would be nice if there was simply some consistency and predictability within these version. If anyone can provide insight I would really appreciate it.

V/r,

Chris


Viewing all articles
Browse latest Browse all 4762

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>