Jump to content

Recommended Posts

Posted

Hi

 

Can anyone point me in the right direction to deploy java for i.e. 11. We have manually installed java and tested it. It seems to work ok for us however when the students logon, java seems to be disabled?

 

Thanks in advance

Posted (edited)

This is the line I use when installing JRE; although I have to say, I'm desperately trying to do without it if possible - total nightmare at times

 

msiexec /i jre1.8.0_72.msi AUTO_UPDATE=0 JU=0 JAVAUPDATE=0 EULA=0 NOSTARTMENU=1 SPONSORS=0 WEB_ANALYTICS=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H /q /norestart

 

edit: I disable the self-updating features because they are just an annoyance. I deploy the latest version as soon as it arrives.

 

edit2: I believe that these files are linked with the browser plugins - you could check they exist..

 

   "%ProgramFiles%\Java\jre1.8.0_72\bin\dtplugin\deployJava1.dll"
   "%ProgramFiles%\Java\jre1.8.0_72\bin\dtplugin\npdeployJava1.dll"

Edited by mrwoberts
Posted
You can use a MST instead of a long command line. In ie 10/11 if enhanced protected mode is enabled plugins are disabled unless the domain is in trusted sites.
Posted
Supposedly, deploying the MSI (if obtained via app data) is not actually supported by Oracle. They say use a command line such as "javaexename.exe /s".
Posted
I have had issues with pushing the MSI out through GPO, to get it successfully installed and working I deployed it via vbs script. Seems to work much better. I also deployed the javasettings.cfg file as it helped with the installation if the file was not present.
Posted

My notes:

 

How do I deploy Java using Active Directory across a network?

 

Download offline exe from: MAKE SURE YOU CHOOSE THE 32bit version.

 

 

JAVA 8:

 

Java SE Runtime Environment 8 - Downloads

 

 

Extract the .msi file from the installer

Follow these steps to extract the .msi file from the installer for deployment through Active Directory based network:

1. Download and launch in GUI mode the Windows Offline Installation executable (.exe) file.

(GUI mode is active by default unless silent mode option '/s' is specified)

2. When Welcome to Java window appears do not click Install button and navigate to LocalAppData folder (the user Application Data folder). The location of the LocalAppData folder differs for each Windows platform.

 

Note: You can also navigate directly to APPData folder by typing : %APPDATA% in Windows Explorer Address Bar or Run.

○ Windows Vista and Windows 7

C:\Users\\AppData\LocalLow\Oracle\Java\jre

○ Windows XP

C:\Documents and Settings\\Local Settings\ApplicationData\Sun\Java\jre

○ Windows 2000

C:\Documents and Settings\\ApplicationData\Sun\Java\jre

jre folder contains two files:

Data1.cab and

jre.msi

Example: For jre 6u43, jre is 1.6.0_43 so Sun\Java folder contains

jre1.6.0_43\Data1.cab and

jre1.6.0_43\jre1.6.0_43.msi

3. Copy *.msi and *.cab files to your temp location.

4. Click Cancel button in Welcome to Java window. There is no need to continue installation after msi and cab files got extracted.

From your temp location, you can use Active Directory to distribute the Java msi and cab files to as many client Windows platforms as you want.

Things to note during deploy process:

1. Cab file just needs to be in the same directory as msi file. For example to run msi installation for jre 6u43 with msiexec.exe tool, admin user just needs to specify a location of msi file:

msiexec.exe /i c:\msi_temp_dir\jre1.6.0_43.msi and Cab file needs to be in the same directory.

2. For jre older than 6u10 Sun\Java\jre\jre folder contains msi file only. cab file is packed inside msi file.

3. For jre older than 6u34 build 03 msi and cab files don't get deleted from ApplicationData\Sun\Java after completed installation so there is no need to extract msi and cab files when Welcome to Java window waits for user input.

 

 

 

 

&

 

Extracting an .msi File for Active Directory Distribution

Posted
are you using GPO to uninstall the older version of java, as ive not got it to work properly when doing an upgrade as it just leaves the older version behind.

 

If you deployed say Java 8 Update 60 via MSI, you can then remove it accordingly by adapting the same GPO, then deploy the latest Java 8 Update 72 for example.

 

If you didn't deploy the original/existing version, then it will just stay there. Unfortunately the Java installer only removes older versions when installed manually.

Posted (edited)
Download offline exe from: MAKE SURE YOU CHOOSE THE 32-bit version.

If you use a 64-bit browser (Firefox or IE w/ EPM) you'll need the 64-bit Java.

 

1. Cab file just needs to be in the same directory as msi file.

There isn't a .cab file now. Just the MSI.

Edited by Arthur
  • Thanks 1
Posted (edited)

I use the exe from MDT deployment with the following:

 

"{directory structure}\jre-8u73-windows-i586.exe" INSTALL_SILENT=1 STATIC=1 AUTO_UPDATE=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H WEB_ANALYTICS=0 EULA=0 REBOOT=0 NOSTARTMENU=1 SPONSORS=1

 

"{directory structure}\jre-8u73-windows-x64.exe" INSTALL_SILENT=1 STATIC=1 AUTO_UPDATE=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H WEB_ANALYTICS=0 EULA=0 REBOOT=0 NOSTARTMENU=1 SPONSORS=1

Edited by Sephiroth
Posted
are you using GPO to uninstall the older version of java, as ive not got it to work properly when doing an upgrade as it just leaves the older version behind.

 

We deploy Java via SCCM by running an uninstall command (for all old Java versions) first then run the latest version (I'm sure instructions were taken from a thread on here) I've had this issue and I think it is down to the files being locked when running the uninstaller. It was set to install if a user is logged on or not, but I've changed the install to only when no user is logged on and am currently seeing how that goes. The problem I can see is that not all machines are left logged on long enough for the deployment to start.

Posted
If you deployed say Java 8 Update 60 via MSI, you can then remove it accordingly by adapting the same GPO, then deploy the latest Java 8 Update 72 for example.

 

If you didn't deploy the original/existing version, then it will just stay there. Unfortunately the Java installer only removes older versions when installed manually.

 

yeah, hence i use psexec to call the old MSI and uninstall before rolling out the new version, should really stop that and use GPO to do it when required.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...