Configuring the Download Source

Procedure

• Trend Micro ActiveUpdate server: Select this option to download from the default update server.
  Trend Micro uploads new components to the ActiveUpdate server as soon as they are available. Select the ActiveUpdate server as a source if you require frequent and timely updates.
• Intranet location containing a copy of the current file: Select this option to download from an Intranet location.
  Download components from an Intranet source that receives updated components.

  Type the Universal Naming Convention (UNC) path of another server on your network.

  Note Setting one or more centralized Intranet locations can greatly reduce network traffic and update time. This option is also useful when you do not want to connect an email server directly to the Internet. Instead, you can connect a front-end server to the Trend Micro ActiveUpdate server on the Internet and then set your back-end servers to receive updates from the front-end server.

• Allow other servers to download updates from this server: Select this option to allow other ScanMail servers to download updates from this server.
  Click Allow other servers to download updates from this server to set ScanMail to create a duplicate copy of the update package on the current server. Normally, ScanMail only downloads components that the user has set it to download or the increments of the components that it needs. When you set ScanMail to duplicate the update package, it will download all the components that are available for downloading.

  For example: There are two Exchange servers (a and b) and each one has ScanMail installed. ScanMail is set up to update server "a" daily and download all components. ScanMail is set to update server "b" every week and download only the spam pattern component. Both servers receive updates from the Trend Micro ActiveUpdate server as required. Therefore, the components on these servers are not always identical and they require different incremental updates when they poll the ActiveUpdate server. Another, more efficient, way to configure your servers would be to set up server "a" to duplicate the update package. Then, you could set server "a" as the source for downloads for server "b", and server "b" could receive incremental updates from server "a" just as if server "a" was the ActiveUpdate server.

  Note You must duplicate the update package to clusters. That is, this option is grayed-out so that you must reproduce the components from one virtual server across all virtual servers on that node by default.