0 Replies Latest reply on Jan 3, 2013 4:17 PM by srussell7

    Move Agentless 2.5

      I have deployed Move AV Agentless 2.5 for approximately 6mos now.

      I am wondering if anyone has any info on Best Practices related to SVA capacity IE> how many vm's can the SVA handle?

      As well should I increase both the cpu and memory of the SVA's from default to double?  I am seeing some cpu issues already and vm count on SVA's is quite low.

      I am also trying to find some info on scheduling the On Demand Scans.  I have already configured the Scan options and times via the SVA scan but

      I notice that scanning is taking place during the DO NOT scan time blocked out in White in the policy.

       

      Any info would be appreciated.

      Thanks