Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Delete manually created schedule scan remotely

Created: 05 Aug 2009 | 6 comments
Peterpan's picture
8 Agree
0 Disagree
+8 8 Votes
Login to vote

Is there an option to delete a manually created schedule scan from SEPM remotely? Because We are planning to enforce an schedule scan on our environment, I'm just worrying if I created an schedule scan and SEP client has already an schedule scan which is created manually, it might having a conflict or having a multiple instances of scanning if we cannot remove the manual scan schedule, I want to implement an standard time of scanning for evey dept. if the feature is not yet available I suggest that if possible please include this in the latest build of SEP. thanks

Comments

Peterpan's picture
05
Aug
2009
2 Votes +2
Login to vote

additional idea an option to

additional idea an option to block or to prohibit the adding of manual scanning.

:-)

Zoidberg's picture
05
Aug
2009
5 Votes +3
Login to vote

Scanning

I agree that you should be able to lock that option from the SEPM.
Granted there is no real negative to having an end user run thier own scan; except the preformance issues that the customer will have when it is running.
But I do think that is a needed option for the SEPM to have.

/signed

Scuba Steve's picture
05
Aug
2009
3 Votes +3
Login to vote

conflict

I believe that what would happen is that when the earlier scan starts, it will finish. Then the other scan will start. You won't have 2 scans going at the same time. I to agree that you should have the ability to interact with the user side scans.

Kurt G.'s picture
05
Aug
2009
3 Votes +3
Login to vote

This would be a good option

This would be a good option, however until something like this is implemented there is an option within the AntiVirus and AntiSpyware policy to not allow user defined scans to run when scan author is not logged in. This at least keeps other users' scheduled scans from running when a different user is logged in. As mentioned above, there would not be an issue with multiple scans running at the same time. If an Administrator defined scan does not run due to a user scheduled scan currently running, provided you have configured the missed scan retry interval for the Administrator defined scan, that scan should start shortly after the user scan completes.

Kurt G.
Symantec Technical Specialist: Endpoint Security Advanced Team

Symantec Corporation www.symantec.com

Symantec Enterprise Support: (800) 342 0652 

Scuba Steve's picture
05
Aug
2009
3 Votes +1
Login to vote

but..

I believe this to be accurate.

shp's picture
08
Aug
2009
0 Votes 0
Login to vote

Its a good option..

I also agree with this.... In some situation we need to delete custom scans.

Regards,
Srinivas H.P.
HCL Infosystems Ltd