Randomization for scheduled scans -
Updated: 22 Dec 2009 | 4 comments
Status:
In Development
Virtualization is the new technology, the ability to run many machines on one set of hardware -
Ideal is being able to setup 2-5 servers each having there own job to do without the need of having to purchase hardware for each machine.
However when it comes to Endpoint scans are defined by policy, and polcies are assigned to groups.
For implemenation in a VM enviroment you will need to create a group for each VM image so that you can setup your scans not to run all at the same time.
The option is there for liveupdate, why not scanning?
Make it an optional option, if you choose not to turn it on you won't be affected but with the change in technology it will be a definate must in most enviroments.
Comments
I've just run into that with
I've just run into that with our VM environment - the guys have said that the resources spike all at the same time.
This leaves me in a dilemma - break inheritance so I can customize the scans to run at different times or break up the SEPM Client structure I have put together...
Exploring possibility
We are exploring the idea of having a range of time to execute schedule scan and possible would help in VM environment. This is just one instance of VM enhancement, as currently we have made randomization of content update to reduce the thrashing of disk I/O when getting update.
Alan Lee
Principal Regional Product Manager, Enterprise Security Group, Symantec
We plan to deliver this with
We plan to deliver this with Jasper, targeted for April 2010.
Jim Waggoner Director Product Management, Symantec Endpoint Protection, Enterprise Security Group, Symantec
We plan to deliver this with
We plan to deliver this with Jasper, targeted for April 2010.
Jim Waggoner Director Product Management, Symantec Endpoint Protection, Enterprise Security Group, Symantec
Would you like to reply?
Login or Register to post your comment.