I actually had 2 auto responses I made that almost killed the server. I made one for rogue printeres and Virus detections. If I have both enabled the sqlserver service goes up to 711mb of meory usage and makes the CPU stay between 65-100% constinatly. If I disabled them it drops the CPU back to normal, between 0-25%. Memory on that service drops to 500mb. I do have a lot of filters in the rogue printer detection. up to 15 filters. 13 of those are IP adress ranges. Then for my virus detection I have 7 threat types and one Event Description. I might see why the rogue printer response woudl do that, but why woudl the other one? and what other way would I have done it? Is there a setting I missed?
Just enabling the virus detection send it over the top, it really bogs the server down.
For the RSD Response you should check your filter and make sure you have added "New Detection Equals True". This will keep the response from repeatedly triggering on machines that have already been detected.
On the VSE response I'm guessing the problem is something similar...the response is being triggered very frequently. You may want to ad the filter "Threat Handled equals false" so that the response is only triggering when a virus has been detected but the remediation failed. Also you can filter out event IDs 1051 and 1059 which are actually classified as "threat events" even though they don't really indicate a virus detection. To see what those events are and to filter them go to "Menu | Configuration | Server Settings | Event filtering | Edit".
Here is the xml part of the response
<ResponseRule id="12" name="Virus Detection"
I can disable that response and the server goes back to like nothing is running on it. Again, it is not detecting anyhting, we don't get an emails except for the few it does see. Like last friday, we have 1 machine hit 7 times, that as it all day long. So 7 emails should not make the server run
sqlserver process is at 847K of used memory, which is higher than I have ever seen it on this box. I turn that response off (disable it) it drops down to 450K and runs fast. I also am attaching my filter for this response.