This article gives a list of frequently asked questions with corresponding answers regarding the Sophos Virtualization Scan Controller.
Applies to the following Sophos product(s) and version(s)
Sophos Virtualization Scan Controller
The Sophos Virtualization Scan Controller is designed to overcome resource issues when running concurrent scheduled scans across virtual machines. A more detailed overview with links to documentation can be found in KBA113828.
Can I use the Sophos Virtualization Scan Controller to specify scan settings other than the schedule? For example specific drives, archive files etc?
No. The Sophos Virtualization Scan Controller uses the same ‘Full System Scan’ mechanism found in the console (right click option) and as such has the same limitations. Further information on what is scanned during a full system scan can be found in article KBA25358
Why did the scan run at a different time to the one specified in the config?
There two important factors to consider when specifying the time that the scans begin.
- The scan times are specified using UTC and as such this will need to be taken into account when configuring scan times. If you are unsure of how to convert to UTC, there are a number of websites that will do this for you. The following is the Microsoft example of how to perform a conversion: http://support.microsoft.com/kb/884804
- The scans are initiated from the Management server by the Virtualization scan controller and as such will use the system time on the Management server. So if managing machines in different time zones you must adjust the scan start and stop times accordingly (in UTC) to accommodate this.
What changes are made to the database as part of the Virtualization Scan Controller installation?
The installation creates three tables in the SOPHOSXX database. These tables are removed if the VSC is uninstalled. The names of these tables and the corresponding fields are shown below:
Can I use the Virtualization Scan Controller with a DRS (Distributed Resource Scheduler)?
Yes. As long as the machine is still accessible by SEC (management service) then VSC will continue to manage the machine. It would be recommended that a group is defined that covers all machines, independent of which host they are actually running on - that way, DRS can shift them around, and VSC will spread the scan load across the whole 'cluster' of hosts.