/build/static/layout/Breadcrumb_cap_w.png

Java Update Through MI

I am having some issues deploying the most recent Java update through a MI. The process seems to start, but then it doesn't end up installing. I attached a copy of my MI.

I also tried to deploy it as a script and run it as a user with admin rights. The install would work correctly, but it would bring up the UAC dialog and force me to hit yes. I wouldn't mind using a script to do it, but I do not want the window to pop up. Any help or ideas would be appreciated.

/s AgreeToLicense=YES IEXPLORER=1 MOZILLA=1 REBOOT=Suppress is the full command line



UPDATE: The MI seems to work fine on Windows XP, but not on 7

0 Comments   [ + ] Show comments

Answers (4)

Posted by: airwolf 13 years ago
Red Belt
0
Rather than rely on our users to use UAC properly instead of just clicking 'Yes' on everything, we disable UAC and restrict them to lower user groups (e.g. Power Users, Users, etc.). I suppose that is more of a philosophical solution, but unfortunately UAC is a pain to deal with for software deployment.

I've heard Group Policy deployment doesn't have this issue, because the domain rights automatically allow elevation above UAC. You can also try reading through this thread - there may be some sort of way around UAC using Application Compatibility: http://www.autoitscript.com/forum/topic/124368-uac-elevate-and-deelevate-scripts/
Posted by: Emir.Brkic 13 years ago
Yellow Belt
0
@lgeier
we have done a similar MI through smart labels which update Java automatically, here is the command line i have used

/s /v/qn "IEXPLORER=1 MOZILLA=1 REBOOT=Suppress JAVAUPDATE=0 WEBSTARTICON=0"

use the default installation command, and enter the above into the run parameters box, its very silent no box pops up UAC doesn't go off or anything, give it a go.

worked for us

hope it helps!
Posted by: GillySpy 13 years ago
7th Degree Black Belt
0
FWIW, jre 1.6.0_27 is available as an update or a full install via patching. It is using the file jre1.6.0_27.msi
Posted by: RichB 13 years ago
Second Degree Brown Belt
0
If a user is logged in with a browser running the Java installer will successfully uninstall older versions but will not install the new version! This makes it a better candidate for "Execute while user logged off" instead of "Execute anytime." I tried putting up a dialog for them to close their browsers before the install but they weren't reading it or they didn't know what it meant so many people were ending up without any java installed.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ