Software Deployment

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

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)

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.