The Antimalware Configuration settings define the server for malware cleanup and Antimalware Agent installation as well as the default server for an Ondemand Content Master. To access these settings, navigate to Security > Getting Started > Protecting Against Malware, and click the link under the Antimalware Server section. You can also access them under Security in the Management Zone Settings.
One Primary Server needs to be designated as the Antimalware Server to perform Antimalware-related maintenance tasks for your zone. This server also functions as an Ondemand Content Master (OCM) by default. If you designate one or more additional Primary servers as OCMs in the zone, the OCM designation can be removed from the server selected in this configuration as the Antimalware Server. You can make that change via the Server Hierarchy configuration.
Any Primary servers designated as OCMs need to meet the Ondemand Content Master requirements. For more information, see Ondemand Content Master - Requirements.
The Antimalware Server performs maintenance once a day, which can include cleaning up old malware events and rebuilding the bundle for the Antimalware Agent installation. You can define the time that the maintenance occurs and remove old malware events or rebuild an agent installation bundle manually.
When you configure the age limit for automatically removing old malware events according to the daily maintenance schedule, the configurable range is from 1-180 days.
The Ondemand Content Master requires an Internet connection to communicate with and download content from the external Antimalware cloud service. This service is a Content Distribution Network (CDN) that manages all the malware signature files required to disinfect files on managed devices.
Configuring a proxy: If the OCM requires a proxy to access the service, the OCM server’s Subscription proxy configuration file is used.
To configure the proxy configuration file for a proxy server:
On the Primary Server that is configured as the Ondemand Content Master, create a JSON file titled ODCExternalConfig.json in the location indicated below for your server type:
Linux: /etc/opt/microfocus/zenworks/
Windows: C:\Program Files (x86)\Micro Focus\ZENworks\conf
An example of the content within the ODCExternalConfig.json file is shown below:
URL proxy format: username:password@host:port
{
"proxyUrl": "johndoe:novell@10.71.66.208:8080"
}
If credentials are not required, use this format example:
{
"proxyUrl": "@10.71.66.208:8080"
}Save the JSON file. The settings are effective within 15 minutes, but you can restart ZENworks services to apply the settings immediately.
A Satellite proxy must be configured with the Content Role and have SSL enabled in that configuration. If you are using a Satellite as proxy:
Save a copy of the JSON file on the Satellite and restart the ZENworks Agent Service on that device. The JSON file location for satellites is provided below:
Linux: /etc/opt/novell/zenworks/
Windows: C:\Program Files (x86)\Novell\ZENworks\conf
Accessing the CDN: The following URL must be open to access the CDN: https://microfocus-2dcb60a8-26c9-4560-9cc2-34a16ea5f6e6.2d7dd.cdn.bitdefender.net
Information: while configuring, if the agent displays "You are at risk" alert message, then check the Troubleshooting section.