/build/static/layout/Breadcrumb_cap_w.png

Java Update to v18 via Group Policy

I recently deployed Version 6 18 via Group policy and it does not work at all after this. I used the MSI file but did not use a mst file. What problems would this cause? Can I go back and insert the MST or do I need to uninstall and redeploy.?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 11 years ago
Red Belt
0
Generally speaking, if you can 'Next', 'Next', 'Next' through an install - as you can with JREs - you don't need a transform.

As to the problem, "it does not work at all" isn't terribly descriptive. The cause could any number of things. As ever, ProcMon will show exactly what's going on.

BTW, your Subject line includes the word "Upgrade". Did the GP use the 'Upgrade' functionality? I haven't used that in years, having had limited success (OK, no success at all...) very early on in my GP days. Nowadays, I just take users/groups out of scope which will trigger an uninstall, replacing their membership with a new group for a new GPO which will then install the later release.
Posted by: cougarnyy 11 years ago
Yellow Belt
0
How would I know if it was deployed correctly? Anything I should check to verify?
Posted by: cougarnyy 11 years ago
Yellow Belt
0
Thanks for the reply. Well When I go to the Java test page http://www.java.com/en/download/help/testvm.xml it fails.

as well as any user web applications that requires Java. It does have JRE 1.6.0_18 in the Advanced tab in IE as well as the Java Console. Not sure where to do from here.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
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