McAfee EPOLICY ORCHESTRATOR 4.5 - Przewodnik Instalacji Strona 31

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 110
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 30
About Global Updating
Global Updating is a powerful feature, but if it is used incorrectly it can have a negative impact in your
environment.
Global Updating is used to update your repositories as quickly as possible whenever the master
repository changes. This is great if you have a smaller environment (fewer than 3,000 nodes) with no
WAN links. But Global Updates generate a lot of traffic that could impact your network bandwidth. If
your environment is on a LAN and bandwidth is not a concern then go ahead and use Global Updating.
If you are managing a larger environment and bandwidth is critical then disable Global Updating.
Global Updating is disabled by default when you install ePolicy
Orchestrator software version 4.5
To confirm the Global Updating setting, click Menu | Configuration |
Server Settings and select Global Updating from the Setting Categories
list. Confirm Status is disabled. If not, click Edit and change the
status.
How Global Updates works
If your ePolicy Orchestrator server is scheduled to pull the latest DATs from the McAfee website at 2
p.m. Eastern time (and the scheduled pull changes the contents of your Master Repository), your
server automatically initiates the Global Update process to replicate the new content to all your
distributed repositories.
The Global Updates process follows this sequence of events:
1
Content or packages are checked in to the Master Repository.
2
The ePolicy Orchestrator server performs an incremental replication to all distributed repositories.
3
The ePolicy Orchestrator server issues a SuperAgent wake-up call to all SuperAgents in the
environment.
4
The SuperAgent broadcasts a global update message to all agents within the SuperAgent subnet.
5
Upon receipt of the broadcast, the agent is supplied with a minimum catalog version needed.
6
The agent searches the distributed repositories for a site that has this minimum catalog version.
7
Once a suitable repository is found, the agent runs the update task.
A common mistake users make with a large environment and where bandwidth is critical is thinking
they should have Global Updating enabled to make sure they receive their DATs quickly. These users
enable Global Updates and everything works fine. But, eventually McAfee releases an update to its
VirusScan Enterprise engine which can be several megabytes compared to the 200 Kb DAT files.
Engine updates typically occurs twice per year. McAfee posts the new engine to the public site and the
McAfee ePO server pulls it down and starts replicating it to the distributed repositories and starts
waking up agents to receive the new engine immediately. This can saturate your WAN links and roll
out an engine that you would preferred to upgrade in a staged release.
Using distributed repositories to keep your security software up to date
About Global Updating
3
McAfee
®
ePolicy Orchestrator
®
Best Practices Guide for use with ePolicy Orchestrator versions 4.5.0 and 4.0.0
31
Przeglądanie stron 30
1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 109 110

Komentarze do niniejszej Instrukcji

Brak uwag