I assumed I would share the final solution. One interesting matter I found that I needed to share is which you can suppress the auto-reboot of install and it returns an exit code of 3010.
In case you are using the cost-free mode of PDQ Deploy, or If you're applying Professional mode but don't have a subscription to your package library, you may even now develop a Java installation. Just follow these steps.
I am able to’t obtain the x86 EXE or maybe the x64 MSI to install silently in any way. They’ve truly screwed up this Variation.
Having said that, you shouldn’t use msiexec for this install at all, since Java comes with its individual executable installer…
Also, as I commented within your previous pretty identical post, are you able to explain why you need to use msiexec in lieu of java's personal exe setup?
The JavaCache folder is blank. The Security folder will consist of the file exceptions.web-sites that is a summary of web sites you need to add to the exceptions list that you see under the java applet, security tab.
increase a remark
I actually also tried using with building the cfg file, but no luck with that system. It's possible just about every offline installer download includes a random element on ways to get it working
Since we nonetheless run XP and IE7, we also had to reinstall Java Digital device on about his all of our workstations which we A part of our script and also the copying in the Oracle Jinitator JVM.dll files.
Another option is to try notepad :Zone.Identifier, this will tell you about the stream containing this value.
WScript.Echo "/removeonly" & vbTab & vbTab & "Script removes only versions specified." & vbCrLf & vbTab & vbTab & vbTab & "If no versions are specified no versions are removed." & vbCrLf
while in the RemoveJava perform. If that directory isn't going to exist you'll see the 1622 errors with MSI packages. That error implies MSIEXEC couldn't publish towards the logfile. You could modify the script to develop/check for that directory but I come across It is really much easier to run the script from a batch file and use "MD %SYSTEMDRIVE%logs" at the very best from the batch file to build the desired logging directory.
This may develop a long-lasting setting variable, not merely a session a single. See the next For additional aspects:
In the event you seem in the application log I think, you’ll see it reference Every MSI becoming termed for all programs in win32_product.