McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual page 17

System protection, a product overview and quick set up in a test environment version 3.6
Table of Contents

Advertisement

®
ePolicy Orchestrator
3.6 Walkthrough Guide
If you are going to use a database other than the MSDE 2000 provided with ePolicy
Orchestrator, you should install the database software before installing ePolicy
Orchestrator.
If you are planning on managing more than 2,000 systems, use a dedicated server
with Microsoft SQL Server 2000 with Service Pack 3 for the database.
Ports you want to use
As ePolicy Orchestrator runs, there is considerable communication between the server
and the other components. During the installation wizard, you must designate the ports
that the server uses for this communication. Although defaults are provided, we
recommend that you consider strongly the ports that you will assign to the different
types of communication.
Once ePolicy Orchestrator is installed, you cannot change some of these assignments
through the ePolicy Orchestrator console without uninstalling the software.
Make sure that the ports you assign are not already assigned to other products.
Agent-to-Server communication port
communicate with the server. The default port is
after installation.
McAfee strongly recommends that you change this to another port due to potential
conflicts in many environments. For example, to
Note
Console-to-Server communication port
communicate with the server. The default port is
installation.
McAfee strongly recommends that you change this to another port due to potential
conflicts in some environments. For example, to
Note
installation.
Agent Wake-Up communication port
wakeup calls. The default port is
Agent Broadcast communication port
SuperAgent wakeup calls. The default port is
installation.
Event Parser-to-Server communication port
System Detection and ePolicy Orchestrator Notifications for non-SSL user interface
communication and non-SSL sensor communication. The default port is
port cannot be changed after installation.
Console-to-Application Server communication port
Rogue System Detection and ePolicy Orchestrator Notifications for SSL user
interface communication and SSL sensor communication. The default port is
This port cannot be changed after installation.
Sensor-to-Server communication port
Detection sensor to report host-detected messages to the Rogue System Detection
server using SSL. The default port is
installation.
— This is the port the agent uses to
80
. This port cannot be changed
82
.
— This is the port the console uses to
81
. This port can be changed after
83
. This port cannot be changed after
— This is the port used to send agent
8081
. This port can be changed after installation.
— This is the port used to send
8082
. This port can be changed after
— This is the port used by Rogue
— This is the port used by
— The port used by the Rogue System
8444
. This port cannot be changed after
14
Installing or Upgrading the Server
Installing for the first time
8080
. This
8443
.
2

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Epolicy orchestrator

Table of Contents