How to Manage Superseded Patches (LDMS 9.0 SP2 and earlier)

Applies to LANDesk Management Suite 8.8 and LANDesk Management Suite 9

LANDesk provides data about if a patch has been superseded by another patch. When this is true, the previous patch is no longer needed because the newer patch contains all the needed fixes. However sometimes this is difficult to manage.

Problem

It is difficult to tell what Vulnerabilites are no longer needed because a newer Vulnerability has replaced it.

Solution

1. Open the LANDesk Management Suite console.
2. Open Security and Patch Manager (Patch and Compliance in 9.0)
3. Click on All Items.
4. Scroll over to the "Replaced" column. Click on the heading to sort by this column.
5. Drag all the Definitions that Say "ALL" to the "Do Not Scan folder".

Depending on the number of end points that are being managed this could take along time to complete. If you would like to avoid the long delay move the superceded patches over in smaller groups.

Additional Information

The following SQL statements will move all Vulnerabilities that have been completely superceded by a newer Patch to the Do Not Scan Folder. This will only work in LANDesk Management Suite 8.8

Assigns the Vulnerability to the Do not scan folder:

UPDATE vulnerability SET Status=0 WHERE SupercededState='2'

Removes client specific scan information for the vulnerabilites:

DELETE FROM ComputerVulnerability
INNER JOIN Vulnerability ON ComputerVulnerability.Vul_ID = Vulnerability.Vul_ID
WHERE(Vulnerability.Status = 0)