Software patch selection tool

• US 6,477,703 B1
• Filed: 06/29/1999
• Issued: 11/05/2002
• Est. Priority Date: 06/29/1999
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Company (HP Inc.)
• Inventors: Titman, Mary Beth, Smith, Randolph C., Chan, Kay, Richards, Linda, Spotts, Roger, Ritzer, Janet, Stapleton, Lisa, Marakovits, Eric, Macias, Abbey
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US09/342,763
• Time in Patent Office: 1,225 Days
• Field of Search: 717/1, 717/11, 717/168, 717/169, 717/170, 717/172, 717/174, 717/177, 707/203, 707/204, 707/511
• US Class Current: 717/168
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A patch selection tool providing a method and apparatus for identifying software patches for installation on a computer system in which current versions of software applications installed on the computer system are identified as well as currently installed patches, products, and versions. An initial list of recommended patches is generated based on the combination of the installed products and the validated list of datasheet selected products, a final list is created by modifying the initial list to remove bad or outdated patches.

Claims

1. A method for identifying software patches for installation on a computer system comprising the method steps of:

identifying the current versions of software products installed on the computer system,

running a script on the computer system to create a Product Specific Information file listing patches and products, including versions, that are currently installed on the system,

pulling a list of the currently installed patches, products, and versions from the PSI file,

identifying any currently installed patches which are bad,

filling out a datasheet identifying new software products to be installed on the computer system,

validating new software patches for those new software products identified on the datasheet having patches associated with them that pass any version checks that apply,

generating an initial list of recommended patches based on the combination of the list of currently installed patches that are not bad and the validated new software patches.

2. The method for identifying software patches for installation on a computer system as claimed in claim 1, the step of identifying the current versions of software applications further comprising the steps of identifying product versions and the step of ascertaining whether a patch will install.

3. The method for identifying software patches for installation on a computer system as claimed in claim 1, the step of identifying the current versions of software applications further comprising the step of filling out a datasheet, wherein, the identification of products installed on the computer system provides for the identification of associated patches.

4. The method for identifying software patches for installation on a computer system as claimed in claim 1, further comprising the step of determining whether any recommended patches require dependent patches, and

adding missing dependent patches to list of recommended patches if the dependent patch is not all ready recommended, installed, or superseded by a dependent or currently installed patch.

5. The method for identifying software patches for installation on a computer system as claimed in claim 4, further comprising the step of checking the list against itself and against the list of installed patches to remove patches that are anticipated by newer versions of software not requiring a patch, such software having already been installed or recommended.

6. The method for identifying software patches for installation on a computer system as claimed in claim as claimed in claim 5, wherein the list is also checked to make sure the recommended patches will run on the customer'"'"'s system, when the customer tries to install, and wherein, if there are bad patches that haven'"'"'t been resolved, the user is presented with a list of the bad patches, and is forced to resolve them before continuing.

7. The method for identifying software patches for installation on a computer system as claimed in claim 6, wherein, if the patch tool was already going to recommend a newer version of a bad patch, the new patch is given.

8. The method for identifying software patches for installation on a computer system as claimed in claim 7, further comprising the step of checking the list of recommended patches for patches that cause structural conflicts, wherein, structural conflicts are presented to the user for further, manual intervention.

9. The method for identifying software patches for installation on a computer system as claimed in claim 4, further comprising the step of reviewing the final list of recommended patches and deselecting any of the recommended patches or manually adding additional patches.

10. The method for identifying software patches for installation on a computer system as claimed in claim 9, further comprising the step of ordering the patches for installation on the computer system.