Setting Up A Lab Environment - McAfee EPOLICY ORCHESTRATOR 3.6 - WALKTHROUGH GUIDE Manual

®
ePolicy Orchestrator 3.6 Walkthrough Guide

Setting up a lab environment

What is covered and what is not covered
This section of the guide does not cover everything that ePolicy Orchestrator can do,
for example, many advanced features and installation scenarios typical in real-world
deployments. For your live deployment, you can follow many of these basic steps, but
you may need more information. For complete information on all aspects of the
product, refer to the ePolicy Orchestrator 3.6 Product Guide.
What is covered What is not covered
Setting up a single Setting up multiple ePolicy
ePolicy Orchestrator Orchestrator servers and
server and console. remote consoles.
Running MSDE Running SQL Server
database on the same databases or remote
server as ePolicy database servers.
Orchestrator.
Using ePolicy Using login scripts or
Orchestrator to deploy third-party tools to deploy
agents and VirusScan agents and VirusScan
Enterprise. Enterprise.
Setting up a simple Setting up UNIX, Linux, or
network environment NetWare environments
with NT domains and
Active Directory.
Before you install and test ePolicy Orchestrator, you must first create a safe test
network. Planning and testing a live deployment is an involved process, especially in a
large organization. However, you can create a small test environment in a matter of
hours, and if you identify existing systems in your network for testing, the process
takes even less time.
A test environment should contain:
One server system to host the ePolicy Orchestrator server.
One or more client systems (servers or workstations) to which you deploy agents
and VirusScan Enterprise 8.0i.
See the ePolicy Orchestrator 3.6 Installation Guide and VirusScan Enterprise 8.0i
Installation Guide for complete software and hardware requirements for the ePolicy
Orchestrator server, the agent, and VirusScan Enterprise 8.0i.
Note
Configure your network?
Before setting up your test environment, ensure your network is correctly configured
for ePolicy Orchestrator:
1 Create trusted domain connections to any remote NT domains.
To deploy the agent to systems outside the local NT domain (where the ePolicy
Orchestrator server resides), you must create a trusted connection between the
domains. This connection is required for the server to deploy agents and install
software on remote systems. See your Microsoft Windows documentation for
instructions. You must also have a user account with administrator rights in the
remote domain.
Comments
In a small test environment, one
server is enough.
Using the MSDE database packaged
with ePolicy Orchestrator is simpler
for testing in a small lab network.
Manually installing the agent is also
covered.
These examples use NT domains and
Active Directory to illustrate key
product features.
79
8
Installing and setting up