• State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 21 subscribers
  • Views 301 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

New Java Upgrades are fully installing

strict

My testing is showing that the new Java upgrades (7u5 and 6u33) are fulling installing when not present previously on the system, specifically:

6u33x86 update does a full install

7u5x86 update does a full install

7u5x64 update does a full install

It would appear that Applicability rules are all looking at the same java.dll file and installing if it is less than version 6.0.330.3 and 7.0.50.5 respectively.  To me this means that if that java.dll is anything less than 6.0.330.3 both will be installed.  I am not super familiar with java.  Is this by design?

Thanks!

-mark

  • 0

    You are right on track. Java is designed to allow both versions 6 and 7 to live on the same machine concurrently to provide compatibility with certain software. Approving 7u4 against a machine that is running 6u33 would result in the installation of 7u4.

  • 0 in reply to David_Di_Blasio

    understood.  thank you.  wondering if these could be set to minor impact and never reboots?  do you ever test out the extremely useful minor impact option?

  • 0 in reply to strict

    Greetings Mark.

    The Impact="Minor" setting is an authoritative statement that the update will never require a system restart and will never require a service restart.

    Since we explicitly terminate one or more Java services in order to install the Java updates, our update package is not suitable for classification as "Minor".

    The Reboot Behavior setting in the package definition is informational only, for display in the console, and has no impact whatsoever on how the Windows Update Agent actually behaves.

    That value is set to "Can Request Reboot", because we cannot authoritatively determine that a system will never require a reboot or will always require a reboot.

    The authoritative setting for how the WUAgent handles system restarts is determined by the Pending Reboot Result Code(s) that is defined on the installation file screen of the Package Wizard.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.