Software Deployment

Have you looked into trying to remove problem at source (ie removing the Java from this MSI?) It may be installed in a separate component, which can be isolated and removed, or maybe it's being installed via a custom action?

Hi
I am new to Installshield and i need to create a major upgrade(Uninstall existing one and install new version) for a module using silent installation in MSI. I tried it once but it didnot uninstall the older version. Can someone plz post the way to create a silent installation?
Regards
Udit

udit1002, please post this in a separate thread.

meastaugh1, I have had a look at removing it from the package but don't think it's going to be possible - this is a repackage of a legacy app and it won't be that straightforward. I know the re-install of the JRE will fix it if I can get it to work.

I haven't had to do it, but it looks like you just need to specify a custom action that will launch your second MSI at the end of the sequence table: [url]http://helpnet.installshield.com/robo/projects/helplibdevstudio9/IHelpNestedInstallations.htm[/url]

I can successfully get the MSI to try and run when I nest it, but it doesn't run with the same permissions as the MSI it is nested in so fails. Is there any way to ensure it runs elevated just like the MSI being installed?

ORIGINAL: dgdavis

I can successfully get the MSI to try and run when I nest it, but it doesn't run with the same permissions as the MSI it is nested in so fails. Is there any way to ensure it runs elevated just like the MSI being installed?


Unless you strip out the JRE part of the install you are setting yourself up for problems imho.

One other way is to get your isntall to remove a keypath of the original JRE and then call the Java console to run....that will prompt a self repair. Messy and ugly actually but it will work.

I've tried removing the JRE in the application, but this just stops it working altogether. Even if I change the shortcuts to start using javaw instead of jvmstartw I get funny errors about 'unable to create Java Virtual Machine'.

The problem with the keypath thing is that the JRE is a machine-assigned app through Group Policy, not to the user, hence autorepair doesn't kick in.

ORIGINAL: dgdavis

I've tried removing the JRE in the application, but this just stops it working altogether. Even if I change the shortcuts to start using javaw instead of jvmstartw I get funny errors about 'unable to create Java Virtual Machine'.

The problem with the keypath thing is that the JRE is a machine-assigned app through Group Policy, not to the user, hence autorepair doesn't kick in.


Yep that is going to be a problem. Workstation assigned apps have this issue with self repair.

Ok one step at a time.

1. What Java is in the build? MS JVM I assume?
2. Have you tried to capture the app on a clean build that has no JVM installed at all?
3. Have you tried to capture the app on a clean build with MS JVM installed?
4. Look for keys in HKLM\System\CurrentControlSet\Control\Session Manager\Environment that start with JRE_. Perhaps JRE_BIN= or JRE_PATH=

You really need to capture this thing as raw as you can to find out how clever the installation is regarding existing Java. One way is to remove MS JVM and capture it.

Let us know how you go.

I might add that you should be able to install and run multiple versions of Java side by side. I have done it and it works perfectly. Something in your install/capture might be conflicting though.