If you want to see the manual process @rtrouton has a good blog post for a previous version, you can see if that info still applies: https://derflounder.wordpress.com/2015/10/20/oracles-java-8-update-65-the-return-of-the-java-install...
ok, I right clicked the .app and /contents/Resources and dragged the JavaAppletPlugin.pkg to desktop
@mvu I checked out the link @Josh.Smith provided, based on the information provided from reading that link, after java installs the JavaAppletPlugin.pkg via Casper Policy, the application will prompt for admin privileges before fully launching and a few other user needed input. Going to check this out.
hope this is not still happening.
@tcandela I think the portion of Rich's post you are referring to (about the elevation prompt) is for the .app...not the .pkg:
Now that the good news is covered, let’s talk about the install application. Oracle’s Java 8 Update 65 install application has the following behavior: This application will prompt for admin privileges before fully launching.
I packaged Java 8 Update 92 yesterday for a manual ARD deployment with everything dumped into an Iceberg package. It's not the casper way of doing it but there may be stuff in here that will be of use to you. I'll try to post the config files below.
sudo installer -dumplog -verbose -pkg "$1/Contents/Resources/JavaAppletPlugin.pkg" -target /
sudo mkdir -pv -m 755 "/Library/Application Support/Oracle/Java/Deployment"
sudo chown root:admin "/Library/Application Support/Oracle/Java/Deployment/"
sudo cp -R "$1/Contents/Resources/deployment.config" "/Library/Application Support/Oracle/Java/Deployment/"
sudo cp -R "$1/Contents/Resources/deployment.properties" "/Library/Application Support/Oracle/Java/Deployment/"
sudo cp -R "$1/Contents/Resources/exception.sites" "/Library/Application Support/Oracle/Java/Deployment/"
sudo chown root:admin "/Library/Application Support/Oracle/Java/Deployment/deployment.config"
sudo chown root:admin "/Library/Application Support/Oracle/Java/Deployment/deployment.properties"
sudo chown root:admin "/Library/Application Support/Oracle/Java/Deployment/exception.sites"
sudo chmod 755 "/Library/Application Support/Oracle/Java/Deployment/deployment.config"
sudo chmod 755 "/Library/Application Support/Oracle/Java/Deployment/deployment.properties"
sudo chmod 755 "/Library/Application Support/Oracle/Java/Deployment/exception.sites"
sudo defaults write /Library/Preferences/com.oracle.java.Java-Updater JavaAutoUpdateEnabled -bool false
sudo defaults write "/System/Library/User Template/English.lproj/Library/Application Support/JREInstaller/ThirdParty" SPONSORS -string "0"
The Deployment.Config File
I'm sorry about the formatting, the hashes in the files code are making the text in the post huge.
The Deployment.Properties File
Just a plain text file with a list of https addresses in it. Only needed if you want to control approved websites to run Rich Internet Applications (JAR files etc.) without them being blocked.
Orcale release 2 versions at the same time. Why? I don't know. O_o? Theres a "mandatory bug fix" version 91 and a "mandatory + extra bugs fixed" version 92. You can get both of them here:
Java 8 SE (Standard Edition)
This is where I usually get them instead of Java.com <- That site for the public.
@Taylor.Armstrong - I think so, but then again, I don't see any acknowledgement. Maybe we're using invisible fonts? :)
Just in case: .- ..- - --- .--. -.- --. .-.
Has anyone suggested AutoPKG yet? ;) Seriously, it is worth the price of admission just for Java and Flash updates. (that's a joke, since the "price" = "Free".
@maxvre One release is CPU, one is PSU. Some links below for reference.
"Which Java version should I choose: the CPU or the PSU?
Oracle strongly recommends that all Java SE users upgrade to the latest CPU release available for a release family. Most users should choose the CPU release.
Users should only use the corresponding PSU release if they are being impacted by one of the additional bugs fixed in that version as noted in the release notes."
The deployment.properties file above may be overkill for what you want to do but it lets me configure every setting in the advanced tab of the Java control panel.
Any setting you don't want locked, just put a hash in front of the "locked" line and it will be ignored.
Also note! in the postflight script the default write command for
"Disable Sponsor offers during install or updating of Java"
This setting isn't available in the deployment.properties file and has to be set by a default write command. Why? Bad programming on oracles part. I've seen people posting on the net variations of the setting that gets created in the users home directory deployment.properties file when you tick the box manually but none of them worked for me. Only this default write command ticked the box for me in the Java control panel. Tested it in a clean VM to make sure.
What I have posted gives you control over "every" setting in the Java 8 control panel and may be more than what some people need, if they just want a simple package deployment. Everyone has their own deployment method and preferred software.
I have been using Composer to build a deployable package. This has worked well for me, but often, when I run a test install via Self Service, I would end up with a bad installation of Java. I created a new package for 8u91 yesterday, and it seems to be working really well.