Dear all,
i'd like to spend the information how to install the Java Runtime Exe Installer using SCCM.
in fact this bug hunts oracle since the very first installers for x64 systems.
Why would you not want to install using the unpacked MSI Package:
Well you will miss out the cosy languages (detection inclusive), oracle has prepared for us.
use some script code like this:
REM *** Prepare Settings fix
md "%allusersprofile%\Oracle\Java"
copy /y "java.settings.cfg" "%allusersprofile%\Oracle\Java"
REM *** Create appdata rerouting. This is very bad but i didnt find a different way yet.
REM *** Still it worked for years now without creating a known problem
md %temp%\TempSystemProfile\AppData\LocalLow
reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18" /v ProfileImagePath /t REG_EXPAND_SZ /d %temp%\TempSystemProfile /f
REM *** Start our main installer. Change your options here.
start /w "x" jre-8u25-windows-i586.exe /s SPONSORS=Disable INSTALLCFG=java.settings.cfg REBOOT=ReallySuppress /qn
REM *** Undo the reghack
reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18" /v ProfileImagePath /t REG_EXPAND_SZ /d %%systemroot%%\system32\config\systemprofile /f
don't forget to add regfixes and the config files to the package.
The bug is based on their stupid try to launch a 32bit msiexec process using syswow64\msiexec.exe.
Because this fails, they don't find their unpacked msi package anymore which would be located in syswow64\config, instead of system32\config.
32bit and 64bit processes will simply point to the same path for normal users, which is why this bug doesnt surface on Std user installations.
Rerouting is a very nasty way to circumvent this bug, however i didnt find a better way till now.
btw. thx for the config file fix. saved me a lot of time.
Mike
