I have run into a problem where I are unable to deploy Java 8 Update 25 via SCCM 2012.
I noticed that several other people have had similar problems lately, and thought I would post the problem here in the hopes that someone has a resolution.
I have built a package for deploying Java 8U25 in SCCM 2012, distributed the content, and assigned to a test group (as I have always done for the last few releases of Java). One interesting tidbit was that when I went to the %APPDATA% folder to extract the MSI and CAB files, the CAB file wasn't there anymore, as it was in previous versions.
Under the "Deployment Type" settings, I am using is the following MSI installer command:
msiexec /i "jre1.8.0_25.msi" TRANSFORMS="jre1.8.0_25_x86.mst" /qn /L*v C:\WINDOWS\CCM\LOGS\jre1.8.0_25_Install.log
Running the advertised program on the client machine will always fail. The interesting part is that if I open an elevated command prompt on the test machine (Right click, Run As Administrator, CD into the CCMCACHE\{Java 8U25} folder) and use the exact same command, it installs just fine.
My first thought was, "Well, something must be buggered with the account that System Center uses...." - however I am able to deploy Office, previous versions of Java, and Flash using System Center, so that tells me the configuration is correct for the user account. I have also confirmed that the System Center account is part of the Domain Admins AD group, so it should be able to do whatever it wants in regards to system changes.
One final head-scratcher that just makes it even more aggravating:
- Manually uninstall previous Java version (7U67)
- Manually install 8U25 as Administrator
- Manually uninstall 8U25
- Reinstall 7U67 via System Center
- Deploy 8U25 to machine
- 8U25 will now successfully install
There seems to be two conditions that will allow 8U25 to successfully deploy:
- You have to run the installation procedure as a LOCAL admin, not a DOMAIN admin OR
- Java 8U25 has to have been previously installed on the machine
What has changed in the deployment process/procedure that is causing this behavior? Is anyone else running into the same issues? What "remnants" are getting left behind by the manual 8U25 installation that allows future deployments to proceed normally?