Recently we have been seeing vulscan using 40-50%cpu usage with spikes to 100% and slowly machines to a crawl. I have updated the local scheduler with the belownormal switch and the cpu usage stays below 10% but a couple of the machines still run slowly while being scanned.
If someone could provide a breakdown of the vulscan process, how and what it scans, it would be greatly appreciated. We are on SP3 and the users having the issues have the updated clients.