2 Replies Latest reply on Oct 23, 2013 6:29 PM by brentdw

    VirusScan Post-Deployment Exclusions


      The fact that I can't find any information about this indicates that it's probably nothing to worry about, and that I'm probably misunderstanding something, but I want to check anyway to put my mind at ease. After deploying VirusScan via Orchestrator, it takes several minutes (presumably the policy enforcement interval) to implement file and folder exclusions. This probably isn't a big deal for workstations, but I fear it could be harmful to servers, especially SQL, Exchange, and Active Directory. Is there a way to force VirusScan to implement these exclusions immediately, or am I missing something here?