Jump to content

Recommended Posts

Posted

We're finding that whenever our file servers perform the scheduled VSS tasks, SCCM's Endpoint Protection on-access scanning is battering the CPU as it tries to scan every file being copied. This has caused intensive CPU usage during these scheduled VSS jobs, slowing down not only the progress, but also everything else on the server. I can't seem to figure out how to add VSS as an exception in the Antimalware policy in SCCM, as the syntax I've seen for other AVs is not compatible.

 

Can anyone shed any light, or share their practices for file server scanning/VSS?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...