05.08.2013 Views

Trend Micro ScanMail for Microsoft Exchange Getting Started Guide

Trend Micro ScanMail for Microsoft Exchange Getting Started Guide

Trend Micro ScanMail for Microsoft Exchange Getting Started Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Trend</strong> <strong>Micro</strong> <strong>ScanMail</strong> <strong>for</strong> <strong>Micro</strong>soft <strong>Exchange</strong> <strong>Getting</strong> <strong>Started</strong> <strong>Guide</strong><br />

3-12<br />

Allowing Other Servers to Download Updates from a <strong>ScanMail</strong><br />

Server<br />

Click Allow other servers to download updates from this server to set <strong>ScanMail</strong><br />

to create a duplicate copy of the update package on the current server. Normally,<br />

<strong>ScanMail</strong> only downloads components that the user has set it to download or the<br />

increments of the components that it needs. See Incremental updates of the pattern<br />

file on page 1-12. When you set <strong>ScanMail</strong> to duplicate the update package, it will<br />

download all the components that are available <strong>for</strong> downloading.<br />

For example: There are two <strong>Exchange</strong> servers (a and b) and each one has <strong>ScanMail</strong><br />

installed. <strong>ScanMail</strong> is set up to update server "a" daily and download all components.<br />

<strong>ScanMail</strong> is set to update server "b" every week and download only the spam pattern<br />

component. Both servers receive updates from the <strong>Trend</strong> <strong>Micro</strong> ActiveUpdate server<br />

as required. There<strong>for</strong>e, the components on these servers are not always identical and<br />

they require different incremental updates when they poll the ActiveUpdate server.<br />

Another, more efficient, way to configure your servers would be to set up server "a"<br />

to duplicate the update package. Then, you could set server "a" as the source <strong>for</strong><br />

downloads <strong>for</strong> server "b", and server "b" could receive incremental updates from<br />

server "a" just as if server "a" was the ActiveUpdate server.<br />

Note: You must duplicate the update package to clusters. That is, this option is enabled<br />

and grayed-out so that you must reproduce the components from one virtual server<br />

across all virtual servers on that node by default.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!