Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > Network Performance Monitor (NPM) Training > Free SolarWinds Training Videos - NPM > Patching Java: Prevent Failed Java Updates - Video

Patching Java: Prevent Failed Java Updates - Video

Updated December 20, 2016


This video walks you through the steps to successfully patch Java with Patch Manager.



All Patch Manager versions

Related Resources

Video Transcription

Click Next, the package is now being published to the wsus server. After the client systems have checked in and reported their state you can identify the client systems that need this update. Use the update management utility to deploy the update to those systems.


The package boot utility works in conjunction with the java installer to ensure that the proper pre-installation environment is established, so that the Java installation will complete successfully from the active tasks node. You can monitor the progress of the java update deployment on your selected target systems. When the task is completed, you can review the success of your task in the task history. Here we see that the java update successfully downloaded and installed on our system. This successful update is made possible because of the packaged food technology and patch manager.


Package boot allows the execution of pre installation tasks such as starting stopping services, terminating processes, running programs, and testing for files with locks and terminating the processes that hold those locks. It also allows the execution of post installation tasks such as starting stopping services, and running other programs.


Let's see what happens when we try to deploy this java update without using packaged food. We will edit a copy of the JRE 6 update 34 package to turn off packaged food and then publish the package without packaged food to our WSS server. Now that we have published, our package boot disabled Jerry 6 update 34 package to our WSS server we will now attempt to deploy it to our target systems. In the task history you can see that the update installation has failed because the features of package boot that are used to properly prepare the installation environment were not available.


Now you know how easy it is to successfully deploy a java update using patch manager and the packaged food technology. 



Last modified