Java Runtime 6 Update 21
Having a problem with the install, I have created a MST from the MSI then set the application to deploy via SCCM. I applied this to a test collection where I had a 50% failure when I re-advertised the package the ones that had been successful no longer have any of the program files on the machine.
I then manually insatlled the MSI without Transform on a machine then run the MSI again and even though the log file and MSi said it was successful all the program files have been removed and JAVA is no longer installed although it is still in add & remove programs. If I run the MSI a third time on some machines it is a success on others I get the regutils.dll error (Internal Error 2753)
Thanks
Andrew
I then manually insatlled the MSI without Transform on a machine then run the MSI again and even though the log file and MSi said it was successful all the program files have been removed and JAVA is no longer installed although it is still in add & remove programs. If I run the MSI a third time on some machines it is a success on others I get the regutils.dll error (Internal Error 2753)
Thanks
Andrew
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
chrismholmes
13 years ago
Did you get this resolved? If not I have a batch file that installs Java and seems to work on almost installation I have. (60k+ workstations)
Checks for Java Version installed via wmic and if the correct version is already installed it continues to just remove Java Automatic Updates.
Checks for Java Automatic Update and removes it via au.msi after it successfully installs JAVA.
Checks error levels (This still needs work, but of course Java needs to write a better installer...)
Check for JQS prior to install, uninstalls it, installs Java, then uninstalls JQS again... (This should only be a problem on Windows XP)
Install the required Cert for Java to complete the install process.
Java is one of the worst written applications. In an Enterprise environment it is very easy to break the Java install process. If you extract the msi and reinstall via the msi over a working install that was done via the full exe, you will have a log file that claims success, but only one file will exist in the lib folder. (Trying to repair this is a nightmare too)
Java Updater is a joke. I have written MST after MST trying to remove all of Java update components, but most of the time you will not any longer have a Java applet in the Control panel...
AU.msi (Java Auto Updater) can only be uninstalled by the source installed it... So when using Delivery systems that run as LocalSystem and another user installed Java, You have to basically reinstall the AU.msi under LocalSystem to then turn around and uninstall it...
Things that still need to be done in this batch file:
A ton! Need to check for various running Java exe processes prior to running the update. (Too many people leave Java apps running on the machine in the background.) You would think Java would have built this in the install, but if it was done, it was done so poorly.
The batch file really needs a severe rewrite. I have a lot of things in it that no longer apply.
Let me know if you need or want anything like this. This should also work with Java Updates going foward.
Checks for Java Version installed via wmic and if the correct version is already installed it continues to just remove Java Automatic Updates.
Checks for Java Automatic Update and removes it via au.msi after it successfully installs JAVA.
Checks error levels (This still needs work, but of course Java needs to write a better installer...)
Check for JQS prior to install, uninstalls it, installs Java, then uninstalls JQS again... (This should only be a problem on Windows XP)
Install the required Cert for Java to complete the install process.
Java is one of the worst written applications. In an Enterprise environment it is very easy to break the Java install process. If you extract the msi and reinstall via the msi over a working install that was done via the full exe, you will have a log file that claims success, but only one file will exist in the lib folder. (Trying to repair this is a nightmare too)
Java Updater is a joke. I have written MST after MST trying to remove all of Java update components, but most of the time you will not any longer have a Java applet in the Control panel...
AU.msi (Java Auto Updater) can only be uninstalled by the source installed it... So when using Delivery systems that run as LocalSystem and another user installed Java, You have to basically reinstall the AU.msi under LocalSystem to then turn around and uninstall it...
Things that still need to be done in this batch file:
A ton! Need to check for various running Java exe processes prior to running the update. (Too many people leave Java apps running on the machine in the background.) You would think Java would have built this in the install, but if it was done, it was done so poorly.
The batch file really needs a severe rewrite. I have a lot of things in it that no longer apply.
Let me know if you need or want anything like this. This should also work with Java Updates going foward.
Posted by:
langa100
13 years ago
Tried everything in that thread already but thanks anyway. Still no joy :(
Posted by:
deranjer
13 years ago
Thats odd, the transform I posted in the other thread should work with 6u21... just as an update, here is the process.
1. Download File
The transform has more than just the RemoveFiles table edited, it also adds a few other company policy stuff on top, which you can ignore.
Link to transform:http://docs.google.com/fileview?id=0Bz170qNApm2ANWE2N2ZlNmYtOThhOS00MDQ2LWIyZDUtMmJlMmI0ODZjMTgw&hl=en&authkey=CLKt6_YI
Ignore the fact that Google thinks .mst is some sort of word format.
2. On a fresh machine, run the MSI with the transform.
3. Rerun MSI with transform (should remove some temp files, but Java still should work)
4. Rerun MSI again. (Java should recognize that it is installed and exit).
This worked for me with 6u21.
1. Download File
The transform has more than just the RemoveFiles table edited, it also adds a few other company policy stuff on top, which you can ignore.
Link to transform:
Ignore the fact that Google thinks .mst is some sort of word format.
2. On a fresh machine, run the MSI with the transform.
3. Rerun MSI with transform (should remove some temp files, but Java still should work)
4. Rerun MSI again. (Java should recognize that it is installed and exit).
This worked for me with 6u21.
Posted by:
langa100
13 years ago
Chris
Finally I have got it working there were a few issues but have now resolved had to modify it a little to incorporate 2 reg hacks one for the Java Update which is pretty straight forward then there is the previous JAVA versions for some reason (manufacturer's incompetence) previous versions will not uninstall correctly so had to hack the registry within the script basically to remove product keys for update 20 and update 18.
You are a star
Andrew
Finally I have got it working there were a few issues but have now resolved had to modify it a little to incorporate 2 reg hacks one for the Java Update which is pretty straight forward then there is the previous JAVA versions for some reason (manufacturer's incompetence) previous versions will not uninstall correctly so had to hack the registry within the script basically to remove product keys for update 20 and update 18.
You are a star
Andrew
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.