Option to disable the Full scan that runs after the SEP Client is installed.
Updated: 10 Dec 2009 | 5 comments
Status:
In Review
While Creating a Custom Install Package there should be an option in SEPM to Enable or Disable the Full scan that runs on the machine when SEP is installed . In SAV there was a option to disable the full scan. It will be great if something like this can be done with SEP also.
idea Filed Under:
Comments
Hmm I am up in the air on
Hmm I am up in the air on this one. I think that the full scan is important for 99% of the users who install SEP, and I think if their was an option (like a pop up box saying "Do you want to run a full scan now?") 80% of people would just click no and not do the full scan. BUT I am also a fan of giving people the option of doing what they wish with software they buy. I would like to see this implemented as an option in something like a command line switch, that way people who are scripting massive installs of SEP they can disable this option if they wish. Usually the type of people who actually know what a command line switch is are the kinds of people that understand the risk of not having a full scan after the install. So I will vote this yes, but I also see the merit in having it there, because I think most people don't understand that there really is a need for a full scan after the install.
Grant-
Please don't forget to mark your thread solved with whatever answer helped you : )
Like Mr.granthall told
Like Mr.granthall told command line swich is the better option
Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind
This knocks performance post client install
there should be an option to suppress a full scan running directly after the client is installed or upgraded.
Clients typically update content directly during or after client installation, which makes sense. To hit them with a full scan on top of that is excessive performance draining. It is a bad first impression to have the new AV client cripple a machine's performance. Especially lower-spec'ed ones (512MB RAM) look like they have frozen.
In addition, by being able to
In addition, by being able to disable this you could make sure the client was in teh right group WITH the right exclusions before allowing the endpoint to scan data that could potentially be corrupted by teh scan.
_________________________________________________________________
Please remember to mark the thread 'SOLVED' with the answer that most helped you by choosing 'Mark As Solution' on the applicable answer
This might be related to
This might be related to missed event handling. When SEP is installed and sees the new schedule scan policy it looks as if it missed one so kicks it off.
Have you tried disabling that option?
Jim Waggoner Director Product Management, Symantec Endpoint Protection, Enterprise Security Group, Symantec
Would you like to reply?
Login or Register to post your comment.