Sophos AP/APX users may experience issues registering to Sophos Central. More info available here: Central Wireless
This article provides an overview to the deployment options available to an administrator when installing the Guest VM Agent component of the Sophos for Virtual Environments product across their estate..
Applies to the following Sophos products and versions Sophos For Virtual Environments
Sophos provide a number of supported methods for deploying the Sophos Guest VM Agent to your Hyper-V or VMware Estate - these are:
All of the methods above require the Security Virtual Machine to be deployed prior to the steps below being completed. For information on how to do this please see the Sophos for Virtual Environments Startup Guide. All of these options also rely on you having the Sophos Guest VM Agent installer available.
Once the Security Virtual Machine has been successfully deployed; the installer can be located in:
\\<SVM IP ADDRESS>\public\
Note. Please replace <SVM IP ADDRESS> with the IP address of the primary network card specified in the Security Virtual Machine installation process. If you are using the Guest VM Migration functionality introduced in Sophos for Virtual Environments 1.2.0 then this address can be the facing address of any of the Migration enabled Security VMs you specified during installation.
To install the Sophos Guest VM Agent run the "SVE-Guest-Installer.exe" located in the "Public" folder on the Security Virtual Machine. You will need to enter the IP address of the preferred Security VM during this installation.
You can distribute the SVE-Guest-Installer.exe across your network regardless of which host the Guest Virtual Machines are hosted on, as long as you remember to specify the IP address of the correct Security Virtual Machine.
If you are using the Guest VM Migration functionality introduced in Sophos for Virtual Environments 1.2.0 then this address can be the facing address of any of the Migration enabled Security VMs you specified during installation.
You can follow the standard deployment methods to install the Guest VM Agent on a template virtual machine prior to the image being created.
Important. If you are not using the Guest VM Migration functionality introduced in Sophos for Virtual Environments 1.2.0 then please make sure that Guest VMs built from the template VM reside on the same host as the Security Virtual Machine. Although Guest VMs on a different host to their Security Virtual Machine are still fully protected you may notice increased latency when opening files as the scan data will need to traverse the network.
The SVE-Guest-Installer.exe is compatible with deployment tools and methods that can be used to deploy .exe files across your estate (for example Group Policy Startup Scripts). The installer can be used with a number of switches to aid in this:
Note. The above commands are case sensitive.
If you are using the Guest VM Migration functionality introduced in Sophos for Virtual Environments 1.2.0 then the specified IP address can be the facing address of any of the Migration enabled Security VMs you specified during installation.
These switches can be used in combination of each other, for example:
SVE-Guest-Installer.exe SVMIPAddress=10.1.1.1 /quiet
SVE-Guest-Installer.exe SVMIPAddress=10.1.1.1 /quiet InstallFolder=C:\path
If you require assistance with creating scripts to aid in the deployment of Sophos for Virtual Environments please contact your Sophos Partner or Sales Account Manager to discuss our Professional Services Consulting offerings.
If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article. This is invaluable to us to ensure that we continually strive to give our customers the best information possible.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.