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

First-Time Installation Installing the server
If you intend to use an existing instance of SQL Server 2005, or SQL 2008, you can continue without selecting the checkbox for 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 SQL 2005 or 2008 on a server. If you are installing ePolicy Orchestrator with SQL 2005, the SQL Browser must be enabled or you cannot complete the installation wizard. Install SQL Server 2005 Express on the same computer where you are installing ePolicy Orchestrator. If you selected the checkbox for installation of SQL Server 2005 Express, ePolicy Orchestrator installs the database automatically. If you are installing SQL Server 2005 Express, you might be prompted to install SQL Server 2005 Backward Compatibility. You must install it. In the Welcome page of the installation wizard, click Next. The License Key page appears. NOTE: License Keys are distributed from the same McAfee website from which the ePolicy Orchestrator software is downloaded. 5 Select whether you are installing based on a license key or installing an evaluation version. If you have a License Key, type its number here. If you select License Key but do not type its number you are asked if you want to install an evaluation version. Click OK to proceed with installation of the evaluation version, or Cancel to return to the previous page. If you are installing a beta version of the software, the Beta test information box appears. Click OK. Accept the End User License Agreement, then click OK to continue. The Choose Destination Location dialog box appears. Click Next. Accept the default installation path or click Browse to select or create a different location, then click Next. If installing on a cluster server, the Set Database and Virtual Server Settings dialog box appears. Otherwise the Set Administrator Information dialog box appears. Type and verify the password for logging on to this ePolicy Orchestrator server, then click Next. If your environment employs Microsoft Cluster Server (MSCS) for a high availability system that ensures failover support, the Set Database and Virtual Server Settings dialog box appears.
10 In the Set Database Information dialog box, identify the type of account and authentication details that the ePO server will use to access the database: a Use the drop-down list to select a database server. If SQL Express was installed, the name of the database is <computername>\EPOSERVER. b Select the type of authentication, then click Next. Windows authentication (recommended) Specify the NetBIOS name of the Domain associated with the desired domain administrator user account. Then, provide and verify a password. NOTE: If the database identification fails, type 1433 or 1434 in the SQL server TCP port field. SQL authentication Provide the User name that the ePolicy Orchestrator software will use to access the database, then provide a password. If the installer cannot identify

First-Time Installation Installing an Agent Handler
the port used for communication to and from the server, you might be prompted to provide that information. NOTE: The ePolicy Orchestrator account must have DB ownership to the database. 11 Set the HTTP Configuration. Designate the port to be used by each function, then click Next.
Function Agent-to-Server communication port Port Configurable. McAfee recommends using a port other than 80. Configurable. Configurable port used to send SuperAgent wake-up calls. Configurable.
Agent Wake-Up communication port Agent Broadcast communication port
Console-to-Application Server communication port Sensor-to-Server communication port
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. See SQL documentation for configuration information.
Security Threats communication port

SQL server TCP port

NOTE: Client firewalls block communication from the ePO server. Ensure that the ports required for communication from the ePO server are available on the client. 12 Optional step (can be performed after ePolicy Orchestrator is up-and-running). In the Default Notification Email Address dialog box, type the email address of the recipient of messages from ePolicy Orchestrator notification 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. However, 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. 13 In the Start Copying Files dialog box, click Next to begin the installation. 14 In the Installation Complete dialog box, you can view the Release Notes, launch ePolicy Orchestrator, or click Finish to complete the installation.
Installing an Agent Handler
Use this task to set up an Agent Handler.
Before you begin You must first install the ePO server with which the Agent Handler is to communicate. Task Open the folder where you extracted the contents of the ePolicy Orchestrator installation package. Copy the AgentHandler folder to the intended Agent Handler server system. Double-click and run Setup.exe. Installation activities take place in the background. When they are completed, the InstallShield Wizard for McAfee Agent Handler opens. Click Next. Accept the default destination or click Browse to change the destination, then click Next. The Server Information page opens. Type the machine name of the ePO Server with which the Agent Handler is to communicate. Type the port to be used for server-handler communication. Port 8433 is the default. McAfee recommends that you change the port designation. See the discussion of Ports in the Server and Agent Handler requirements section. Type the ePO Admin User name and password of a user with global administrator privileges. If these credentials are to be used for the database as well, click Next to start the installation. NOTE: These credentials must be identical with those used during installation of ePolicy Orchestrator. 8 If you want to use different database credentials than those mentioned in step 7, follow these additional steps: a Deselect Use ePO Server's database credentials, then click Next. b Type the name of the SQL database server. c Select Windows Authentication or SQL Authentication, then type the credentials. NOTE: These credentials must be identical with those of a previously defined SQL Server user. 9 Click Next. The installation process begins.

Upgrading to ePolicy Orchestrator 4.5
This chapter provides instructions for upgrading an existing version of ePolicy Orchestrator to version 4.5 of the software. Contents Unsupported products Performing backups before upgrading Upgrading the ePO server from version 3.6.1 Upgrading the ePO server from version 4.0

Removing unused consoles

ePolicy Orchestrator 3.6.1 and earlier provided the option of installing remote consoles (MMC). If remote consoles are present, use Windows Add/Remove programs feature to remove them.

Unsupported products

The following products are no longer supported in version 4.5 and are not migrated. McAfee ePolicy Orchestrator Agent for Macintosh OS X McAfee ePolicy Orchestrator Agent for Linux McAfee ePolicy Orchestrator Agent for Netware McAfee NetShield 4.6.3 for NetWare McAfee Common Management Agent 3.5.5 McAfee LinuxShield 1.3 McAfee LinuxShield 1.4 McAfee LinuxShield 1.5 McAfee Site Advisor Enterprise 1.5 McAfee Non-Windows Agents v2.0 McAfee VirusScan Mobile Enterprise McAfee System Compliance Profiler 2.0 McAfee Network Access Control 3.0 Patch 2 McAfee Policy Auditor 5.0 McAfee Policy Auditor 5.0.1 McAfee Group Shield for Exchange 6.0
Upgrading to ePolicy Orchestrator 4.5 Performing backups before upgrading
McAfee Groups Shield for Exchange 6.0.2 with SKE RTW Repost_5200 McAfee Virex 7.7 McAfee VirusScan 8.0i with McAfee AntiSpyware Enterprise Patch 16 McAfee VirusScan For Macintosh 8.5 McAfee VirusScan For Macintosh 8.6
Performing backups before upgrading
Before you upgrade to version 4.5, back up all ePolicy Orchestrator databases, as well as the ePO directory. Additional information is available in the following Knowledge Base articles:
ePolicy Orchestrator Version 3.6x 4.0 KB article KB53219 KB51438
Upgrading the ePO server from version 3.6.1
This task upgrades the ePO server from ePolicy Orchestrator version 3.6.1 Patch 4 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 version 3.6.1 is: C:\Program Files\McAfee\ePO\3.6.1 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. 4 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.

Upgrading to ePolicy Orchestrator 4.5 Upgrading the ePO server from version 3.6.1
In the Choose Destination Location dialog box, accept the default installation path or click Browse to select a different location, then click Next. If installing on a cluster server, the Set Database and Virtual Server Settings dialog box appears. Otherwise the Set Administrator Information dialog box appears. In the Set Administrator Information dialog box, type and verify the user name and password for logging on to this ePO server for the first time, then click Next. For security reasons, ePolicy Orchestrator does not allow accounts with blank passwords. In the Set Database Information dialog box, identify the type of account and authentication details that the ePO server will use to access the database. Indicate whether ePolicy Orchestrator will use a Windows NT user account or a SQL Server user account. McAfee recommends using Windows NT authentication. NOTE: The name of the database server that was set during the original installation cannot be changed here. Windows authentication (recommended) Specify the NetBIOS name of the Domain associated with the desired domain administrator user account. Then, provide and verify a password. SQL authentication Provide the User name that ePolicy Orchestrator will use to access the database, then provide a password. If the installer cannot identify the port used for communication to and from the server, you might be prompted to provide that information. Otherwise, the SQL server TCP port field shows the port and is disabled. When upgrading an installation using NT authentication, the Set Database Information panel of the wizard appends the domain name to the User name field and auto-populates the port field with 1433. Remove the domain from the User name field and click Next. You will receive a port error. Dismiss this error and manually retype the port number 1433, then click Next. For security reasons, ePolicy Orchestrator does not accept accounts with blank passwords. NOTE: If you are installing on a system with a local SQL 2005 database server, you must manually type the TCP port number on the Set Database Information page of the installation wizard.
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.

Log File Name

Log Type

File Location

Description Tomcat service. Present only after initial service startup The file contains any Standard Error output captured by the Tomcat service.
Installing in a Cluster Environment
The ePolicy Orchestrator software provides high availability for server clusters with Microsoft Cluster Server (MSCS) software. Which operating system are you installing on? Windows server 2003 Windows server 2008

Windows server 2003

Contents Requirements Setting up the ePolicy Orchestrator cluster Testing the ePolicy Orchestrator cluster Uninstalling ePolicy Orchestrator

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. Two separate drives are configured for clustering: a Quorum drive and 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 FDQN. 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.
Installing in a Cluster Environment Windows server 2003
Setting up the ePolicy Orchestrator cluster
Once the requirements are met, use these tasks to set up the nodes of the cluster. Tasks Installing ePolicy Orchestrator on each node Creating the ePolicy Orchestrator group Creating the data drive Creating the IP address resource Creating the Network Name resource 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 turned on. Task 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.

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 Application Server resource
Use this task to create the McAfee ePolicy Orchestrator 4.5.0 Apoplication Server resource. Task For option definitions, click ? in the interface. 5 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 Application Server 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 Application Server resource and select Properties. The Properties dialog appears. Click the Dependencies tab and then add McAfee ePolicy Orchestrator 4.5.0 Server as a dependency.
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.