Use the Source tab to set which components to download.
To set the update source:
-
From the scheduled update rule or manual update document, click the Source tab to select one of the following update sources (see Automatically) or (Manually):
-
Replicated database- ScanMail servers automatically replicate (pull) the new pattern files from the central ScanMail server.In this model, a hub ScanMail server downloads the new updates and then all spoke ScanMail servers automatically pull the updates from the hub server.Even if Download only is set, ScanMail will still deploy (that is, apply) components to the spoke servers.
Note
Domino does not replicate the Update Database automatically. Create a connection document in the Domino directory and specify the direction of the replication and the central server, which will download the components from the ActiveUpdate server. -
ActiveUpdate server- ScanMail servers automatically download the latest component from the Trend Micro ActiveUpdate server.
Note
By default, ScanMail implements digital signature checking whenever it downloads components from the Trend Micro ActiveUpdate server. The signature files (*.sig) ensures secure component download from the Trend Micro ActiveUpdate server.Using the ActiveUpdate server is the simplest way to update components. In a multi-server environment, you can configure every ScanMail server to independently poll for component updates using ActiveUpdate, or designate a single ScanMail server to act as a hub server for downloading updates and then have your spoke ScanMail servers pull in the update using replication.Tip
See Update Issues to troubleshoot update issues. -
Other Internet source- ScanMail servers can download the pattern file and scan engine from another non-Trend Micro Web site (for example, your local Intranet Web site)Type the URL or UNC path of your own "ActiveUpdate" server in the Address field.
Note
The UNC source only applies to ScanMail for Domino for Windows. Updating from another source requires having the corresponding signature files (*.sig) saved in the location where the latest components are located. Otherwise, the absence of the *.sig file will lead to an unsuccessful update.To disable checking for the signature files, open the Domino console, and type the following command and press Enter:set configuration disablesecureupdate=1
-
-
Click Save & Close.