J2SE Runtime Environment 5.0 Update 11
All,
I am struggling to disable Java auto update option for the Java cpl in the control panel. I read so many threads and found that it is possible to disable the java update check box only with the vbscript as a last sequence using CA.
I did it and found that the update tab itself missing. Has anybody done this retaining update tab but only unchecked the option of update?
Also i need to set the temporary internet file settings under General tab of Java Cpl from C:\Documents and Settings\Administrator\Application Data\Sun\Java\Deployment\cache to d:\<username>\ Application Data\Sun\Java\Deployment\cache. I captured this setting via picture taker. It was recording under \C:\Documents and Settings\Administrator\ApplicationData\Sun\Java\Deployment\deployment.properties file.I tried manully copying the above files and folders in the same location when i installed the vendor MSI + MST. As soon i copy the above files, the files under C:\program files\java\jre1.5.0_11\bin are getting deleted (installed by CA).
I am not really why.
Please help me out.
Thanks,
Suma
I am struggling to disable Java auto update option for the Java cpl in the control panel. I read so many threads and found that it is possible to disable the java update check box only with the vbscript as a last sequence using CA.
I did it and found that the update tab itself missing. Has anybody done this retaining update tab but only unchecked the option of update?
Also i need to set the temporary internet file settings under General tab of Java Cpl from C:\Documents and Settings\Administrator\Application Data\Sun\Java\Deployment\cache to d:\<username>\ Application Data\Sun\Java\Deployment\cache. I captured this setting via picture taker. It was recording under \C:\Documents and Settings\Administrator\ApplicationData\Sun\Java\Deployment\deployment.properties file.I tried manully copying the above files and folders in the same location when i installed the vendor MSI + MST. As soon i copy the above files, the files under C:\program files\java\jre1.5.0_11\bin are getting deleted (installed by CA).
I am not really why.
Please help me out.
Thanks,
Suma
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
dj_xest
15 years ago
Hello Sumarchana,
Easy, easy... We know he is a damn rude guy but he is the only one always available to answer your questions here. Before posting, be sure to search Appdeploy website for any hits and take the time to read. You can also browse to the Package database for your particular application like your Java here.. http://www.appdeploy.com/packages/browse.asp?cat=alpha&str=j
There are lots of examples and already tested tricks there.
Next is to search Google like we always do if appdeploy cannot answer it. Chances are your problem might have been fixed somewhere. Lastly is to post your message in Appdeploy if none of the above works. Don´t expect to be answered it in 30 minutes though so you will definitely have your time searching for an answer yourself.
That´s what I did before and it worked!
Easy, easy... We know he is a damn rude guy but he is the only one always available to answer your questions here. Before posting, be sure to search Appdeploy website for any hits and take the time to read. You can also browse to the Package database for your particular application like your Java here.. http://www.appdeploy.com/packages/browse.asp?cat=alpha&str=j
There are lots of examples and already tested tricks there.
Next is to search Google like we always do if appdeploy cannot answer it. Chances are your problem might have been fixed somewhere. Lastly is to post your message in Appdeploy if none of the above works. Don´t expect to be answered it in 30 minutes though so you will definitely have your time searching for an answer yourself.
That´s what I did before and it worked!
Posted by:
sumarchana
15 years ago
Thansk for your kind reply.
I would like to mention here that i was not expecting anybody to throw their answer in 30 mins. Secondly I believe this is a place where we share our experience and knowedge. For this you don't need to be rude always!!
Yes i got the info for the uninstallation as soon as sent this post to the forum. My next Q'n was about deployment properties. I have searched but i did not find the suitable answer, that was the reason for my post. (Please refer post no 1)
I would like to mention here that i was not expecting anybody to throw their answer in 30 mins. Secondly I believe this is a place where we share our experience and knowedge. For this you don't need to be rude always!!
Yes i got the info for the uninstallation as soon as sent this post to the forum. My next Q'n was about deployment properties. I have searched but i did not find the suitable answer, that was the reason for my post. (Please refer post no 1)
Posted by:
dunnpy
15 years ago
Suma,
The updates and other settings can be handled by using Sun's preferred method, using a 'deployment.properties' file.
Details can be found in this post on the board, which contains a link to a Sun document.
Hope this helps,
Dunnpy
The updates and other settings can be handled by using Sun's preferred method, using a 'deployment.properties' file.
Details can be found in this post on the board, which contains a link to a Sun document.
Hope this helps,
Dunnpy
Posted by:
MSIPackager
15 years ago
Not sure about the update tab problem but we use ActiveSetup to deliver (or edit) the required deployment.properties configuration file to set the cache location outside of the users raoming profile.
Why sun think sticking a 50Mb cache in the users roaming profile is a good idea has always been beyond me.
Cheers,
Rob.
Edit: Oh yeah.. well found dunnpy that solution is much more elegant - I'd forgotten about that...!
Why sun think sticking a 50Mb cache in the users roaming profile is a good idea has always been beyond me.
Cheers,
Rob.
Edit: Oh yeah.. well found dunnpy that solution is much more elegant - I'd forgotten about that...!
Posted by:
sumarchana
15 years ago
I feel this extracted Java MSI from the setup.exe is not a real MSI. It does not support uninstall(/x), repair(/f).
I tried insttaling deployment.config and deployment.properties using vbscript via CA and it worked fine with a dummy MSI. It worked fine where as the extracted Java MSI did not allow me to install the files directly to Windows folder(sun\Java\deployment).
I am planning to run the setup via CA. Also copying files and setting registry entries via CA.
Any suggestions?
Suma
I tried insttaling deployment.config and deployment.properties using vbscript via CA and it worked fine with a dummy MSI. It worked fine where as the extracted Java MSI did not allow me to install the files directly to Windows folder(sun\Java\deployment).
I am planning to run the setup via CA. Also copying files and setting registry entries via CA.
Any suggestions?
Suma
Posted by:
sumarchana
15 years ago
If you have a little patience do read the my first post. you never understand the problem instead you laugh which is really not help me to solve the issues around.
When my MST failed to uninstall & repair, i tried with MSI and posted my comments. Now tell me if you still want to laugh. FYI, it uninstalls from Add remove programs also if i try to uninstall from command prompt says the msg "uninstall from add remove pgm since it is already installed". Instead of laughing a better job is to solve this issue.
When my MST failed to uninstall & repair, i tried with MSI and posted my comments. Now tell me if you still want to laugh. FYI, it uninstalls from Add remove programs also if i try to uninstall from command prompt says the msg "uninstall from add remove pgm since it is already installed". Instead of laughing a better job is to solve this issue.
Posted by:
anonymous_9363
15 years ago
What made me laugh is the thought that there might be different kinds of MSIs, ones which don't support uninstall or repair. That is patent nonsense.
Post #6: where does any of the information in that post appear in your previous posts?
Coming to the text "uninstall from add remove pgm since it is already installed", that text does not appear anywhere in the 1.5.0_11 JRE that I have, nor does it appear in MSIExec.EXE or MSI.DLL, so it's not generated by the Windows Installer engine. What does the error actually say? Post the command line you're using so we can see if the error lies there.
Post #6: where does any of the information in that post appear in your previous posts?
Coming to the text "uninstall from add remove pgm since it is already installed", that text does not appear anywhere in the 1.5.0_11 JRE that I have, nor does it appear in MSIExec.EXE or MSI.DLL, so it's not generated by the Windows Installer engine. What does the error actually say? Post the command line you're using so we can see if the error lies there.
Posted by:
sumarchana
15 years ago
ORIGINAL: VBScab
Post #6: where does any of the information in that post appear in your previous posts?
PLEASE REFER POST 1
Coming to the text "uninstall from add remove pgm since it is already installed", that text does not appear anywhere in the 1.5.0_11 JRE that I have, nor does it appear in MSIExec.EXE or MSI.DLL, so it's not generated by the Windows Installer engine. What does the error actually say? Post the command line you're using so we can see if the error lies there.
I got the solution :-)
Posted by:
anonymous_9363
15 years ago
I feel this extracted Java MSI from the setup.exe is not a real MSI. It does not support uninstall(/x), repair(/f).Almost the best laugh of the day. Almost.
It seems that you're editing the extracted MSI directly for your additions, rather than using a transform. Editing vendor-supplied MSIs is a Really Bad Idea and using CAs instead of native WI functionality is bad practice.
Create a transform to contain your additional files. At install time, use the logging switch (as you should when testing ALL your packages...) to create a verbose log. Examine the log and it will show you where failures are occuring.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.