Installation guide

Installation Guide 37
Pre-Installation Procedures
How AutoUpdate 7.0 information is converted
If you are currently using ePolicy Orchestrator 2.5 or 2.5.1 to manage McAfee
Security products that use AutoUpdate 7.0 (for example, McAfee VirusScan
Enterprise 7.0), you can — as part of the installation — keep the
McAfee AutoUpdate
7.0
policies and tasks for use with the agent 2.5 or 2.5.1 and convert them to ePolicy
Orchestrator Agent
policies and tasks for use with the agent 3.1.
WARNING
If you don’t migrate the McAfee AutoUpdate 7.0 policies and
tasks, they are no longer enforced on client computers.
Regardless of whether you choose to migrate these policies
and tasks during the installation, the
McAfee AutoUpdate 7.0
policy page is removed and cannot be added back to the
Repository in version 3.0.
Although you cannot view or change the
McAfee AutoUpdate 7.0 policies and tasks
after the installation, they continue to be enforced on the agent 2.5 and 2.5.1. Their
settings remain in the ePolicy Orchestrator database and continue to be exchanged
during agent-to-server communication. You can remove these settings from the
database after you upgrade all agents to version 3.1, or when you no longer want
to enforce these policies and tasks on the agent 2.5 or 2.5.1.
How AutoUpdate 7.0 information in ePolicy Orchestrator 2.5 or 2.5.1 is converted
in version 3.0 is described below:
In version 2.5 or 2.5.1, this... Is converted to this...
Repositories. Hidden repositories. Although these repositories
no longer appear, client computers using the
agent 2.5 or 2.5.1 continue to retrieve updates
from these repositories.
These repositories are also converted to local
distributed repositories. Client computers using
the agent 3.1 retrieve updates from these
repositories.
NAIFtp and NAIHttp default
repositories.
Although these are converted to local distributed
repositories, we recommend that you remove
them after the installation as they are now used as
the default fallback and source repositories,
respectively.
Proxy server settings. Proxy server settings are converted and applied to
client computers.
You must define the proxy server settings for the
master repository separately.