McAfee ePolicy Orchestrator 4.
COPYRIGHT Copyright © 2007 McAfee, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of McAfee, Inc., or its suppliers or affiliate companies.
Contents Pre-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Server requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Installing in a cluster environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Setting up the ePolicy Orchestrator cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pre-Installation Review these requirements and recommendations before installing ePolicy Orchestrator 4.0. Contents System requirements Supported products and components System requirements Before you begin the installation, verify that each component meets the minimum system requirements that are listed in these topics.
Pre-Installation System requirements • Windows 2000 Advanced Server with Service Pack 4 or later. • Windows 2000 Server with Service Pack 4 or later. • Windows Server 2003 Enterprise with Service Pack 1 or later. • Windows Server 2003 Standard with Service Pack 1 or later. • Windows Server 2003 Web with Service Pack 1 or later. • Windows Server 2003 R2 Enterprise. • Windows Server 2003 R2 Standard. • Browser • Microsoft Internet Explorer 6.0 with Service Pack 1 or later. • Microsoft Internet Explorer 7.0.
Pre-Installation System requirements Database considerations Using ePO with a database A database must be installed before ePO can be installed. • Any of the following databases, if previously installed, meets this requirement. • SQL Server 2005 • MSDE 2000 • SQL 2000 • If none of those databases was previously installed, the ePO installation wizard detects that no database is present and offers you the opportunity to install SQL Server 2005 Express.
Pre-Installation System requirements Software Note SQL Server 2005 Express If no other database has been previously installed, this database can be installed automatically at user’s selection. Microsoft updates Update the ePolicy Orchestrator server and the database server with the most current updates and patches. MSI 3.1 The installation fails if using a version of MSI previous to MSI 3.1. NOTE: Using ePolicy Orchestrator 4.0 with MSDE 7 or SQL 7 is not supported.
Pre-Installation System requirements • Possible hosts: • HTTP-compliant servers on Microsoft Windows, Linux, or Novell NetWare operating systems. • Windows, Linux, or NetWare FTP servers. • Windows, Linux, or UNIX Samba UNC shares. • Computer with a SuperAgent installed on it. Agent and SuperAgent requirements Hardware and network requirements • Processor — Intel Pentium-class, Celeron, or compatible processor; 166MHz processor or higher. • Free disk space (agent) — 100MB.
Pre-Installation Supported products and components Windows Server 2003 Enterprise. Windows Server 2003 Standard. Windows Server 2003 Web. Windows XP Home with Service Pack 1. Windows XP Professional with Service Pack 1. Windows Vista (supported by ePO agent 3.6 only). NOTE: The disk space requirement for the distributed repositories on agents that are designated as SuperAgents is equal to the disk space available for the master repository.
Pre-Installation Supported products and components • McAfee GroupShield for Lotus Domino 7.0 • McAfee GroupShield for Exchange 6.0.2, 6.0.3 (with SpamKiller) • McAfee GroupShield for Exchange 7.0 • McAfee Host Intrusion Prevention 7.0 • McAfee Virex 7.7 • McAfee VirusScan for Mac 8.5, 8.6 • McAfee LinuxShield 1.3, 1.4, 1.5 • McAfee SiteAdvisor Enterprise 1.5 • Non-Windows Agent for Virex • Non-Windows Agent for LinuxShield McAfee ePolicy Orchestrator 4.
First-Time Installation This chapter provides instructions for installing ePolicy Orchestrator 4.0 in an environment where no previous version of ePolicy Orchestrator software has been installed. CAUTION: If you are upgrading from a prior version of ePolicy Orchestrator or are migrating from evaluation versions, see the Upgrading to ePolicy Orchestrator 4.0 chapter. Be sure that you have read, understood, and complied with the requirements and recommendations in the Pre-Installation chapter.
First-Time Installation Installing the server If you intend to use an existing instance of SQL Server 2005, MSDE 2000 or SQL 2000, you can reject the installation of SQL Server 2005 Express. If you do not have a supported version of SQL or MSDE, take one of the following actions: • Install a database. • Install SQL Server 2005 Express on the same computer where ePolicy Orchestrator is to be installed.
First-Time Installation Installing the server provide that information. Otherwise, the SQL server TCP port field shows the port and is disabled NOTE: If you are installing on a system with a local SQL 2005 database server, you must type the TCP port number on the Set Database Information page of the installation wizard. 14 Click Next. 15 Set the HTTP Configuration. Designate the port to be used by each function, then click Next. Function Port Agent-to-Server communication port Configurable.
First-Time Installation Migrating to a licensed version 19 In the Installation Complete dialog box, view the ReadMe file for the steps to start the software, then click Finish to complete the installation. NOTE: The installation procedure also installs the version of ePO agent that is appropriate to your operating system (version 3.6 or version 3.7). Migrating to a licensed version Use this task to migrate an evaluation version of the software to a licensed version.
Upgrading to ePolicy Orchestrator 4.0 Contents Unsupported products Backing up ePolicy Orchestrator databases Upgrading the server Migrating to a licensed version Unsupported products The following products are no longer supported in version 4.0 and are not migrated. AntiSpyware Enterprise 8.5 Standalone Outbreak Manager 4.6 Virex 8.0 Desktop Firewall 8.0, 8.5 PortalShield 1.0 VirusScan 4.x Dr. Ahn V3 Pro 2002 Deluxe Quarantine Manager VirusScan Enterprise 7.x Entercept 5.x NetShield 4.6.
Upgrading to ePolicy Orchestrator 4.0 Backing up ePolicy Orchestrator databases Backing up ePolicy Orchestrator databases Before you upgrade to version 4.0, back up all ePolicy Orchestrator databases: Microsoft SQL Server MSDE Microsoft SQL Server If you are using Microsoft SQL Server as the ePolicy Orchestrator database, see the Microsoft product documentation.
Upgrading to ePolicy Orchestrator 4.0 Upgrading the server C:\PROGRAM FILES\MCAFEE\EPOLICYORCHESTRATOR NOTE: The installation process may require you to restart the system. Task 1 Log on to the desired computer using an account with local administrator permissions. 2 If you are using Microsoft SQL Server 2000 as the ePolicy Orchestrator database, verify that the SQL Server 2000 service is running. For instructions, see the Microsoft product documentation. 3 Run SETUP.EXE.
Upgrading to ePolicy Orchestrator 4.0 Upgrading the server • If you select SQL authentication, provide the User name that ePolicy Orchestrator will use. Then provide a password. If the installer cannot identify the port used for communication to and from the server, you may be prompted to provide that information. Otherwise, the SQL server TCP port field shows the port and is disabled.
Upgrading to ePolicy Orchestrator 4.0 Migrating to a licensed version Selecting Setup email server settings now enables the remaining fields in the dialog box: • Email server FQDN: Type the Fully Qualified Domain Name of the mail server and specify the Port to use for email. • If appropriate, select This server requires authentication. Then type the User name and Password required to access the server. Click Next.
Post-Installation Tasks After completing the Setup wizard, follow the appropriate procedures to configure the software. Contents Completing a first-time installation Completing an upgrade Migrating events from an earlier version Checking in files manually Configuring the software for a server with multiple NICs Uninstalling the software Completing a first-time installation The tasks needed to complete the first-time installation are listed here.
Post-Installation Tasks Migrating events from an earlier version 3 Upgrade the agents on your network to version 3.6, if desired. 4 Check in and deploy new products you want to manage. For details, see the ePolicy Orchestrator 4.0 Product Guide. Migrating events from an earlier version Events recorded in earlier versions of ePolicy Orchestrator can be migrated to version 4.0. Task 1 From the ePolicy Orchestrator console, select Automation. 2 On the Server Tasks tab, click New Task.
Post-Installation Tasks Configuring the software for a server with multiple NICs Configuring the software for a server with multiple NICs When you install ePolicy Orchestrator on a server with multiple network interface cards (NICs), ensure that ePolicy Orchestrator is bound to the appropriate NIC. Task 1 Open the SEVER.INI file. The default location is: C:\PROGAM FILES\MCAFEE\EPOLICYORCHESTRATOR\4.0.0\DB 2 Add the following line at the end of the [server] section of the file: ServerIPAddress=XXX.XXX.
Troubleshooting The most common messages that appear during an installation and their solutions are listed in this chapter. If you are unable to resolve an issue using the information in this table, be sure to gather the following information before you contact McAfee Technical Support: • Verify that you have met the minimum installation requirements. • Review the ePolicy Orchestrator 4.0 Release Notes (ReadMe.html) for any known installation issues.
Troubleshooting Common installation messages and their solutions If this message appears... Then... the monitor resolution, see the Windows Help File. To open this file, click the Start button, then select Help. McAfee recommends that you install the software on a computer with at least 512 MB of RAM. The computer on which you are attempting to install the software does not meet the minimum memory requirement. McAfee ePolicy Orchestrator 4.
Troubleshooting Common installation messages and their solutions 26 If this message appears... Then... Unable to connect using the information you provided. Verify that you entered the correct information and try again. The user account that you specified could not be accessed. McAfee ePolicy Orchestrator 4.0 Installation Guide 1 Verify that the Domain, User Name, and Password you provided are typed correctly.
Troubleshooting Default locations of troubleshooting log files Default locations of troubleshooting log files Log File Name Log Type File Location Description EPO400-DBINIT.log Install %temp%\Nailogs Main DB log file for the ePolicy Orchestrator 4.0.0 installer. Contains any output captured by NaiLog.Dll during installation. EPO400-TRACE.LOG Install %temp%\Nailogs Main log file for the ePolicy Orchestrator 4.0.0 installer. licensing.
Troubleshooting Default locations of troubleshooting log files Log File Name Log Type File Location Description EPOServer, and Mod_EPO. 28 errorlog.####-##-##-##_##_## Apache [InstallDir]\Apache2\logs Apache2 log file for the Apache service. Present only after initial service startup. jakarta_service_########.log Tomcat [InstallDir]\Server\logs Tomcat log file for the Tomcat service. Present only after initial service startup. localhost_access_log.####-##-##.
Installing in a cluster environment The ePolicy Orchestrator software provides high availability for server clusters with Microsoft Cluster Server (MSCS) software. Contents Requirements Setting up the ePolicy Orchestrator cluster Testing the ePolicy Orchestrator cluster Requirements Before Running ePolicy Orchestrator as a clustered application, ensure that: • Microsoft Cluster Server (MSCS) is set up and running on a cluster of two or more servers.
Installing in a cluster environment Setting up the ePolicy Orchestrator cluster Creating the Generic Service resources Installing ePolicy Orchestrator on each node Run the ePolicy Orchestrator setup on each of the nodes. McAfee strongly recommends that, during installation, only one node at a time be powered on. Task 1 Double-click SETUP.EXE in the installation folder.
Installing in a cluster environment Setting up the ePolicy Orchestrator cluster 3 Select Physical Disk from the Resource type drop-down list. 4 Ensure that ePO is the selected group, then click Next. 5 In the Possible Owners dialog box, identify the owners of the resource. Select the desired node, then click Add. Repeat until all owners are added, then click Next. 6 In the Dependencies dialog box, click Next. 7 In the Disk pull-down, select the disk and click Finish.
Installing in a cluster environment Testing the ePolicy Orchestrator cluster 3 Type the Name and Description of the resource. For example, ePO 4.0 Server. 4 Select Generic Service from the Resource type drop-down list. 5 Ensure ePO is the selected group, then click Next. 6 In the Possible Owners dialog box, identify the owners of the resource. Select the desired node, then click Add. Repeat until all owners are added, then click Next.
