New KACE user, trying to figure things out, so thank you in advance for your patience.  :)

I'm trying to distribute Java 7 Update 7 (32-bit) to a test machine.  I have the executable (jre-7u7-windows-i586.exe) uploaded to the box, and have the following options set:

 

Installation command - configure manually

command line parameters - /s /promptrestart AUTOUPDATECHECK=0 JAVAUPDATE=0 IEXPLORER=1 MOZILLA=1 

Don't Prepend msiexec.exe - selected

 

The package is pushed to the client, but does not install.   However, if I run the executable + paramanters from a command prompt, it installs just fine.

Thank you for your help...

 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1

Did you try "Run As" with Admin credentials??? 

Answered 10/17/2012 by: ronfalkoff
Third Degree Blue Belt

  • Thanks for the quick response.

    I did not find an option within "Managed Software Installation" that allows me to specify credentials. Where would I designate this?
  • I believe that's a Scripts option - not what I'd personally recommend for pushing applications since the tracking is *much* better with Managed Installs.

    John
  • runas /env/user:(username)
  • I used this on the K2000 to deploy in a scripted install this past summer not sure if variables changed since but I would give this a shot. jre-7u5-windows-x64.exe /s /v"IEXPLORER=1 MOZILLA=1 JAVAUPDATE=0 AgreeToLicense=1 EULA=1 /QN"
Please log in to comment
1

Here's my setup and notes for Java 7 Update 7 (worked with previous versions), which I've used since 6 Update 31 (with a couple changes, obviously).  I personally didn't have a lot of luck pushing the EXE.

Hope that helps!

John

___________________

MSI Note (copied from another website?) - main point here is how to get the MSI and CAB files:

JRE Deployment with Active Directory

This procedure describes how to obtain the .msi file necessary to deploy the Java Runtime Environment (JRE) across a Windows 2000/Windows XP Active Directory-based network. It works for version 1.4.2 and later of the JRE installers. Sun includes an .msi (Microsoft Installer) file bundled up in the JRE Windows Offline installers. The .msi file extracted below can be assigned to an Active Directory software distribution policy.

    Download and launch the Sun JRE Windows Offline Installion executable (.exe) file.
    Retrieve the ".msi" file from the LocalAppData folder (the user's Application Data folder). The LocalAppData folder will differ for each Windows platform.

Win7 - C:\Users\username\Appdata\LocalLow\Sun\Java\%version%

    Inside this folder you will find a folder named:

           {3248F0A6-6813-11D6-A77b-00B0D0150000}

    The first 2 digits are "71" for version 1.4.2_xx, and "32" for 1.5.0_xx. The last 6 digits of this CLSID and the name of the .msi file correspond to the release number. A CLSID ending with "150000" means version 1.5.0_00, and "142010" means verision 1.4.2_01
    From there, you can use Active Directory to distribute this .msi file to as many client Windows platforms as you want.
    If you want to register the JRE as the default VM of Internet Explorer and Mozilla, you will have to create a transform that will set the variables IEXPLORER and MOZILLA to 1 in the Property.idt table. You can find instructions on how to generate and use transforms at the Microsoft MSDN site.
___________________

The batch file (java7u7.bat) that I use to kill all Java-related tasks, uninstall the previous version (in this case Java 7 Update 6, I believe), kill the tasks again (in case a user opens a browser, etc) and install via the MSI:

taskkill /F /IM iexplorer.exe
taskkill /F /IM iexplore.exe
taskkill /F /IM firefox.exe
taskkill /F /IM chrome.exe
taskkill /F /IM javaw.exe
taskkill /F /IM jqs.exe
taskkill /F /IM jusched.exe
msiexec.exe /x {26A24AE4-039D-4CA4-87B4-2F83217005FF} /qn
taskkill /F /IM iexplorer.exe
taskkill /F /IM iexplore.exe
taskkill /F /IM firefox.exe
taskkill /F /IM chrome.exe
taskkill /F /IM javaw.exe
taskkill /F /IM jqs.exe
taskkill /F /IM jusched.exe
msiexec.exe /i jre1.7.0_07.msi /qn
exit

___________________

I then zip up the MSI (jre1.7.0_07.msi), CAB (Data1.cab) and BAT (java7u7.bat) files and setup the MI like this:

Installation Command:

* Configure manually

java7u7.bat

* Delete Downloaded Files

Managed Action:

* Execute anytime (next available)

Limit Deployment To Labels:

* client (this is a label unique to my environment, use whatever you need here)

Answered 10/17/2012 by: jverbosk
Red Belt

Please log in to comment
0

Java is famous for not finishing its installation until you reboot. In other words, the installation actually happens after the next reboot, not when you run the install.

We use the same .EXE that you have, and a similar command line. But we don't look for Java to actually be installed until the computer reboots.

Answered 10/21/2012 by: snissen
Fourth Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share