Pre-Installation System requirements
Windows Server 2003 R2 Standard with Service Pack 2 or later Windows Server 2008 NOTE: Installation is blocked if you attempt to install on a version of Windows earlier than Server 2003. In addition, ePolicy Orchestrator stops functioning if, after having been installed on Windows Server 2003, the server is upgraded to Windows Server 2008. Browser Firefox 3.0 Microsoft Internet Explorer 7.0 or 8.0 If using Internet Explorer and a proxy, follow these steps to bypass the proxy server. From the Tools menu in Internet Explorer, select Internet Options. Select the Connections tab and click LAN Settings. Select Use a proxy server for your LAN, then select Bypass proxy server for local addresses. Click OK as needed to close Internet Options.
Domain controllers The server must have a trust relationship with the Primary Domain Controller (PDC) on the network. For instructions, see the Microsoft product documentation. Security software Install and/or update the anti-virus software on the ePolicy Orchestrator server and scan for viruses. CAUTION: If running VirusScan Enterprise 8.5i or 8.7i on the system where you are installing ePolicy Orchestrator, you must ensure that the VSE Access Protection rules are disabled during the installation process, or the installation fails. Install and/or update firewall software on the ePolicy Orchestrator server. Ports McAfee recommends avoiding the use of Port 8443 for HTTPS communication. Although this is the default port, it is also the primary port used by many web-based activities, is a popular target for malicious exploitation, and it is likely to be disabled by the system administrator in response to a security violation or outbreak. NOTE: Ensure that the ports you choose are not already in use on the ePolicy Orchestrator server computer. Notify the network staff of the ports you intend to use for HTTP and HTTPS communication via ePolicy Orchestrator. NOTE: Installing the software on a Primary Domain Controller (PDC) is supported, but not recommended. Supported virtual infrastructure software VMware ESX 3.5.x Microsoft Virtual Server 2005 R2 with Service Pack 1 Windows Server 2008 Hyper-V

Database requirements

Microsoft updates and patches Update both the ePO server and the database server with the latest Microsoft security updates. If you are upgrading from MSDE 2000 or SQL 2000, be sure to follow Microsoft's required upgrade scenarios. Databases supported for use with ePolicy Orchestrator SQL Server 2005 Express. This database is included with ePolicy Orchestrator for use in environments where there is no supported database available. SQL Server 2005. SQL Server 2008 Express. SQL Server 2008. NOTE: Use of ePolicy Orchestrator with MSDE 2000 or SQL 2000 (or earlier) is not supported. Database installation documented in this Guide The only database installation scenario described in detail is a first-time installation of SQL Server 2005 Express. In this scenario, the ePOSetup installs both the ePolicy Orchestrator software and the database on the same server. If the database is to be installed on a different server from the ePolicy Orchestrator software, manual installation is required on the remote servers. Other relevant database installations and upgrades See the documentation provided by the database manufacturer for information about the following installation scenarios: Installing SQL Server 2005. Installing SQL Server 2008. Upgrading from MSDE 2000. Upgrading from SQL 2000. Upgrading from SQL 2005. Upgrading from SQL 2005 Express. Maintenance settings McAfee recommends making specific maintenance settings to ePO databases. For instructions, see Maintaining ePO databases in the ePolicy Orchestrator Help. SQL Server Dedicated server and network connection Use a dedicated server and network connection if managing more than 5,000 client computers. Local database server If using SQL Server on the same system as the ePOserver, McAfee recommends using a fixed memory size in Enterprise Manager that is approximately two-thirds of the total memory for SQL Server. For example, if the computer has 1GB of RAM set 660MB as the fixed memory size for SQL Server.

SQL Server licenses If using SQL Server, a SQL Server license is required for each processor on the computer where SQL Server is installed. CAUTION: If the minimum number of SQL Server licenses is not available after you install the SQL Server software, you may have issues installing or starting the ePolicy Orchestrator software.

Database considerations

Using ePolicy Orchestrator with a database A database must be installed before ePolicy Orchestrator can be installed. Any of the following databases, if previously installed, meets this requirement. SQL Server 2005 SQL 2005 Express SQL 2008 SQL 2008 Express NOTE: SQL 2000 is not supported. 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. The following tables provide additional information about the database choices and other software requirements.
Database Requirements Note Needed if managing more than 5,000 computers.
SQL Server 2005 Dedicated server and network or SQL Server connection 2008 Local database server
If the database and ePO server are on the same system, McAfee recommends using a fixed memory size in Enterprise Manager or SQL Server Management Studio that is approximately two-thirds of the total memory for SQL Server. For example, if the computer has 1 GB of RAM, set 660 MB as the fixed memory size for SQL Server. A license is required for each processor on the computer where SQL Server is installed. If the minimum number of SQL Server licenses is not available, you might have difficulty installing or starting the ePolicy Orchestrator software. You must acquire and install.

Licenses

SQL Server 2005.NET Framework Express Software MSXML 6.0 Note
You must acquire and install. 1
From the Internet Explorer Tools menu, select Windows Update. Click Custom, then select Software. Select MSXML6.
Select Review and install updates, then click Install Updates.
Software Internet Explorer 7 or 8, or Firefox 3.0.NET Framework 2.0 Microsoft Visual C++ Redistributable Microsoft Visual C++ Redistributable - x86 9.0.21022 MDAC 2.8 SQL Server 2005 Backward Compatibility SQL Server 2005 Express
Note You must acquire and install.
You must acquire and install if using SQL Server 2005 Express. If not previously installed, the installation wizard installs automatically.
If not previously installed, the installation wizard installs automatically.
If not previously installed, the installation wizard installs automatically. If not previously installed, the installation wizard installs automatically.
If no other database has been previously installed, this database can be installed automatically at users selection. Update the ePolicy Orchestrator server and the database server with the most current updates and patches. The installation fails if using a version of MSI previous to MSI 3.1.

Microsoft updates

MSI 3.1
Database installation documented in this guide The only database installation scenario described in detail is a first-time installation of SQL Server 2005 Express. In this scenario, the ePolicy Orchestrator Setup installs both the ePolicy Orchestrator software and the database on the same server. If the database is to be installed on a different server from the ePolicy Orchestrator software, manual installation of SQL is required on the remote server. Other relevant database installations and upgrades See the documentation provided by the database manufacturer for information about the following installation scenarios: Installing SQL Server 2005 or 2008. Upgrading from MSDE 2000 to SQL Server 2005 or 2008. Upgrading from MSDE 2000 to SQL Server 2005 Express. Nested triggers The SQL Server Nested Triggers option must be enabled. Database collation The only database collation supported by ePolicy Orchestrator is the U.S. English default: SQL_Latin1_General_Cp1_CI_AS. Maintenance settings McAfee recommends making specific maintenance settings to ePolicy Orchestrator databases. For instructions, see Maintaining ePolicy Orchestrator databases in the ePolicy Orchestrator 4.5 Help. SQL Server Dedicated server and network connection Use a dedicated server and network connection if managing more than 5,000 client computers. Local database server If using SQL Server on the same system as the ePolicy Orchestrator server, McAfee recommends using a fixed memory size in Enterprise Manager that is approximately two-thirds of the total memory for SQL Server. For example, if the computer has 1 GB of RAM, set 660 MB as the fixed memory size for SQL Server.
Pre-Installation Supported products and components
SQL Server licenses If using SQL Server, a SQL Server license is required for each processor on the computer where SQL Server is installed. CAUTION: If the minimum number of SQL Server licenses is not available after you install the SQL Server software, you might have issues installing or starting the ePolicy Orchestrator software.

Distributed repositories

Free disk space 400 MB on the drive where the repository is stored. 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. Memory 256 MB minimum. 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
Supported products and components
McAfee Agent 4.0 for Email and Web Security McAfee Agent 4.0 for HP-UX McAfee Agent 4.0 for Linux McAfee Agent 4.0 for Macintosh McAfee Agent 4.0 for Solaris McAfee Agent 4.5 McAfee Agent for Windows Patch 1 and Patch 2 McAfee Common Management Agent 3.7 Patch 1 McAfee Common Management Agent MA 3.6 Patch 4 McAfee Data Loss Prevention 2.1 Patch 2 McAfee Data Loss Prevention 2.2 McAfee Data Loss Prevention 3.0 McAfee Email and Web Security 5.1 Appliance McAfee Endpoint Encryption 5.2.1 McAfee Endpoint Encryption 5.3 McAfee Endpoint Encryption Files/Folders 3.1 (EEFF) McAfee Endpoint Encryption Files/Folders 4.x (EEFF) McAfee EndPoint Encryption for Mobile 3.0 (EEMO) McAfee Foundstone 6.5.3 McAfee GroupShield for Domino 7.0 McAfee GroupShield for Exchange 6.0.2 with SKE
Pre-Installation Operating systems language support
McAfee GroupShield for Exchange 7.0 McAfee GroupShield for Exchange 7.0 SP 1 McAfee Host Intrusion Prevention 6.1 Patch 3 McAfee Host Intrusion Prevention 7.0 Patch 3 McAfee Host Intrusion Prevention 7.1 McAfee IntruShield 4.1 McAfee IntruShield 5.1 McAfee LinuxShield 1.5.1 McAfee Network Access Control 3.1 McAfee Policy Auditor 5.1 (Feyman) McAfee PortalShield 2.0 Patch 1 McAfee Quarantine Manager 6.0 McAfee Rogue System Detection 2.0 Patch 2 McAfee Security for Lotus Domino Linux 7.5 McAfee Security for Macintosh v1.0 McAfee SiteAdvisor Enterprise 1.6 McAfee SiteAdvisor Enterprise 2.0+ McAfee SiteAdvisor Enterprise 3.0 McAfee VirusScan 8.5i with McAfee AntiSpyware Enterprise McAfee VirusScan 8.7 with McAfee AntiSpyware Enterprise McAfee VirusScan Advanced Server (NetApp) McAfee VirusScan Advanced Server (SAP) McAfee VirusScan Advanced Server (Virtualization) McAfee VirusScan for Macintosh 8.6.1 Symantec SAV 10.x Symantec SAV 9.x USB Device 1.0 (EEV) Vdisk 4.1 (EEV) vDisk for Macintosh 1.0
Operating systems language support

This version of the ePolicy Orchestrator software runs on any supported operating system irrespective of the language of the operating system. Following is a list of languages into which the ePolicy Orchestrator has been translated. When the software is installed on an operating system using a language that is not on this list, the ePolicy Orchestrator interface attempts to display in English. Chinese (Simplified) Chinese (Traditional) English Japanese Korean Russian
French (Standard) German (Standard)

Spanish

First-Time Installation
This chapter provides instructions for installing ePolicy Orchestrator 4.5 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 an evaluation version, see Upgrading to ePolicy Orchestrator 4.5. Be sure that you have read, understood, and complied with the requirements and recommendations in Pre-Installation. Contents Installing the server Installing an Agent Handler

Installing the server

The installation depends, in part, upon the presence of MSXML 6.0 on the server. If it is not present, an error message appears during the installation, advising you that it must be installed before proceeding. To avoid the inconvenience of interfering with the installation in order to download and install MSXML, we strongly recommend that you obtain and install MSXML before starting the installation. We also recommend that you monitor the entire installation process. It might require you to restart the system. Use this task to install the ePolicy Orchestrator server. Task Using an account with local administrator permissions, log on to the Windows server computer to be used as the ePO server. Run the Setup program. From the product CD: select a language in the ePolicy Orchestrator autorun window, then select Install ePolicy Orchestrator 4.5. From software downloaded from the McAfee website: go to the location containing the extracted files and double-click Setup.exe. The executable is located in the file EPO 4.5.0 <build and package numbers>.zip. Be certain to extract the contents of the zip file to a temporary location. Do not attempt to run Setup.exe without first extracting the contents of the zip file. NOTE: If any prerequisite software is missing from the installation target computer, a list of those items appears. 3 Click Next. The installation process for each software item not listed as Optional begins automatically.

Click Next to display the HTTP Configuration dialog box. The values that were set during the original installation cannot be changed here.
Configurable port used by the Rogue System Sensor to report host-detected messages to the Rogue System Detection server using SSL. Port 8801. Nonconfigurable port used by McAfee Avert to provide information on security threats and the required DAT and engine versions to protect against them
Upgrading to ePolicy Orchestrator 4.5 Upgrading the ePO server from version 4.0
Function SQL server TCP port
Port Port 1433. Nonconfigurable unless connection has failed. It then becomes configurable. See SQL documentation for additional information about configuring this port.
Click Next. In the Default Notification Email Address dialog box, type the email address for the recipient of messages from ePolicy Orchestrator Notifications, or leave the default. For a new recipient, complete these options, then click Next. a Provide a default destination for messages. b Select Setup email server settings now. If you choose Setup email server settings later, leave the default address. c Type the Fully Qualified Domain Name (FQDN) of the mail server and specify the Port to use for email. d Select This server requires authentication if needed, then type the User name and Password required to access the server. For more information, see Automatic Responses in the ePolicy Orchestrator 4.5 Product Guide.
10 In the Start Copying Files dialog box, click Install. 11 In the Installation Complete dialog box, click Finish to complete the installation.
Upgrading the ePO server from version 4.0
This task upgrades the ePO server from ePolicy Orchestrator version 4.0 Patch 3 or later to version 4.5. McAfee recommends that you monitor the upgrade process. It might require you to restart the system. The default location of ePolicy Orchestrator version 4.0 is: C:\Program Files\McAfee\ePolicy Orchestrator Before you begin You must install the SQL 2005 Backwards Compatibility package before upgrading an ePolicy Orchestrator installation if you are using a remote database server or a local SQL 2005 server that does not already have it installed. Task 3 Log on to the desired system using an account with local administrator permissions. If you are using Microsoft SQL Server 2005 or 2008, verify that it is running. Run the Setup program. From the product CD: select a language in the ePolicy Orchestrator autorun window, then select Install ePolicy Orchestrator 4.5. From software downloaded from the McAfee website: go to the location containing the extracted files and double-click Setup.exe. NOTE: If any prerequisite software is missing from the installation target computer, a list of those items appears. Click Next. The installation process for each software item not listed as Optional begins automatically. For Optional items, a dialog box appears, where you can allow installation or reject it.

In the Welcome window of the installation wizard, click Next. A warning message lists which products are no longer supported with this version of the software. These products are not migrated to the ePolicy Orchestrator 4.5 Repository. In the Set Administrator Information dialog box, type and verify the user name and password of the global administrator for the current ePO server, then click Next. For security reasons, ePolicy Orchestrator does not allow accounts with blank passwords. In the Start Copying Files dialog box, click Next to begin the installation. In the Installation Complete dialog box, click Finish to complete the installation.

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 version 3.6.1 Files to check in manually Configuring the software for a server with multiple NICs Uninstalling the software
Completing a first-time installation
The tasks needed to complete a first-time installation are listed here. For details about performing these tasks, see the ePolicy Orchestrator 4.5 Product Guide. Tasks 7 Plan your ePolicy Orchestrator System Tree and updating scheme. Create the ePolicy Orchestrator System Tree. Distribute the McAfee Agent to the systems you want to manage with ePolicy Orchestrator. Create the updating repositories. Check in to the repositories the products ePolicy Orchestrator is to manage. Then configure their policy settings. Deploy products to the managed computers. Configure the advanced features of ePolicy Orchestrator.

Completing an upgrade

Perform the following tasks to complete an upgrade. Tasks Migrate events from the previous version of ePolicy Orchestrator. See Migrating events from version 3.6.1 in this guide. Plan and implement any changes you want to make to the ePolicy Orchestrator System Tree (formerly Directory) and Repository.
Post-Installation Tasks Migrating events from version 3.6.1
Check in and deploy new products you want to manage. For details, see the ePolicy Orchestrator 4.5 Product Guide.
Migrating events from version 3.6.1
Use this task to migrate events recorded in version 3.6.1 of ePolicy Orchestrator to version 4.5. It is not necessary to migrate events from version 4.0 to version 4.5. Task Click Menu | Automation | Server Tasks. Select the Edit link in the Actions column for the row labeled Event Migration (3.6x->4.x). On the Description tab, type a name for the task and any notes you want; select Enabled, then click Next. On the Actions tab, ensure that Event Migration is selected from the drop-down Actions list. From the list of DTS (Data Transformation Services) packages, select the packages that you want to migrate. To run the migration immediately, click Finish, then click Run in the Actions field. To schedule the migration to run at a future time, click Next. To implement the continuous migrating of events until conclusion, make the following settings on the Schedule page: a Select Daily. b Specify a Start date and make the End date the same. c Select a time of day. d Click Next.

Files to check in manually
These are the files that you must check in to the master repository after you install or upgrade the software. For more information, see the ePolicy Orchestrator 4.5 Product Guide. Custom packages Only managed product packages that were created with McAfee Installation Designer 8.0 or later can be checked in to the master repository. Product extensions If the extension for a managed product was not added to the repository during the installation, you must manually add it as a zip file. Product plug-in files Any product plug-in (.dll) files that were not checked in as part of the installation must be checked in to the master repository manually as zip files. Products Check the software you intend to deploy into the repository. If you are installing ePolicy Orchestrator for the first time, you must check in all products that you want to deploy via ePolicy Orchestrator. If you are upgrading ePolicy Orchestrator, any supported products that were not already present must be checked in to the master repository manually as zip files. Product updates You must check in all product updates that you want to deploy via ePolicy Orchestrator.
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. There are three approaches to achieving this, depending on the number of IP addresses you want to expose for agent-server communication. Task Open the server.ini file. The default location is: C:\Program Files\McAfee\ePolicy Orchestrator\DB Modify the [server] section of the file by adding the following line:
Server=<IP address of the server you want ePolicy Orchestrator to use>
Follow the procedure that corresponds to the number of IP address you want to expose: a To expose a single IP address: modify the server.ini file, and insert the IP address you want to expose. b To expose all IP addresses: modify the server.ini file, and insert the FQDN of the ePO server. c To expose some IP addresses: modify the server.ini file, and insert an IP address you want to expose. Then, set up a new virtual Agent Handler group to define additional IP addresses you want to expose for agent-server communication. See the ePolicy Orchestrator Product Guide for additional information. NOTE: The server IP addresses are used for agent access to the master repository and for agent-server communication. If these addresses are not provided, the IP address of the first listed NIC is used. Save and close the server.ini file. Restart all ePO services.
Uninstalling the software
If you need to uninstall ePolicy Orchestrator software, use this procedure. If you used the ePO Setup program to install SQL 2005 Express, you can remove the database when you remove ePolicy Orchestrator. Before you begin You must uninstall any Agent Handlers registered to this ePO server before you uninstall the ePolicy Orchestrator. Task Close all database management software. Open the Control Panel and select Add/Remove Programs. Select McAfee ePolicy Orchestrator, then click Remove. The Remove McAfee ePolicy Orchestrator dialog box appears. Select Also remove the ePolicy Orchestrator database.

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. 1 Verify that the Domain, User Name, and Password you provided are typed correctly.
Then. 2 Verify that the account you used to log on to this computer has access to this domain.
Troubleshooting Default locations of troubleshooting log files
Default locations of troubleshooting log files
Log File Name AHSetupDLL.log Log Type Temporary File Location %temp% on the Agent Handler server %temp%\mfelogs Description Logs Agent Handler backend events Main log file for the ePolicy Orchestrator 4.5.0 installer. File created by ePolicy Orchestrator installer, containing the command (sent to Remote-Client) to check in extensions. Log of migration errors. List of extensions that have failed to check in. Log file created when the ePolicy Orchestrator installer calls the Orion ANT installer. Log file created when the ePolicy Orchestrator installer calls the Mercury ANT installer. Application Server log file. Present only after initial service startup. Output = RManJNI, DalPolicy, SiteMgr, and SiteMgrWrap. Event Parser log file. Present only after initial service startup. Output = EventParser. ePolicy Orchestrator Server Agent Handler and other C++ code log file. Present only after initial service startup. Output = EPOServer, and Mod_EPO. Apache2 log file for the Apache service. Present only after initial service startup. Tomcat log file for the Tomcat service. Present only after initial service startup. Tomcat log file for the Tomcat service. Present only after initial service startup. Log file used by the McAfee Foundation Services platform and, by default, all loaded extensions. Present only after initial service startup. Tomcat log file for the

EPO450-Install-MSI.LOG

Install

[ExtensionFileName].cmd

Temporary
%temp%\MFElogs\ePO4 50-troubleshoot\ OutputFiles
dbmExecute.log EPO450-Checking-Failure.log

Temporary Temporary

%temp%MFElogs %temp%MFElogs

core-install.log

[InstallDir]\Installer\core

epo-install.log

[InstallDir]\Installer\ePO

EpoApSvr.log

Primary

[InstallDir]\DB\Logs

eventparser.log

server.log

errorlog.####-##-##-##_##_## Apache
[InstallDir]\Apache2\logs
jakarta_service_########.log

Tomcat

Creating the Network Name resource
Use this task to create a Network Name resource. Task In the Cluster Administrator, right-click the ePO group, then select New | Resource. The New Resource dialog box appears. Type the Name and Description of the resource, for example, ePO Server Name. From the Resource type drop-down list, select Network Name. Ensure that ePO is the selected group, then click Next.
In the Possible Owners dialog box, identify the owners of the resource. Select the desired node, then click Add. Repeat until all owners have been added, then click Next. In the Dependencies dialog box, select IP Address, then click Next. Provide the virtual server name for the ePO group, then click Finish.
Creating the Generic Service resources
Use this task to create the Generic Service resources. Task 1 Add Generic Service resources in the following order: a McAfee ePolicy Orchestrator 4.5.0 Server b McAfee ePolicy Orchestrator 4.5.0 Application Server (Dependency on Server) c McAfee ePolicy Orchestrator 4.5.0 Event Parser (Dependency on Application Server) In the Cluster Administrator, right-click the ePO group, then select New | Resource. The New Resource dialog box appears. Type the Name and Description of the resource, for example, ePO 4.5 Server. From the Resource type drop-down list, select Generic Service. Ensure ePO is the selected group, then click Next. 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. In the Dependencies dialog box, type the dependency specific to each service.
Service ePolicy Orchestrator 4.5.0 Application Server ePolicy Orchestrator 4.5.0 Event Parser Dependancy ePolicy Orchestrator 4.5.0 Server ePolicy Orchestrator 4.5.0 Application Server
For each service, type the Service Name, leave the Start Parameters field blank, then click Finish.
Service Server Application Server Event Parser Service Name MCAFEEAPACHESRV MCAFEETOMCATSRV200 MCAFEEEVENTPARSERSRV
Testing the ePolicy Orchestrator cluster
When the ePolicy Orchestrator cluster is set up and online, use this task to ensure that ePolicy Orchestrator functions in a failover situation. Task Restart the system functioning as the active node. The passive node automatically becomes the active node and you are automatically logged-out. When ePolicy Orchestrator then prompts you to log in, you can conclude that it has continued to function during the failover.

Installing in a Cluster Environment Windows server 2008
Uninstalling ePolicy Orchestrator
Use this task to remove ePolicy Orchestrator from a system running as a cluster node. Task 1 Open the Cluster Administrator on the active node: Start | Program Files | Administrative Tools | Cluster Administrator 2 In the ePolicy Orchestrator Group, right-click each one of the ePO resources, and select Delete: McAfee ePolicy Orchestrator 4.5.0 Server McAfee ePolicy Orchestrator 4.5.0 Application Server 3 McAfee ePolicy Orchestrator 4.5.0 Event Parser Open the Windows Control Panel, select Add or Remove Programs, select McAfee ePolicy Orchestrator, then click Change/Remove.

Windows server 2008

Before running ePolicy Orchestrator as a clustered application, ensure that: Microsoft Failover Clustering is set up and running on a cluster of two or more servers. Two separate drives are configured for clustering: A Quorum drive A Data drive A supported remote database server is configured for the ePO installation: SQL 2005 SQL 2008 The following information is available during installation: The ePolicy Orchestrator virtual server IP Address The ePolicy Orchestrator virtual server name The ePolicy Orchestrator virtual server FQDN The location on the data drive where you intend to place the ePolicy Orchestrator cluster folder CAUTION: The IP address and name of the ePO virtual server should be static and unique. These two identifiers of the ePO virtual server should be listed as resources in the ePolicy
Orchestrator group along with the Cluster IP address and Cluster network name that were created when you set up MSCS. To ensure that all four resources appear, avoid using the same identifying information for both the Cluster and the ePO virtual server.
Once the requirements are met, use these tasks to set up the nodes of the cluster. Before you begin Before configuring and installing ePolicy Orchestrator 4.5, run the "Validate a Configuration" tool in "Failover Cluster Management" to ensure your cluster configurations is setup correctly. Tasks Installing ePolicy Orchestrator on each node Creating the ePolicy Orchestrator application group Creating the Client Access Point Creating the data drive Creating the Generic Services resources
Run the ePolicy Orchestrator setup on each of the nodes. Task For option definitions, click ? in the interface. Double click Setup.exe in the installation folder. Follow the wizard until you reach the Choose Destination Location page, and specify the path for the shared data drive and click Next. NOTE: Use this same path for each node. In the Set Database and Virtual Server Settings, Select Enable Microsoft Cluster Server Support. On the first node only provide the following identifying information for the ePO cluster: The ePO virtual server IP address The ePO virtual server name The ePO virtual server FQDN NOTE: This information is automatically provided on subsequent nodes. Complete the installation of ePolicy Orchestrator on the first node as described in First-Time Installation. Repeat this task for the second node.

Creating the Event Parser resource
Use this task to create the McAfee ePolicy Orchestrator Event Parser resource. Task For option definitions, click ? in the interface. Right-click the ePO Application Group and select Add a resource | Generic Service. The Select Service Wizard appears. Select McAfee ePolicy Orchestrator 4.5.0 Event Parser and click Next. The Confirmation page displays.
Click Next to allow the Generic Service to be created. Click Finish when the Wizard is complete. Right-click the McAfee ePolicy Orchestrator 4.5.0 Event Parser resource and select Properties. The Properties dialog appears. Click the Dependencies tab and then add McAfee ePolicy Orchestrator 4.5.0 Application Server as a dependency.
When the ePolicy Orchestrator cluster is set up and online, use this task to ensure that ePolicy Orchestrator functions in a failover situation. Task For option definitions, click ? in the interface. Restart the system functioning as the active node. The passive node automatically becomes the active node and you are automatically logged-out. When ePolicy Orchestrator prompts you to log in, you can conclude that it has continued to function during the failover.
Use this task to remove ePolicy Orchestrator from a system running as a cluster node. Task For option definitions, click ? in the interface. To open the Failover Cluster Management tool on the Active Node, click Start | Programs | Administrative Tools | Failover Cluster Management. In the ePO application group, right-click each one of the following ePO resources, and select Delete: McAfee ePolicy Orchestrator 4.5.0 Server McAfee ePolicy Orchestrator 4.5.0 Application Server 3 McAfee ePolicy Orchestrator 4.5.0 Event Parser Open the Windows Control Panel and select Programs and Features, then select McAfee ePolicy Orchestrator and click Uninstall/Change. Repeat this step for every node.