04.03.2013 Views

OfficeScan 10.6 Administrator's Guide - Trend Micro™ Online Help

OfficeScan 10.6 Administrator's Guide - Trend Micro™ Online Help

OfficeScan 10.6 Administrator's Guide - Trend Micro™ Online Help

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> Micro <strong>OfficeScan</strong> <strong>10.6</strong> Administrator’s <strong>Guide</strong><br />

5-20<br />

Updating an Isolated <strong>OfficeScan</strong> Server<br />

If the <strong>OfficeScan</strong> server belongs to a network that is isolated completely from all outside<br />

sources, you can keep the server’s components up-to-date by letting it update from an<br />

internal source that contains the latest components.<br />

This topic explains the tasks that you need to perform to update an isolated <strong>OfficeScan</strong><br />

server.<br />

To update an isolated <strong>OfficeScan</strong> server:<br />

Note: This procedure is provided for your reference. If you are able to fulfill all the tasks in<br />

this procedure, please ask your support provider for the detailed steps for each task.<br />

1. Identify the update source, such as <strong>Trend</strong> Micro Control Manager or a random host<br />

machine.<br />

The update source must have:<br />

• A reliable Internet connection so that it can download the latest components<br />

from the <strong>Trend</strong> Micro ActiveUpdate server. Without Internet connection, the<br />

only way for the update source to have the latest components is if you obtain<br />

the components yourself from <strong>Trend</strong> Micro and then copy them into the<br />

update source.<br />

• A functional connection with the <strong>OfficeScan</strong> server. Configure proxy settings if<br />

there is a proxy server between the <strong>OfficeScan</strong> server and the update source.<br />

For details, see Proxy for <strong>OfficeScan</strong> Server Updates on page 5-16.<br />

• Enough disk space for downloaded components<br />

2. Point the <strong>OfficeScan</strong> server to the new update source. For details, see <strong>OfficeScan</strong><br />

Server Update Sources on page 5-15.<br />

3. Identify the components that the server deploys to clients. For a list of deployable<br />

components, see <strong>OfficeScan</strong> Client Updates on page 5-24.<br />

Tip: One of the ways to determine if a component is being deployed to clients is by<br />

going to the Update Summary screen on the web console (Updates ><br />

Summary). In this screen, the update rate for a component that is being<br />

deployed will always be larger than 0%.

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

Saved successfully!

Ooh no, something went wrong!