Software Deployment

As with any MSI issue, you need to verbosely log the installation. Without that, you're reaching in the dark. Once you have a log, search for the text "Return value 3." The dozen or so lines around that entry will tell you what's gone wrong.

Now luckily, I've just dealt with U77 and I'll guarantee that you haven't changed the 'Type' entry for the CustomAction which runs the installer - remember that Oracle is still brain-dead as far as MSI is concerned and just uses it as a mechanism to deploy then run their own installer!

So, find this row in the CustomAction table:

installexe 0x0412 installerexe [CMDLINE] 

You need to change the value in the 'Type' value to read '0x0C12'. What that does is tell the installer to run the CA without impersonation. Do this in the same transform that you'll be using to copy in the 'java.settings.cfg', 'deployment.config' and 'deployment.properties' files. You are doing that, too, right?

Hi,

Thank you for the respons. For now it doesn't seems to work with the info.

I added the following code the the above script:

/L*v C:\Dell_Kace_Logs\Java\jre8u40.log

What i did in following steps:

1. Unpack the .exe to get an MSI
2. Copy the code from the above schript and named it "Instal_Web.bat"
3. Put these 2 files in a folder, zipped them under the name "Java.zip"
   
4. Made an installer in the case K1000 and uploaded the zip file
5. Under the MI is set that it needs to run the "Install_Web.bat" file

I can't help you with the KBox stuff - I don't use one - but isn't this line in the log obvious?

MSI (s) (AC:08) [10:45:18:710]: Product: Java 8 Update 77 -- Error: Need Administrative privileges to proceed

>Did i forget some basics to install Java?
If you want the default installation, then no, you have it done. However, if you want to avoid your users calling the Helpdesk as soon as JRE tries to update itself (which of course it can't because your users don't have admin privileges - they don't, right?) and/or goes out-of-date, then you need to turn that junk off.

The use of the files I mentioned are documented here at IT Ninja and elsewhere as nauseum so Google away and use the information you find to create a transform to use with the MSI.

>So to be sure i reinstalled everything and manually deleted the java.settings.cfg file
>and ran the Kace setup again but now it failed.

>

>This means that the file needs to be there in order to let the MSI install properly

Do this in the same transform that you'll be using to copy in the 'java.settings.cfg', 'deployment.config' and 'deployment.properties' files. You are doing that, too, right?

I didn't do any of these things, all the information I found was to take the MSI, made a script, upload, run and Java is installed. Did I forget some basics to install Java?

I did read your post but it was not direct enough for me to make something out of it. It makes sense now when I saw that the java.settings.cgf need to exist. Also, I mentioned it above the above my screenshots.

You mention 2 other files 'deployment.config' and 'deployment.properties' but I can't find info of these files. Do they also need to exist or are these optional? If required where do they need to be and what do they do or what info do they need to contain?

Just *once*, I'm not going to post a LMGTFY link because I'm feeling generous but, as I mentioned, these files and their use is documented here at IT Ninja and elsewhere ad nauseum so do avail yourself of the tools available to you.

Oracle's documentation is here. I recommend using the system-level usage, as copying to each user's profile will introduce to a whole new world of Windows Installer pain which, it seems to me, you really don't need to get into now.

>it just doesn't work
Have you got a more vague description of the problem? This one is too detailed.

>jre-8u66-windows-i586.exe /s INSTALL...
Here you go, going back to using the EXE and not the MSI/MST so that's me done.