Software Deployment

I don't think it is possible to get this package to repair without repacking it. The msi is basically just a wrapper for the install scripts, so you don't get the windows installer repair functionality here. I had to repack it myself, after giving up trying to find a solution for this problem.

The only item you have to pay attention to when repackaging Java is that some of the installer logic is lost. Some registry and com objects change depending on what version is the newest and the default Java. What I typically do is suggest that the MSIs are installed from oldest to newest to ensure that the Java is properly installed. If the default Java is not the newest version you will have to either configure that in the setup capture or have a script put the machine in the correct state. In one case I could not guarantee the install order for Java so I wrote a VBScript that ran at logon which talked to Active Directory to find out what was the newest Java assigned to the user then update the necessary registry entries so that all the Java runtimes would properly co-exist. You probably don't want to do that far but it is important to note that improper deployment of JVM setup captures can cause application issues that would not exist with the vendor installer.

Hi kkaminsk,
interesting...
Could you please tell us, which Reg-Keys are responsible for the version that is actually used?

About the repair case:
Has somebody ever tried to alter the original MSI to that effect, that the conditions of the real installation sequences also permit a reinstall?

Regards, Nick

ORIGINAL: nheim

Could you please tell us, which Reg-Keys are responsible for the version that is actually used?



Sure but be patient. My VMWare machine lost the drive with all my VMs on it this weekend so I'll be mostly useless for a bit.

You should do your own research because I did this quickly and these items may change depending on how complete your setup captures are. But here is my quick list as to what to watch for when using setup captured MSIs to install Java out of order. This is based on a machine where Java 1.5.x is the latest version installed and Java 1.4.1.02 is installed out of order via a setup capture.

Actually ignore the COM stuff because this example actually sucks for that but I did find a COM issue with out of order Java installations a couple years ago.

[HKEY_CURRENT_USER\Software\Classes\CLSID\{8AD9C840-044E-11D1-B3E9-00805F499D93}]
@="Java Plug-in 1.4.1_02"

[HKEY_CURRENT_USER\Software\Classes\CLSID\{8AD9C840-044E-11D1-B3E9-00805F499D93}\InprocServer32]
@="C:\\Program Files\\Java\\j2re1.4.1_02\\bin\\NPJPI141_02.dll"
"InprocServer32"=hex(7):00,6a,6e,48,2b,63,46,69,44,77,38,32,4b,74,6b,73,35,47,\
2b,34,71,43,6f,6d,70,6c,65,74,65,3e,75,79,71,60,34,2d,67,55,4f,39,51,32,73,\
3d,59,4a,41,34,25,6b,00,00,0a,00,00
"ThreadingModel"="Apartment"

[HKEY_CURRENT_USER\Software\Classes\CLSID\{CAFEEFAC-0014-0001-0002-ABCDEFFEDCBA}]
@="Java Plug-in 1.4.1_02"

[HKEY_CURRENT_USER\Software\Classes\CLSID\{CAFEEFAC-0014-0001-0002-ABCDEFFEDCBA}\InprocServer32]
@="C:\\Program Files\\Java\\j2re1.4.1_02\\bin\\NPJPI141_02.dll"
"InprocServer32"=hex(7):00,6a,6e,48,2b,63,46,69,44,77,38,32,4b,74,6b,73,35,47,\
2b,34,71,43,6f,6d,70,6c,65,74,65,3e,75,79,71,60,34,2d,67,55,4f,39,51,32,73,\
3d,59,4a,41,34,25,6b,00,00,0a,00,00
"ThreadingModel"="Apartment"

[HKEY_CURRENT_USER\Software\Classes\CLSID\{CAFEEFAC-0014-0001-0002-ABCDEFFEDCBB}]
@="Java Plug-in 1.4.1_02<applet> redirector"

[HKEY_CURRENT_USER\Software\Classes\CLSID\{CAFEEFAC-0014-0001-0002-ABCDEFFEDCBB}\InprocServer32]
@="C:\\Program Files\\Java\\j2re1.4.1_02\\bin\\NPJPI141_02.dll"
"InprocServer32"=hex(7):00,6a,6e,48,2b,63,46,69,44,77,38,32,4b,74,6b,73,35,47,\
2b,34,71,43,6f,6d,70,6c,65,74,65,3e,75,79,71,60,34,2d,67,55,4f,39,51,32,73,\
3d,59,4a,41,34,25,6b,00,00,0a,00,00
"ThreadingModel"="Apartment"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\JAVA_SUN]
"Bitmap"="C:\\Program Files\\Java\\j2re1.4.1_02\\bin\\ActPanel.dll,1000"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\AdvancedOptions\JAVA_SUN\SELECT]
"RegPath"="Software\\JavaSoft\\Java Plug-in\\1.4.1_02"
"Text"="Use Java 2 v1.4.1_02 for <applet> (requires restart)"

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment]
"CurrentVersion"="1.4"

I had the same problem with Java... Unfortunately as sikkert said... The MSI is just a wrapper for the Java install scripts. When I first packaged Java I was new to packaging and I couldn't work out why when I did a repair the only things to come back were the readme files and some copyright file. I tried a few things then decided the best course of action in the case of a repair is to just uninstall it and reinstall it.

I know this isn't much help... More just to let you know that the only way to really enable a repair is probably to do a setup capture.