We have a K1000 VM and 1 replication that was recently set up and we are trying to push Java 8.65 out to a few computers to test the replication share. Dell had sent us a JAVA white paper to follow to set up an uninstall, version check and an install of either the 32 or 64 bit java. When running the script the installation files are copied out to the computer - batch file + 32 & 64 bit MSI installers, but fail to run on the computers. The KACE server reports back that the installation was successful although the uninstall and the install failed to run.

Not sure if the install is supposed to take place immediately when the script is run or if it needs to be kicked off by another process or agent. The white paper references $(kace_sys_dir) - not sure if that needed to be changed to reflect the actual location of the installation files on the C drive. My other thoughts are that the script type might need to be changed to a different type. In any event I have tried rebooting the computers, forcing them to update, tried changing the script settings - tried and retried, waited several days and not had a successful installation. The files copy but don't install.

Any assistance that can be provided would be greatly appreciated,

Dana Ton

Dton@calance.com


Location on computer where files are being copied to:

C:\programdata\dell\kace\kbots_cache\packages\kbots\506


Per Dell KACE White Paper:

Online Script mode - Script enabled

Task 1 - Uninstall task

wmic product where "name like 'Java%%'" call uninstall /nointeractive

Task 2 - Check and Installation

Select Launch a Program…

a. Enter $(KACE_SYS_DIR) in the Directory: field

In the line above - Should the directory name be modified to match actual settings?

b. Enter msiexec.exe in the File: field

c. Enter /I /QN jre1.8.0_60_x86.msi JAVAUPDATE=0 JU=0 AUTOUPDATECHECK=0 SYSTRAY=0 EULA=0 in the Parameters: field

Note: File name was changed in the actual script above to match the file name.

d. Click Save Changes

Task 3 - Check and Installation

In Task 3 Under Verify, click Add

3) Select Verify a Registry Key Exists…

a. Enter HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node in the Key: field

b. Click Save Changes

4) In Task 3 Under On Success, click Add

5) Select Launch a Program…

a. Enter $(KACE_SYS_DIR) in the Directory: field

b. Enter msiexec.exe in the File: field

c. Enter /I /QN jre1.8.0_60_x64.msi JAVAUPDATE=0 JU=0 AUTOUPDATECHECK=0 SYSTRAY=0 EULA=0 in the File: field

Note: File name was changed in the actual script above to match the file name.

d. Click Save Changes

----------------------------------------------------------------------------------------------------------------------------------------------

KACE Console Logs

Log for Java Management Script on 62414-TESTLT1 [ Show All ]

Started:10/22/2015 18:04:45
Finished:10/22/2015 18:04:46
Elapsed Time:1 second
Status:2

Output Log

Running as: SYSTEM
Launched Process: kace1826.bat
Running as: SYSTEM
Launched Process: msiexec.exe
Running as: SYSTEM
Checking if registry key exists 'HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node' did not succeed: (2)

Activity Log

Launching program: 'C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\506\kace1826.bat' '' wait='false'
Launching program: 'C:\Windows\System32\msiexec.exe' '/I /QN jre1.8.0_65_32BIT.msi JAVAUPDATE=0 JU=0 AUTOUPDATECHECK=0 SYSTRAY=0 EULA=0' wait='false'
Checking if registry exists: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node



0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0
How odd that the test for installation success is a simple check that the Wow6432Node key exists!! It should at least check for the ProductCode in the 'Uninstall' branch.

I don't know much at all about Kace scripting so can't say why the test that it's doing fails, though. I strongly suspect that the 'wait' should be set to 'True'. I think with it 'False', the script exits as soon as it's kicked off the MSIEXEC process.

Next, the properties on the command line will disable automatic updates but will NOT stop the brain-dead "JRE is out of date" message. For that you need to deploy the two 'deployment.' files. There's plenty of detail on that here at IT Ninja so I won't repeat it.

I would also recommend that you use '%~dp0' in front of your MSI name.

Answered 10/23/2015 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity