Sending a patch to a machine using patch manager returns with a result of NO PATCHES AVAILABLE.
LANDesk Patch Manager will only apply a patch to a machine that reports that it is vulnerable and needs the patch. So if a machine has not scanned and reported back to the Core Server that it needs the patch it will not apply the patch when scheduled to it and will return the NO PATCHES AVAILABLE. The machine keeps a local record of what it has reported vulnerable to the core so when the task is ran on the machine it checks the local record to see if it needs it or not.
Repair task does not scan the machine until after the repair has happened on the machine.
Work around for this is to:
1- Create a custom group.
2- Add the Vulnerabilities to the group that need to be fixed.
3- Create a Scan and Repair settings that scans for the group created in step one.
4- Select the option under the scan for group to "Immediately repair all detected items"
This will first scan the computer then repair anything that it finds vulnerable.
Windows XP SP3 has a Dependency on 952287 being installed before LANDesk Patch Manager will remediate the patch. Looking in Security and Patch Manager information for a computer could show that Windows XP SP3 is vulnerable, but the Name column will state Dependency. If the XP SP3 Vulnerability is highlighted it will show what dependency is needed.
This has changed in content and 952287 is no longer set as a Dependency for XP-SP3 to be installed.