ninjaneer

I have our environment set up to push the MMS.CFG file at the end of the install. Funny thing is that it goes in two different places, based on 32/64 bit versions of Windows. My solution was to put it in both places, if they both existed. C:\Windows\System32\Macromed C:\Windows\SysWOW64\Macromed The only two lines I have in my files are: SilentAutoUpdateEnable=0 AutoUpdateDisable=1 I can flip the values and watch it change in the control panel applet.

Here's what is working in my environment so far: Short version: Creating the C:\ProgramData\Oracle\Java\java.settings.cfg before installing the MSI allows me to deploy Java 8 Update 25 via SCCM. Long version: - Extracted the MSI from the EXE installer from Java.com the way we have always done (There was no CAB file this time - don't panic!) - Using Arthur's jre1.8.0_25_x86.mst transform file and modifying the "Property" table to match the screenshot below. (You could generate your own transform as well - your choice.) - Using stomie's advice about the C:\ProgramData\Oracle\Java\java.settings.cfg file, I built a VBscript that does the following: --- Creates the C:\ProgramData\Oracle\Java\ folder if it's missing --- Backs up any existing java.settings.cfg file that it finds if the folder DOES exists (renames it based on a timestamp) --- Creates a new java.settings.cfg file in the folder with the settings show in screenshot 2. - Call the MSI installer with the following parameters: 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 Once the installation completed, I went to Java.com and Javatester.org to confirm that Java 8U25 was functional and so far it has worked 100% of the time. The only caveat to this is that I have only been able to test it on 8 systems so far. (Weekends are the busiest time for our company, so I'm limited in what maintenance I can do going into Saturday/Sunday) Then I built a .cmd file to wrap it all up nicely. Step 1: Uninstall old software (We use supersedence, but I also have a master list of old software versions GUIDs that I uninstall with a VBScript - this lets me target old versions of Flash, Java, etc. during every deployment. It's a little bit of overkill, but I don't want to get a phone call asking why 3 machines are still running outdated Flash...) Step 2: Create Java folder and generate the cfg file with the proper settings Step 3: Run the MSI installation When I initially configured the "Deployment Type" in System Center, I chose "MSI", then pointed it to the MSI that I extracted. This imported the information and saved me a few steps. Then I just modified the "Installation Program" on the "Programs" tab to call my Ju825.cmd file instead of the msiexec command. (Screenshot 3) Then I redistributed content, waited for it to finish, and now have it deployed to a device group that I created for testing purposes. So far, the MSI installation has worked on eight machines, and now I'm patiently waiting to test the new, all-inclusive package. [ATTACH=CONFIG]27268[/ATTACH] MST Settings, edited in Orca. [ATTACH=CONFIG]27269[/ATTACH] java.settings.cfg file generated by VBScript. [ATTACH=CONFIG]27270[/ATTACH] Calling custom install command file.

I just tested this on a machine that did not have Java 8 previously installed, and it worked as expected. Literally, the ONLY change I had to make was to create that folder and copy the java.settings.cfg file into it. I'll test it on a few more machines just to make sure - so far, you're 1 for 1 though!

Yes, the problem that some of us seem to be having is that it CAN be manually installed, but cannot be deployed through System Center. [EDIT] It can be deployed MANUALLY using the exact same command that System Center is using, which includes the "INSTALL_SILENT=1" option.

What is the path to this file? (I mean, I'll look for it on my successful machine...but if you wanna save me some time...*grin*)

As an extra note, I have noticed that if I manually install 8U25, then uninstall it and reinstall 7U67 to test the deployment package - it works fine. If 8U25 has never been installed on the machine, however, it fails. Digging through the log file now, thankful I don't have any hair left to pull out.

Yep. Just started seeing this on my first test machine of the day. Here are the steps I took - I should mention that most of our machines have 7U67 already installed, and I have supersedence set to "UNINSTALL" that version during the deployment: 1) Verify that target machine has 7U67: "Java 7 Update 67|{26A24AE4-039D-4CA4-87B4-2F03217067FF}" 2) Deploy Java 8U25 to device: OK 3) Launch install from Software Center: OK 4) Installation fails, "The software change returned error code 0x643(1603)." 5) Check MSI Installation Log: "MSI (s) (38:0C) [10:19:41:437]: Product: Java 8 Update 25 -- 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\MSI3525.tmp, command: /s INSTALLDIR="C:\Program Files (x86)\Java\jre1.8.0_25\\" WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H WEB_ANALYTICS=0 EULA=0 NOSTARTMENU=1 AUTO_UPDATE=0 SPONSORS=0 REPAIRMODE=0 " 6) Reboot machine: OK 7) Retry installation from Software Center: Failed, same errors 8) Check installed Java version: "Java 8 Update 25|{26A24AE4-039D-4CA4-87B4-2F83218025F0}" (So...it installed, but it didn't? 0_o) 9) Check Java version at Java.com and JavaTester.org: Tests fail 10) Disable anti-virus, retry installation: Install failed 11) Run command manually: Install failed. 12) Create alternate deployment without supersedence: OK 13) Install alternate deployment: Failed. (same errors) Still doing some research/testing, but that's what I have so far.

I've had a measure of success with at least one machine. I plan on dropping a few more into my test collection tomorrow to see if it's a repeatable success. If so, I will try to put together a How-To for SCCM 2012, if no one has one put together by then.

My two cents: I have been able to semi-automatically install update 25 on about 10 systems. I say "semi" because even though I specified the "SILENT" switch, I still had to click on "Yes" for the prompt "Do you want to allow this program to make changes on your computer?" This was while logged in as a restricted user, but launching the install script with my Domain Admin credentials. I've deployed several versions of Java via SCCM 2012 and never had this issue crop up. Like many others, it was a matter of finding the MSI, building the application, and letting it run.