McAfee EPOLICY ORCHESTRATOR 4.5 - Guía de instalación Pagina 20

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 110
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 19
Overview of repository types
There are several types of repositories you can use in your managed environment.
The ePolicy Orchestrator server always acts as the Master Repository. It keeps the master copy of all
the content needed by your agents. The server replicates content to each of the repositories
distributed throughout your environment. As a result, your agents can retrieve updated content from
an alternate and closer source.
Your ePolicy Orchestrator server requires does not require configuration
to make it the Master Repository. It is the Master Repository by default.
Repository types include:
FTP repositories
HTTP repositories
UNC share repositories
SuperAgents
Keep the following considerations in mind when planning your distributed repositories:
The McAfee ePO server requires certain protocols be used for the repositories, but any server
vendor can provide those protocols. For example, if you use an HTTP repository you can use either
Microsoft Internet Information Services (IIS) or Apache server (Apache is the faster option).
There is no operating system requirement for the systems that host your repository. As long as
your ePolicy Orchestrator server can access the folders you specify to copy its content to, and as
long as the agents can connect to the folder to download their updates, everything works as expected
Your agent updates and ePO replication tasks are only as good as your repositories. If you are
already using one of these repositories and your environment works well, then do not change the
configuration.
If you are starting with a new installation, with no repositories, use a
SuperAgent because they are easy to configure and reliable.
FTP repositories
You can use an FTP server to host a distributed McAfee ePO server repository. You might already have
FTP servers in your environment and you can allow McAfee content to reside there as well.
FTP repositories are:
Generally fast
Can manage extensive load from the clients pulling data
Helpful in a DMZ where HTTP may not be optimal and UNC shares can't be used
Using FTP servers your clients do not need authentication and can use anonymous logon to pull their
content. No authentication reduces the chance a client might fail to pull its content.
HTTP repositories
You can use an HTTP server to host a distributed McAfee ePO server repository. You might already
have HTTP servers in your environment placed in the proper regional locations.
HTTP servers can be very fast serving out files to large environments. An HTTP server like Apache is a
good example. Your HTTP servers allow clients to pull their content without authentication. No
authentication reduces the chance a client might fail to pull its content.
3
Using distributed repositories to keep your security software up to date
Overview of repository types
20
McAfee
®
ePolicy Orchestrator
®
Best Practices Guide for use with ePolicy Orchestrator versions 4.5.0 and 4.0.0
Vista de pagina 19
1 2 ... 15 16 17 18 19 20 21 22 23 24 25 ... 109 110

Comentarios a estos manuales

Sin comentarios