Windows Server 2008 R2
I am having a big problem with our Patch and Compliance from LANdesk Management Suite. Here is the case.
There is a new patch that was released for a critical vulnerability. I quickly added the patch from the Unassigned folder to the Scan folder in Patch and Compliance. This patch should be detected on most systems, since I have not patched for it yet.
Anyway, I waited for 2 days now and nothing shows to have been detected, or even scanned for that matter.
I also tried to run a large Patch and Compliance scan manually as a task to refresh the results, but all of the systems (1400 PCs) filed with the return code 443 "Server busy, unable to complete request"
I am not sure how to get the patch, which I know is critical, to be detected via the scan. Any help would be greatly appreciated.
I have attached a screenshot of the task result.
Is this the only patch that has not scanned?
Looks like your IIS App Pool could be hung and not processing any scans. Can you check the app pool to see what it's doing? You can try to restart it and see what happens.
Check the "incomingdata" folder on the core server and see if it is full of scans. Also, what version is postcgi.exe?
The quickest troubleshooting tip is to reboot your core and start another scan and see if that clears it.
Some services and or IIS can hang at times, a quick reboot will solve these types of issues many times
No it is not the only patch that is not scanning. It seems to be affecting all of the patches within the last few weeks.
Where can I find the app_pool that you are referring to?
Where is he incomingdata folder located (sorry)?
I rebooted the core but this did not help. It has still not showed any devices to be scanned.
Look at IIS on your Core Server under the Administrative Tools. There are a bunch of app pools there that should all be started.
Incoming data is in C:\Program Files (x86)\LANDesk\ManagementSuite\incomingdata (replace driveletter with yours and leave the (x86) on Win2003)
Also check your IIS logfiles for more information.
Frank, I checked the Application Pools and all of them are "Started" now.
I didn't see any errors or warnings over the last 24 hours, and over the last few days it hasn't had any erros related to IIS that I can find.
Check the Vulscan logs on your clients for errors. Running "vulscan e" opens up the map where they are located. Maybe there is some useful information in there.