Systems Management Question

Extracting/Installing msi package through managed installations only seems to work for the computer that I extracted from.

10/30/2014 9495 views
So I'm trying to update Java to latest version (8u25) and I seem to be failing horribly at using the managed installation via KACE Management Appliance K1000.
Here is the gooey bits:
Part 1
Pulled down offline installer for Windows 32-bit
Started install
Navigated to C:\Users\Obligatory_Blank_Account\AppData\LocalLow\Sun\Java\jre1.8.0_25 and copied the msi file: jre1.8.0_25.msi
Placed on my desktop

Part 2
Added new software under Inventory, fields as follows:
        Name:     Java 8 Update 25
        Version:  8.25
        Pub:       Oracle
Chose the correct OS types it would be distributing to.
Uploaded and Associated the msi file and hit Save

Part 3
Created new Managed Installation in Distribution
Configure as follows:
        Name: Java Install (8u25) x86
        Execution: Anytime (for test bed purposes, this will be switched to When User is Logged Off)
        Only display records with an associated file: Checked
        Alt Location: Unchecked
        Default Location selected
        Additional Parameters: AUTO_UPDATE=0 EULA=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=M /qn /i (for some reason it keeps throwing the switches on the end... not sure why it's doing that. This could be the problem area.)
Deploy as follows:
Test Bed Label (3 pc's, including my own)
Notify as follows:
        Alert User before run: Checked
        Default Message: The Administrator would like to install software update on your PC.
        Timeout: 5 minutes
        Action: Install Now
Schedule as follows:
        Order: 10
        Max Attempts: 3

So does anyone have any insight as to why the managed install keeps failing? Any and all help would be appreciated!


Jeff B.

3 Comments   [ + ] Show comments


  • To help out and possibly building a .mst, here is the deployment.properties file that AK was referring to: #deployment.properties
    #Fri Oct 24 15:10:52 EDT 2014
    deployment.browser.path=C\:\\Program Files (x86)\\Mozilla Firefox\\firefox.exe
    #Java Deployment jre's
    #Fri Oct 24 15:10:52 EDT 2014
    deployment.javaws.jre.0.path=C\:\\Program Files (x86)\\Java\\jre1.8.0_25\\bin\\javaw.exe
    deployment.javaws.jre.1.path=C\:\\Program Files (x86)\\Java\\jre7\\bin\\javaw.exe
  • Was able to solve the first part of a two-part problem.

    In short, KACE installs as local system (x64 for almost all the PC’s we have), and when KACE unpacks a 32-bit executable, it places the files in the x86 directory. However, the local system installer is x64, so inherently it looks in the 64-bit directory instead of x86, which results in and Error Code:1619, files not found. I have found and utilized a resolution for this, and tested successfully in my sandbox. It is listed below:

    1. Create the directory in the SYSWOW64 directory: Basically I have to place the folders there ahead of the install, this is done as a preliminary step. AFP (absolute file path): C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.8.0_25
    2. Create a directory junction in the System32 directory. This will point (create a link) to the 32-bit directory when the 64-bit installer looks for these files. The AFP where this junction is going is: C:\Windows\System32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.8.0_25
    3. The above command was done with the mklink /J command in an Administrative Command Prompt.
    • The next part is the creation of a batch file to automate the process of creating the file directory and the directory junction.
  • Ok, had to back up a little. It seems I also need to manually install a java.settings.cfg file in the directory C:\ProgramData\Oracle\Java. All that will be contained in the config file are the following variables: AUTO_UPDATE=0 EULA=1. Even if I add other variables, the file is modified back to this. At least i can now push 32-bit Java to either platform using KACE scripting. :) Moving forward towards a solution.

Community Chosen Answer

Is creating an .mst option for you, if so, then:

  • Pass the following switches to command line (Additional Parameters):
  • There is a property file (deployment.properties) located in the following location:
    • %UserProfile%\AppData\LocalLow\Sun\Java\Deployment
  • Add the following two properties to the file (deployment.properties):


  • Lastly, use active setup to pass this properties file across all users.

Answered 10/30/2014 by: 786_ak
Third Degree Green Belt

  • JREs are already MSIs (albeit as merely a container for the ZIP and Custom Actions) so deploying to that location via an MST is the best option.

    Also, putting 'deployment.properties' in %SystemRoot%\Sun\Java\Deployment negates the need to propogate it to all users.

All Answers

As EdT suggests, did you copy out a CAB file? For me the CAB file should be approx 24MB and the MSi itself is under 1MB. You should find both in that folder you posted.
Answered 10/31/2014 by: alphabeta
Black Belt

  • Hi alphabeta, Nope, there was only the msi package in that file. EdT did ask if it would work as standalone and it did not. The only place I found a cab file was in the AU folder, and it was titled AU.cab. I will look into the deploment.properties and deploying via MST as suggested below. I was able to get version 7.67 to deploy in the same method used above though, so I'm curious as to why it's changed. I have been scouring the net to glean any info I can about Java 8u25 and have found some interesting things (this version will NOT auto uninstall 7 or lower, since it is a different family) but nothing pointing to installation issues.
My memory triggered a recollection that I have previously downloaded the JDK and used the JRE installer from there. Don't have time right now to check this with the V25 release but if you are still trying to solve this one, it might be something you want to check yourself.
Answered 11/03/2014 by: EdT
Red Belt

  • Ok, thanks for the Heads Up, I will check it out.

Did you check whether the source folder you got the MSI from, contained any CAB files?  Have you tried to install the MSI manually on a test machine to check that it works?

If the parameters you are questioning are the /qn (silent install) and /I (install), they are a requirement. However this makes me ask the question - are you specifying the MSI as the executable, or are you calling msiexec.exe and passing the msi and all its parameters as the argument? 

What location are you calling msiexec.exe from?  Remember you will need the 32 bit version.

Answered 10/30/2014 by: EdT
Red Belt

  • Hi EdT, there were no CAB files for the MSI folder. The only CAB file I found was in a different folder and was the AU.cab for the AutoUpdater. I tried copy/pasting jre1.8.0_25.msi to another test computer and it did not work.

    As for the parameters i know they work, the are just being moved around by KACE in the Managed Installation section. Normally when I run CLI I have the setup as follows:

    msiexec.exe /i jre1.8.0_25 PARAMETERS /qn

    KACE has it as follows:
    (Default installation selected)
    Additional Parameters

    So I was just curious as to why it moves all the switches to the end of the string. To answer whether I am specifying the MSI as the executable or calling msiexec.exe and passing the msi and all it's parameters as the argument, i believe I am trying to do the latter. Not exactly sure what the difference between Default installation and Override Default Installation is when using Managed installation in KACE K1000.

    The location I'm calling to is the Software I created specifically for this Install. Refer to Part 2 of my question for clarification.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ