Hi Guys,
Have used ESET AV products and the different incarnations of the RA for as long as I can remember, always because of the excellent balance between top-notch threat detection and low resource usage;
However is it just me that has started noticing this excellent situation is becoming sqewed? Have done a few ESET deployments recently where the hit on end users systems was not only noticable but sometimes work-stopping.
Now I am fully prepared to accept that it is my configuration of the policy rather than ESET itself, but with so many sections of the ESET AV engine now and my rather busy schedule at work for the next month or so, I dont have time to trial and error a test rig of tiny configuration changes.
In particular I notice that outlook performance suffers badly when using exchange and the default startup scan is enough to seriously impact all but the newest machines, especially at a time when windows is already rapeing in the IOPS.
Could anyone share there experiences of recent ESET deployments and if not too much to ask, the configuration XML for clients? In order for me to correlate wether your experiences and my experiences are a direct relation to options chosen in the configuration.
Thanks,
//TrX
Have used ESET AV products and the different incarnations of the RA for as long as I can remember, always because of the excellent balance between top-notch threat detection and low resource usage;
However is it just me that has started noticing this excellent situation is becoming sqewed? Have done a few ESET deployments recently where the hit on end users systems was not only noticable but sometimes work-stopping.
Now I am fully prepared to accept that it is my configuration of the policy rather than ESET itself, but with so many sections of the ESET AV engine now and my rather busy schedule at work for the next month or so, I dont have time to trial and error a test rig of tiny configuration changes.
In particular I notice that outlook performance suffers badly when using exchange and the default startup scan is enough to seriously impact all but the newest machines, especially at a time when windows is already rapeing in the IOPS.
Could anyone share there experiences of recent ESET deployments and if not too much to ask, the configuration XML for clients? In order for me to correlate wether your experiences and my experiences are a direct relation to options chosen in the configuration.
Thanks,
//TrX