/build/static/layout/Breadcrumb_cap_w.png

Scripting Question


Why wont my Java 8 update 40 install run? *.Bat file issue

04/14/2015 3424 views

I've followed to the "T" how to create the custom install for Java on various posts here on ITNinja. I know it works, because if I manually run the *.bat file on my test PC everything works perfectly, just when I call it in my zip that I uploaded to the MI nothing happens. Inside my zip is two files - "jre1.8.0_40.msi" and "install.bat". I have the distribution to configure manually with the command line being "install.zip" <--tried with and without quotes though I know you don't need them. The bat file looks like this:

taskkill /f /im java.exe

taskkill /f /im jusched.exe

taskkill /f /im jp2launcher.exe

START /WAIT /MIN WMIC product where "Name LIKE '%%J2SE Runtime%%'" call uninstall /nointeractive

START /WAIT /MIN WMIC product where "Name LIKE '%%Java%%'" call uninstall /nointeractive

msiexec /i "jre1.8.0_40.msi" /qn AUTOUPDATECHECK=0 IEXPLORER=1 JAVAUPDATE=0 JU=0 MOZILLA=1

It kills all java processes, then uninstalls any previous version, then installs the java 8 update 40. Like I said, just manually running the file works, but calling it in KACE does not. I also tried checking the box "don't prepend msiexec", and tried with it unchecked. What am I doing wrong? Why is nothing happening. I'm on 6.3 by the way. Thanks in advance.

Answer Summary:
2 Comments   [ + ] Show comments

Comments

  • Does the script do anything? i.e. does it uninstall the old software but just not install the new one? Have you tried putting the full UNC path into the script to the MSI? e.g. "\\server\folder\jre1.8.0_40.msi".
  • http://docs.oracle.com/javase/1.5.0/docs/guide/deployment/deployment-guide/properties.html#properties

    You will find most of the options here.

Answer Chosen by the Author

0
still didn't work, so I used a script.
Answered 04/14/2015 by: mazostyle
Purple Belt

All Answers

0
>still didn't work, so I used a script.
...and the next time I encounter a problem, I won't bother to find out why it occurred. I'll just create a long and convoluted way to work around it.

The log will have contained the clue as to why your command line was failing.
Answered 04/16/2015 by: VBScab
Red Belt

  • thanks dad, lol. If you have nothing nice to say...leave.
This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
0
Add the logging argument to your command line: /L*V path_to_and_name_of_log_file.LOG.

In the resulting log, look for the text "return value 3". The half-dozen or so lines above that text will have the detail of what failed.
Answered 04/14/2015 by: VBScab
Red Belt

  • what would be an example for the path_to_and_name_of_log_file.LOG
0
Seriously?!?!?

Try "%SystemRoot%\TEMP\JRE 1.8.0_40.LOG".

%SystemRoot% resolves to C:\Windows in most installations.
Answered 04/14/2015 by: VBScab
Red Belt

This content is currently hidden from public view.
Reason: Removed by member request For more information, visit our FAQ's.
0
I created an mst with all the properties you mentioned above inside it.  It worked out for me, I used SCCM for push.

Hopefully, this will be helpful.

Thanks.
AK
Answered 04/14/2015 by: 786_ak
Third Degree Green Belt