(imported topic written by SystemAdmin)
Gentlemen,
I’ve been banging my head against this one for a while. We’re doing test runs deploying JRE6 update 24 to machines that already have JRE6 installed. I modified/simplified relevancy a little bit so x64 systems that have x38 versions of JRE6 are also included. Here’s the relevance:
((
if (name of operating system starts with
"Win") then platform id of operating system != 3
else
false) AND (name of operating system as lowercase starts with
"win")) AND NOT exists key whose (value
"DisplayVersion" of it as string >=
"6.0.240" AND (value
"DisplayName" of it as string starts with
"Java")) of key
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall" of registry AND (language of version block of file
"kernel32.dll" of system folder contains
"English") AND (name of operating system !=
"WinNT") AND (exists file
"msiexec.exe" whose (version of it >=
"3.0") of system folder)
Action has also been modified to run via RunAsCurrentUser to minimize Win7 and UAC issues, here’s the code:
download http:
//malbf1:443/Uploads/5ca415033154492071ff01c97ffcffb17d6abc90/RunAsCurrentUser-2031exe.tmp
continue
if
{(size of it = 149903 AND sha1 of it =
"5ca415033154492071ff01c97ffcffb17d6abc90") of file
"RunAsCurrentUser-2031exe.tmp" of folder
"__Download"
} extract RunAsCurrentUser-2031exe.tmp download http:
//malbf1:443/Uploads/35fed33b1f00085a567a916dd326e72e401179ec/jre-6u24-windows-i586-sexe.tmp
continue
if
{(size of it = 14808868 AND sha1 of it =
"35fed33b1f00085a567a916dd326e72e401179ec") of file
"jre-6u24-windows-i586-sexe.tmp" of folder
"__Download"
} extract jre-6u24-windows-i586-sexe.tmp
// Note: update .exe will restart service automatically
if
{exists running service
"JavaQuickStarterService"
} delete __appendfile delete stop_javaquickstarter.bat appendfile net stop JavaQuickStarterService move __appendfile stop_javaquickstarter.bat waithidden stop_javaquickstarter.bat endif waithidden __Download\RunAsCurrentUser-2.0.3.1.exe --w --q cmd.exe /c __Download\jre-6u24-windows-i586-s.exe /s ADDLOCAL=ALL IEXPLORE=1 MOZILLA=1 SYSTRAY=0 REBOOT=REALLYSUPRESS JAVAUPDATE=0 /L C:\sct_util\jre6u24_install.log action may require restart
"35fed33b1f00085a567a916dd326e72e401179ec"
In about 60% of all of our test runs this action fails. Every step of the action completes but overall action will fail for no apparent reason. (See attachment for a screenshot.)
Re-running the same action on the machine that failed will often result in success, but sometimes will not. More interestingly, installation is designed to log its progress; when it fails, log is not created so it looks as almost the “waithidden” part is not running properly for some reason.
I have the following questions:
- has anyone come across the same issues with deploying Java?
- do you need to terminate active browser(s) and all Java processes (e.g. java.exe, javaws.exe, etc.) that may be in memory prior to running the install?
- is there a way to add some kind of verbose logging to the fixlet running on the client, to see how it’s working and where it’s failing?
Thanks in advance!
Dimitri