Installation Guide Revision 1.0 ePolicy version 3.
COPYRIGHT © 2003 Networks Associates Technology, 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 Networks Associates Technology, Inc., or its suppliers or affiliate companies.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Getting more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Preparing McAfee AutoUpdate Architect 1.0 repositories . . . . . . . . . . . . . . . . . . . . . . . . . 36 How AutoUpdate 7.0 information is converted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3 Installing the Software for the First-Time . . . . . . . . . . . . . . . . . . 39 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Installing the server and console . . . . . . . . . . . . . .
Contents A Migrating Existing Databases to SQL Server 2000 . . . . . . . . . . . 99 Migrating from MSDE to SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Migrating from SQL Server 7 to SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Stopping the ePolicy Orchestrator server service . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Installing Client Tools only (SQL Server 2000) . . . . . . . . . . . . . . . . . . . . . . . . .
Contents vi ePolicy Orchestrator™ software version 3.
Preface This Installation Guide introduces McAfee® ePolicy Orchestrator™ software version 3.0, and provides the following information: n Minimum hardware and database software recommendations. n Minimum hardware and software requirements. n Detailed instructions for installing or upgrading the database software. n Detailed instructions for installing the software for the first time. n Detailed instructions for upgrading the software from a previous version.
Preface Conventions This guide uses the following conventions: Bold All words from the user interface, including options, menus, buttons, and dialog box names. Example Type the User name and Password of the desired account. Courier Text that represents something the user types exactly; for example, a command at the system prompt. Example To enable the agent, run this command line on the client computer: FRMINST.EXE /INSTALL=AGENT /SITEINFO=C:\TEMP\SITELIST.
Preface Getting more information Product Guide Product introduction and features, detailed instructions for configuring the software, information on deployment, recurring tasks, and operating procedures. Available in an Adobe Acrobat .PDF file from either the product CD or the McAfee Security download site. Product Deployment Comparison Compares the method used to deploy products in version 3.0 with the same process in version 2.0, 2.5, and 2.5.1.
Preface Getting Started Guide Detailed instructions for installing the Small Business Edition of the software, detailed instructions for configuring and deploying the agent and anti-virus products using an automated wizard, and a list of weekly anti-virus management tasks. Available as a printed booklet that accompanies the product CD. Also available in an Adobe Acrobat .PDF file from either the product CD or the McAfee Security download site. Release Notes README file.
Preface Contacting McAfee Security & Network Associates Technical Support Home Page http://www.nai.com/naicommon/services/technical-support/intro.asp KnowledgeBase Search https://knowledgemap.nai.com/phpclient/Homepage.aspx PrimeSupport Service Portal * http://mysupport.nai.com McAfee Security Beta Program http://www.mcafeeb2b.com/beta/ AVERT Anti-Virus Emergency Response Team Home Page http://www.mcafeeb2b.com/naicommon/avert/default.asp Virus Information Library http://vil.nai.
Preface 12 ePolicy Orchestrator™ software version 3.
1 Requirements and Recommendations The minimum system requirements and minimum hardware configuration and database software are provided in these topics: n System requirements. n Recommendations. System requirements Before you begin the installation, verify that the minimum system requirements are met for all computers being used as ePolicy Orchestrator servers, consoles, and remote consoles; for the ePolicy Orchestrator database; for ePolicy Orchestrator reporting; and for ePolicy Orchestrator agent.
Requirements and Recommendations Server and console requirements The ePolicy Orchestrator server and console install and run on any Intel Pentium II-class (or higher) compatible PC or higher equipped with: NOTE Installing the software to a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC) is supported, but not recommended. n Browser — Microsoft Internet Explorer 6.0. n Dedicated server — If managing more than 250 client computers, we recommend using a dedicated server.
Requirements and Recommendations n Processor — 400MHz processor or higher. n Terminal Services — Supported operating systems support Terminal Services. NOTE Although you can install the software on a computer with Terminal Services, you cannot use Terminal Services to install or use the software. To manage the software remotely, install ePolicy Orchestrator remote consoles and log on to ePolicy Orchestrator servers from these remote consoles.
Requirements and Recommendations n Operating system — Any of the following Microsoft Windows operating systems: w Windows 2000 Advanced Server with Service Pack 1 or later. w Windows 2000 Professional with Service Pack 1 or later. w Windows 2000 Server with Service Pack 1 or later. w Windows NT Server 4.0 with Service Pack 6a. w Windows NT Workstation 4.0 with Service Pack 6a. w Windows Server 2003 Enterprise. w Windows Server 2003 Standard. w Windows Server 2003 Web. w Windows XP Professional.
Requirements and Recommendations n Dedicated network connection — If using SQL Server and managing more than 5,000 client computers, install SQL Server on a separate server from the ePolicy Orchestrator server, and use a dedicated network connection. n Local database server — If using SQL Server on the same server as the ePolicy Orchestrator server, we recommend specifying a fixed memory size approximately two-thirds of the total memory for SQL Server in Enterprise Manager.
Requirements and Recommendations Reporting requirements To create custom report templates, you must use Crystal Decisions Crystal Reports 8.0. The Chinese (Simplified), Chinese (Traditional), Japanese, and Korean language versions of reports install and run on computers equipped with the corresponding language version of the supported operating system and database software.
Requirements and Recommendations n Operating system — Any of the following Microsoft Windows operating systems: w Windows 2000 Advanced Server with Service Pack 1, 2, or 3. w Windows 2000 Datacenter Server with Service Pack 1, 2, or 3. w Windows 2000 Professional with Service Pack 1, 2, or 3. w Windows 2000 Server with Service Pack 1, 2, or 3. w Windows 95. w Windows 98 Second Edition (SE). w Windows 98. w Windows Millennium Edition (Me). w Windows NT 4.
Requirements and Recommendations n Windows 95 — Client computers using Windows 95A, Windows 95B, and Windows 95C must meet these additional requirements: w VCREDIST.EXE, available at no charge from Microsoft. At press time, this program and instructions for installation were available on the Microsoft web site: support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q259403& NOTE After you install VCREDIST.EXE, you must restart the computer. w DCOM95 1.3, available at no charge from Microsoft.
Requirements and Recommendations SuperAgent requirements You can enable the ePolicy Orchestrator agent for Windows as a SuperAgent, which is used to communicate with other agents or store a distributed repository. n Operating system — Any of the following Microsoft Windows operating systems: w Windows 2000 Datacenter Server with Service Pack 1, 2, or 3. w Windows 2000 Professional with Service Pack 1, 2, or 3. w Windows 2000 Server with Service Pack 1, 2, or 3. w Windows NT 4.
Requirements and Recommendations n Operating system — Any of the following Novell operating systems: w NetWare 4.11 with Support Pack 9. w NetWare 4.2 with Support Pack 9. w NetWare 5.0 with Support Pack 6a. w NetWare 5.1 with Support Pack 5. w NetWare 6.0. n Product — McAfee NetShield 4.6 for NetWare. Agent for WebShield appliances requirements The ePolicy Orchestrator agent for WebShield appliances installs and runs on ny of the following WebShield appliances: n WebShield e250 appliance.
Requirements and Recommendations Recommendations For optimum performance, we recommend the following minimum hardware configuration and database software based on the number of client computers being managed by a single ePolicy Orchestrator server: Client computers Processor and processor speed Memory Free disk space for database Database Less than 100 Pentium II 400MHz 256MB 500MB MSDE 100 – 500 Pentium III 500MHz 256MB (dedicated server) 500MB – 1GB MSDE 512MB (non-dedicated server) 500 –
Requirements and Recommendations 24 ePolicy Orchestrator™ software version 3.
2 Pre-Installation Procedures The procedures you need to complete before you install the new version of the software depend on whether you are installing the software for the first time or upgrading from version 2.0, 2.5, or 2.5.1. For a list of which procedures apply to you, see the appropriate Before you begin section in Installing the Software for the First-Time on page 39 or Upgrading from Version 2.0, 2.5, or 2.5.1 on page 57, respectively. n Pre-installation best practices guidelines.
Pre-Installation Procedures Pre-installation best practices guidelines We recommend that you complete the following tasks before you install the software. n Update the ePolicy Orchestrator server with the latest Microsoft security updates. n Update the ePolicy Orchestrator database server with the latest Microsoft security updates for the database software you use. NOTE Specifically, be sure to install Service Pack 3 on all MSDE 2000 and SQL Server 2000 databases.
Pre-Installation Procedures Installing or upgrading the database software Depending on which database you are using and whether you are upgrading it to the most recent version, you need to complete different tasks. In most cases, we recommend that you install or upgrade the database before you install the ePolicy Orchestrator software. n Installing MSDE 2000 for the first time. n Upgrading MSDE to MSDE 2000. n Remote database servers using MSDE or MSDE 2000.
Pre-Installation Procedures Installing SQL Server 2000 for the first time If you are installing SQL Server 2000 for the first time, you must manually install it before you install the ePolicy Orchestrator software. Be sure to also install Service Pack 3 for SQL Server 2000. For instructions, see the SQL Server product documentation. If you installed SQL Server remotely, verify that it is visible on the network before you install the ePolicy Orchestrator software.
Pre-Installation Procedures 3 In Open, type the following command: MSIEXEC.EXE /I “E:\SETUP\MSDE\SQLRUN01.MSI” /Q TARGETDIR=”C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\” COLLATION=SQL_LATIN1_GENERAL_CP1_CI_AS SAPWD= REBOOT=R Where TARGETDIR equals the installation path of the ePolicy Orchestrator software. The default location is provided here. And where is the password for the System Administrator (sa) user account. 4 Click OK to start the installation.
Pre-Installation Procedures Upgrading to MDAC 2.7 Before you install the ePolicy Orchestrator software, you need to determine the version of Microsoft Data Access Components (MDAC) currently installed on all ePolicy Orchestrator database servers, then upgrade to version 2.7 as needed. Because the ePolicy Orchestrator server uses version 2.7, it’s important that all database servers use the same version to avoid performance and functionality issues. WARNING The ePolicy Orchestrator 3.
Pre-Installation Procedures Installing MDAC Use this procedure to install Microsoft Data Access Components (MDAC) 2.7. You must do this manually for all remote database servers and for all local database servers using a Chinese (Simplified), Chinese (Traditional), or Korean language version of the database software. n The English, French, German, Japanese, and Spanish language versions of the MDAC 2.
Pre-Installation Procedures Downloading the software Use this procedure to download the software from the McAfee Security web site and extract the Setup program and other files that you need to install the software. 1 Go to the McAfee Security download web site. For more information, see Contacting McAfee Security & Network Associates on page 11. 2 Download the following files to a temporary location; for example, C:\TEMP: w EPO300B.EXE w EPO300B.C00 w EPO300B.
Pre-Installation Procedures Which files are checked in during the installation Files that are checked into the master repository or the Repository as part of the installation are listed below. For more information, see Supported Products and Features in the ePolicy Orchestrator 3.0 Product Guide or Help. n Agent language packages — The agent language packages for all supported languages are checked into the master repository as part of the installation.
Pre-Installation Procedures Which files are removed during the installation All policy pages, plug-in (.DLL) files, and Setup (binary) files associated with products that are no longer supported are removed from the Repository during the installation. The following products are no longer supported in this version of the software: 34 n McAfee AVERT Klez/Elkern stand-alone scanner 1.0 or later. n McAfee AVERT Nimda stand-alone scanner 1.0 or later. n McAfee NetShield 4.0.3 for Windows NT.
Pre-Installation Procedures How McAfee AutoUpdate Architect 1.0 information is converted If you are using McAfee AutoUpdate Architect 1.0 to manage distributed repositories, you can migrate their configuration settings to ePolicy Orchestrator 3.0. For instructions, see Preparing McAfee AutoUpdate Architect 1.0 repositories on page 36. How information in McAfee AutoUpdate Architect 1.0 is converted in ePolicy Orchestrator 3.0 is described below: In version 1.0, this... Is converted to this...
Pre-Installation Procedures Preparing McAfee AutoUpdate Architect 1.0 repositories Use this procedure to make a backup copy of the SITEMGR.XML file before you uninstall McAfee AutoUpdate Architect 1.0. This file contains the configuration settings of repositories defined in McAfee AutoUpdate Architect. You cannot install McAfee AutoUpdate Architect 1.0 and ePolicy Orchestrator 3.0 on the same computer. For more information, see How McAfee AutoUpdate Architect 1.0 information is converted on page 35.
Pre-Installation Procedures How AutoUpdate 7.0 information is converted If you are currently using ePolicy Orchestrator 2.5 or 2.5.1 to manage McAfee Security products that use AutoUpdate 7.0 (for example, McAfee VirusScan Enterprise 7.0), you can — as part of the installation — keep the McAfee AutoUpdate 7.0 policies and tasks for use with the agent 2.5 or 2.5.1 and convert them to ePolicy Orchestrator Agent policies and tasks for use with the agent 3.1.
Pre-Installation Procedures In version 2.5 or 2.5.1, this... Is converted to this... McAfee AutoUpdate 7.0 — Update and Mirror client tasks. Hidden McAfee AutoUpdate 7.0 — Update and Mirror client tasks. Although these tasks no longer appear, they continue to be enforced on the agent 2.5 and 2.5.1. These tasks are also converted to ePolicy Orchestrator agent — Update and Mirror tasks, which are enforced on the agent 3.1 only. Policy and task inheritance. 38 ePolicy Orchestrator™ software version 3.
3 Installing the Software for the First-Time The procedures you need to complete to install the new version of the software depend on whether you are migrating existing information from McAfee AutoUpdate Architect 1.0, and whether you are installing the ePolicy Orchestrator server and console or the remote console. Be sure to complete all pre-installation procedures that apply to you before you install the software.
Installing the Software for the First-Time Before you begin You need to complete the following procedures before you install the software: n Requirements and Recommendations on page 13. n Pre-installation best practices guidelines on page 26. n Installing or upgrading the database software on page 27. n Upgrading to MDAC 2.7 on page 30. n Downloading the software on page 32. n Which files are checked in during the installation on page 33.
Installing the Software for the First-Time Installing the server and console Use this procedure to install ePolicy Orchestrator 3.0 server and console on computers. For a list of common installation messages and their causes and solutions, see Troubleshooting on page 91. The ePolicy Orchestrator 3.0 Setup program requires you to restart the computer up to two times. All installations require that you restart the computer once. If Setup upgrades MDAC to version 2.
Installing the Software for the First-Time 4 In the ePolicy Orchestrator 3.0 Setup wizard, click Next to begin the installation. 5 For beta and evaluation versions of the software, an additional dialog box identifies how long you are licensed to use the software. Also, Step 6 and Step 7 differ slightly. For more information, see Beta and evaluation software on page 75.
Installing the Software for the First-Time 8 In the Installation Options dialog box, select Install Server and Console. Figure 3-1. Installation Options dialog box 9 Accept the default installation path (C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO) in Install to Folder, or click Browse to select a different location, then click Next.
Installing the Software for the First-Time 10 In the Server Service Account dialog box, specify the type of account to log on to the ePolicy Orchestrator server service, then click Next. Figure 3-2. Server Service Account dialog box w Use Local System Account — When selected, specifies that the ePolicy Orchestrator server service logs on using the system account rather than a user account. Most services log on to a system account.
Installing the Software for the First-Time Best practices recommendation When you change the password on the account used to log on to the ePolicy Orchestrator server service, be sure to update the password for the McAfee ePolicy Orchestrator 3.0 Server service. This procedure varies depending on the operating system. For instructions, see the operating system product documentation. 11 In the Select Database Server dialog box, specify the desired database server, then click Next. Figure 3-3.
Installing the Software for the First-Time w Use an existing server on the network — Uses the remote database server that you specify. The drop-down list displays all remote SQL Server database servers that are in the same domain as this computer. If the desired database server doesn’t appear, type its name in the list box. NOTE If using Windows NT, MDAC 2.7 is required to display the names of remote database servers in this list. If using other operating systems, MDAC 2.5 or later is required.
Installing the Software for the First-Time w Change SA password of existing SQL Server Account — This option applies only when you are upgrading the server and console. Allows you to change the System Administrator (sa) password on existing MSDE databases installed using the ePolicy Orchestrator Setup program. w Domain — Specifies the NetBIOS name of the domain associated with the desired domain administrator user account. Leave this box blank to use a local user account.
Installing the Software for the First-Time w HTTP port for Agent communication — Specifies the port number (default is 80) that the agent uses to communicate with the server. w HTTP port for Console communication — Specifies the port number (default is 81) that the console uses to communicate with the server. w HTTP port for Agent Wake-Up communication — Specifies the port number (default is 8081) used to send agent wakeup calls.
Installing the Software for the First-Time The Executing Setup dialog box appears and provides the status of the installation. Figure 3-7.
Installing the Software for the First-Time 15 In the Installation Complete dialog box, click Finish to complete the installation. You can also click View Readme to learn about the latest product information, resolved issues, any known issues, and last-minute additions or changes to the product or its documentation. In addition, steps for starting the software are provided. Figure 3-8. Installation Complete dialog box 50 ePolicy Orchestrator™ software version 3.
Installing the Software for the First-Time Changing the default password on the administrator user account You are required to change the default password on the global administrator (admin) user account after you install the software for the first time. It is important to change the default password on every ePolicy Orchestrator server to ensure that they are kept secure. 1 Start the software. For instructions, see Starting the software on page 87.
Installing the Software for the First-Time Installing remote consoles Use this procedure to install ePolicy Orchestrator 3.0 remote consoles on computers. You can use remote consoles to log on to and manage ePolicy Orchestrator servers across your network. For a list of common installation messages and their causes and solutions, see Troubleshooting on page 91. The ePolicy Orchestrator 3.0 Setup program requires you to restart the computer up to two times.
Installing the Software for the First-Time 5 In the Network Associates End User License Agreement dialog box, select the appropriate license type and the country in which you purchased the software. The license type you select must match the license you purchased. If you are unsure which license you purchased, contact the person who sold you the software.
Installing the Software for the First-Time 9 In the Ready To Install dialog box, click Install to begin the installation. This dialog box includes the estimated time needed to complete the installation. Figure 3-12. Ready To Install dialog box NOTE If you cancel the installation after you click Install, then uninstall the software, you can ignore messages indicating that Setup was unable to remove items. These messages appear because the items were never installed.
Installing the Software for the First-Time The Executing Setup dialog box appears and provides the status of the installation. Figure 3-13.
Installing the Software for the First-Time 10 In the Installation Complete dialog box, click Finish to complete the installation. You can also click View Readme to learn about the latest product information, resolved issues, any known issues, and last-minute additions or changes to the product or its documentation. In addition, steps for starting the software are provided. Figure 3-14. Installation Complete dialog box 56 ePolicy Orchestrator™ software version 3.
4 Upgrading from Version 2.0, 2.5, or 2.5.1 The procedures you need to complete to upgrade from version 2.0, 2.5, or 2.5.1 depend on whether you are migrating existing information from McAfee AutoUpdate Architect 1.0 or AutoUpdate 7.0, and whether you are upgrading the ePolicy Orchestrator server and console or the remote console. You migrate AutoUpdate 7.0 information as part of the installation. Be sure to complete all pre-installation procedures that apply to you before you install the software.
Upgrading from Version 2.0, 2.5, or 2.5.1 Before you begin You need to complete the following procedures before you upgrade the software: n Requirements and Recommendations on page 13. n Pre-installation best practices guidelines on page 26. n Installing or upgrading the database software on page 27. n Upgrading to MDAC 2.7 on page 30. n Downloading the software on page 32. n Which files are checked in during the installation on page 33.
Upgrading from Version 2.0, 2.5, or 2.5.1 Backing up ePolicy Orchestrator databases Before you upgrade to version 3.0, we recommend that you back up all ePolicy Orchestrator databases. n If you are using Microsoft SQL Server as the ePolicy Orchestrator database, see the Microsoft product documentation. n If you are using Microsoft Data Engine (MSDE) as the ePolicy Orchestrator database, you can use the Database Backup Utility (DBBAK.
Upgrading from Version 2.0, 2.5, or 2.5.1 Upgrading the server and console Use this procedure to upgrade the ePolicy Orchestrator server and console from version 2.0, 2.5, or 2.5.1 to version 3.0. For a list of common installation messages and their causes and solutions, see Troubleshooting on page 91. The ePolicy Orchestrator 3.0 Setup program requires you to restart the computer up to two times. All installations require that you restart the computer once. If Setup upgrades MDAC to version 2.
Upgrading from Version 2.0, 2.5, or 2.5.1 1 Log on to the desired computer using a user 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 (MSSQLSERVER) is running. Depending on the operating system that you are using, this procedure varies. For instructions, see the Microsoft product documentation. 3 Close all ePolicy Orchestrator consoles.
Upgrading from Version 2.0, 2.5, or 2.5.1 9 A warning message appears to notify you which products are no longer supported and will be removed from the Repository. Click Next to delete all Setup (binary), Management Package, Package, and Plug-In Package files for all language versions of the listed products. Figure 4-1. Warning about product removal Migrating information from AutoUpdate 7.0 10 If you are upgrading from version 2.5 or 2.5.1 and the AutoUpdate 7.
Upgrading from Version 2.0, 2.5, or 2.5.1 11 In the Server Service Account dialog box, specify the type of account to log on to the ePolicy Orchestrator server service, then click Next. Figure 4-2. Server Service Account dialog box w Use Local System Account — When selected, specifies that the ePolicy Orchestrator server service logs on using the system account rather than a user account. Most services log on to a system account.
Upgrading from Version 2.0, 2.5, or 2.5.1 Best practices recommendation When you change the password on the account used to log on to the ePolicy Orchestrator server service, be sure to update the password for the McAfee ePolicy Orchestrator 3.0 Server service. This procedure varies depending on the operating system. For instructions, see the operating system product documentation. 12 In the Database Server Account dialog box, specify the type of account to log on to the database server, then click Next.
Upgrading from Version 2.0, 2.5, or 2.5.1 w Domain — Specifies the NetBIOS name of the domain associated with the desired domain administrator user account. Leave this box blank to use a local user account. Available only when you select This is an NT account. w User Name — Specifies the user name of the desired user account. If you selected Install a server on this computer and use it in the Select Database Server dialog box, type sa. w Password — Specifies the password of the desired user account.
Upgrading from Version 2.0, 2.5, or 2.5.1 13 In the Ready To Install dialog box, click Install to begin the installation. This dialog box includes the estimated time needed to complete the installation. Figure 4-4. Ready To Install dialog box NOTE If you cancel the installation after you click Install, then uninstall the software, you can ignore messages indicating that Setup was unable to remove items. These messages appear because the items were never installed.
Upgrading from Version 2.0, 2.5, or 2.5.1 The Executing Setup dialog box appears and provides the status of the installation. Figure 4-5.
Upgrading from Version 2.0, 2.5, or 2.5.1 14 In the Installation Complete dialog box, click Finish to complete the installation. You can also click View Readme to learn about the latest product information, resolved issues, any known issues, and last-minute additions or changes to the product or its documentation. In addition, steps for starting the software are provided. Figure 4-6. Installation Complete dialog box 68 ePolicy Orchestrator™ software version 3.
Upgrading from Version 2.0, 2.5, or 2.5.1 Upgrading remote consoles Use this procedure to upgrade ePolicy Orchestrator remote consoles from version 2.0, 2.5, or 2.5.1 to version 3.0. You can use remote consoles to log on to and manage ePolicy Orchestrator servers across your network. For a list of common installation messages and their causes and solutions, see Troubleshooting on page 91. The ePolicy Orchestrator 3.0 Setup program requires you to restart the computer up to two times.
Upgrading from Version 2.0, 2.5, or 2.5.1 4 In the ePolicy Orchestrator 3.0 Setup wizard, click Next to begin the installation. 5 For beta and evaluation versions of the software, an additional dialog box identifies how long you are licensed to use the software. Also, Step 6 and Step 7 differ slightly. For more information, see Beta and evaluation software on page 75.
Upgrading from Version 2.0, 2.5, or 2.5.1 8 In the Ready To Install dialog box, click Install to begin the installation. This dialog box includes the estimated time needed to complete the installation. Figure 4-7. Ready To Install dialog box NOTE If you cancel the installation after you click Install, then uninstall the software, you can ignore messages indicating that Setup was unable to remove items. These messages appear because the items were never installed.
Upgrading from Version 2.0, 2.5, or 2.5.1 The Executing Setup dialog box appears and provides the status of the installation. Figure 4-8. Executing Setup dialog box 72 ePolicy Orchestrator™ software version 3.
Upgrading from Version 2.0, 2.5, or 2.5.1 9 In the Installation Complete dialog box, click Finish to complete the installation. You can also click View Readme to learn about the latest product information, resolved issues, any known issues, and last-minute additions or changes to the product or its documentation. In addition, steps for starting the software are provided. Figure 4-9.
Upgrading from Version 2.0, 2.5, or 2.5.1 74 ePolicy Orchestrator™ software version 3.
5 Migrating to a Licensed Version of the Software Use this procedure to migrate an evaluation version of the software to a licensed version. To migrate any pre-release software (beta or release candidate) to a licensed version, you must first uninstall the existing version of the software. For instructions, see Uninstalling the software on page 89. 1 Log on to the desired computer using a user account with local administrator permissions. 2 Close all ePolicy Orchestrator consoles.
Migrating to a Licensed Version of the Software n Beta software — Click Beta Contact to access the beta feedback page on the Network Associates web site, where you can supply your comments about the beta software. n Evaluation software — Click Buy to access a page on the Network Associates web site, where you can purchase a full version of the software. The reminder dialog box appears a number of times before the license expires.
6 Post-Installation Procedures The procedures you need to complete after you install the new version of the software depend on whether you are migrating existing information from McAfee AutoUpdate Architect 1.0 or AutoUpdate 7.0, and whether you are installing the software for the first time or upgrading from version 2.0, 2.5, or 2.5.1. Regardless, you need to complete the following procedures after you install the software: n Post-installation best practices guidelines on page 78.
Post-Installation Procedures Post-installation best practices guidelines We recommend that you complete the following tasks after you install the software. n If you installed a new ePolicy Orchestrator database, we recommend that you assign a password to the System Administrator (sa) user account. For instructions, see Securing ePolicy Orchestrator databases in the ePolicy Orchestrator 3.0 Product Guide or Help. n Define maintenance settings for ePolicy Orchestrator databases.
Post-Installation Procedures Which files you need to check in manually Files that you must check into the master repository or the Repository after you install the software are listed below. For more information, see Supported Products and Features in the ePolicy Orchestrator 3.0 Product Guide or Help. n Contents of the McAfee AutoUpdate Architect 1.0 master repository — Packages that were checked into the McAfee AutoUpdate Architect master repository are not migrated to the ePolicy Orchestrator 3.
Post-Installation Procedures Determining which products can be managed Use this procedure to determine which products currently have policy pages in the Repository. Policy pages allow you to set policies and create scheduled tasks for products. 1 Log on to the desired ePolicy Orchestrator server. For instructions, see Logging on to or adding ePolicy Orchestrator servers in the ePolicy Orchestrator 3.0 Product Guide or Help. 2 In the console tree under ePolicy Orchestrator | , select Directory.
Post-Installation Procedures Agent AutoUpgrade The items below apply only to the agent for Windows. The agent for WebShield appliances and the agent for NetWare have not been updated for this release. n If you upgrade the software from version 2.0, 2.5, or 2.5.1, agents are not automatically upgraded to version 3.1 unless you enable agent AutoUpgrade. The version 2.0, 2.5, and 2.5.1 agents continue to send events and properties to the ePolicy Orchestrator server.
Post-Installation Procedures Importing McAfee AutoUpdate Architect 1.0 repositories Use this procedure to import the configuration settings of repositories defined in the McAfee AutoUpdate Architect 1.0 software into the ePolicy Orchestrator 3.0 software. For more information, see How McAfee AutoUpdate Architect 1.0 information is converted on page 35. We recommend that you import repositories from McAfee AutoUpdate Architect before you set up repositories in ePolicy Orchestrator.
Post-Installation Procedures 3 In the details pane under AutoUpdate Components, click Source Repository. The Source and Fallback Repositories page appears. Figure 6-1. Source and Fallback Repositories page 4 Click Import repository list to open the Open dialog box, and select the McAfee AutoUpdate Architect repository list (SITEMGR.XML).
Post-Installation Procedures Verifying configuration settings for repositories If you migrated existing information from McAfee AutoUpdate Architect 1.0 or AutoUpdate 7.0, use this procedure to verify that no duplicate repositories exist and that the configuration settings for all repositories are correct. 1 Review source and fallback repositories. For instructions, see these topics in the ePolicy Orchestrator 3.0 Product Guide or Help: w Redefining the default source repository.
Post-Installation Procedures Defining proxy server settings You need to provide separate proxy server settings for the master repository and for client computers. The settings for the master repository enable it to retrieve packages through a proxy server. The master repository uses these settings to retrieve packages from source repositories through a proxy server. The client computer settings enable client computers to retrieve packages through a proxy server.
Post-Installation Procedures Removing AutoUpdate 7.0 policies and tasks after agent deployment If you migrated existing McAfee AutoUpdate 7.0 policies and tasks during the installation, you can remove these settings from the database after you upgrade all agents to version 3.1, or when you no longer want to enforce these policies and tasks on the agent 2.5 or 2.5.1. Because these policies and tasks continue to be enforced on the agent 2.5 and 2.5.
7 Getting Started Once you have installed the software, use these topics to start using it: n Determining the language version of the software. n Starting the software. n Uninstalling the software. Determining the language version of the software The ePolicy Orchestrator software is automatically installed in multiple languages. The locale you select in Regional Settings when you start the software determines the language version in which the ePolicy Orchestrator console and policy (.
Getting Started 2 Click the Start button, then point to Programs | Network Associates | ePolicy Orchestrator 3.0 Console. The ePolicy Orchestrator console appears. Figure 7-1. ePolicy Orchestrator console 3 88 If you have just installed the software to a computer for the first time, you are required to change the default password on the global administrator user account. For instructions, see Changing the default password on the administrator user account on page 51.
Getting Started Uninstalling the software Use this procedure to remove the software. If you used the ePolicy Orchestrator Setup program to install MSDE, you can remove it at the same time. 1 Close all ePolicy Orchestrator consoles. 2 Close all database management software; for example, SQL Enterprise Manager. 3 Use Add/Remove Programs in the Control Panel to remove the software. For instructions, see the Windows Help File. To open this file, click the Start button, then select Help.
Getting Started 90 ePolicy Orchestrator™ software version 3.
8 Troubleshooting The most common messages that appear during an installation and their solutions are listed in Table 8-1 on page 92. Messages are listed in alphabetical order. If you are unable to resolve an issue using the information in this table, be sure to gather the following information before you contact the Network Associates Technical Support staff: n Verify that you have met the minimum installation requirements. For a complete list, see System requirements on page 13.
Troubleshooting Table 8-1. Common installation messages and their solutions If this message appears... Then... ePolicy Orchestrator 1.0 is currently installed. First upgrade to 1.1, then upgrade to 2.0, then upgrade to 3.0. The ePolicy Orchestrator 2.0 software has not been installed on this computer. You must install version 2.0 before you can install version 3.0. If you are using version 1.0 or 1.1, see the ePolicy Orchestrator 1.1 Getting Started Guide or ePolicy Orchestrator 2.
Troubleshooting Table 8-1. Common installation messages and their solutions (Continued) If this message appears... Then... Microsoft Windows 2000 SP 1 is not installed. ePolicy Orchestrator recommends Windows 2000 Service Pack 1 or later be installed. The computer on which you are attempting to install the software is using a non-supported version of the operating system. Microsoft Windows NT or 2000 Server is not installed. ePolicy Orchestrator requires that you run on Windows NT or 2000 Server.
Troubleshooting Table 8-1. Common installation messages and their solutions (Continued) If this message appears... Then... Please enter a value in the “Install to Folder” field provided. The Install to Folder box is blank. Type the installation path in Install to Folder, or click Browse to select a location. The default location is: C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO Please enter a value in the “User Name” field provided. Please enter a value in the “VirusScan Enterprise 7.
Troubleshooting Table 8-1. Common installation messages and their solutions (Continued) If this message appears... Then... Setup was unable to access the Domain to validate the user information you entered. The domain that you specified could not be accessed. Make sure the current logged on user has access to the domain. 1 Verify that the Domain, User Name, and Password you provided are typed correctly. 2 Verify that the user account you used to log on to this computer has access to this domain.
Troubleshooting Table 8-1. Common installation messages and their solutions (Continued) If this message appears... Then... The License file is missing. Please contact support for assistance. Setup is unable to read the license information required to install the software. Contact Network Associates Customer Service. For more information, see Contacting McAfee Security & Network Associates on page 11. The operating system you are using is not currently supported.
Troubleshooting Table 8-1. Common installation messages and their solutions (Continued) If this message appears... Then... This system is not currently configured with a static IP address, which is recommended for ePolicy Orchestrator Server. The computer on which you are attempting to install the software does not use a static IP address. Unable to determine the edition of your license. Please contact support for assistance.
Troubleshooting Table 8-1. Common installation messages and their solutions (Continued) If this message appears... Then... You cannot install MSDE 2000 Service Pack 3 on a Backup Domain Controller. You are trying to install ePolicy Orchestrator on a Backup Domain Controller (BDC). MSDE 2000 with Service Pack 3 cannot be installed on a BDC. Do one of the following: You have chosen the user “sa” with a blank password for your SQL information.
A Migrating Existing Databases to SQL Server 2000 To migrate existing ePolicy Orchestrator databases from Microsoft Data Engine (MSDE) or SQL Server 7 with Service Pack 3 to SQL Server 2000, use one of the following procedures after you install ePolicy Orchestrator 3.0: n Migrating from MSDE to SQL Server 2000. n Migrating from SQL Server 7 to SQL Server 2000.
Migrating Existing Databases to SQL Server 2000 Stopping the ePolicy Orchestrator server service Now that you have successfully installed ePolicy Orchestrator 3.0, you need to stop the ePolicy Orchestrator server service (McAfee ePolicy Orchestrator 3.0 Server) to ensure the data integrity while you back up the database. Depending on the operating system that you are using, this procedure varies. For instructions, see the Microsoft product documentation.
Migrating Existing Databases to SQL Server 2000 Backing up ePolicy Orchestrator 3.0 databases (MSDE users) Now that you have installed the SQL Server 2000 Client Tools, you are ready to back up the ePolicy Orchestrator 3.0 databases. It is important to back up the database should you need to continue using Microsoft Data Engine (MSDE). Be sure to store the backup copy of the database files (for example, EPO_.MDF and EPO_.LDF) in a safe and secure location.
Migrating Existing Databases to SQL Server 2000 Backing up ePolicy Orchestrator 3.0 databases (SQL Server 7 users) Now that you have stopped the ePolicy Orchestrator server service, you are ready to back up the ePolicy Orchestrator 3.0 databases. It is important to back up the database should you need to continue using SQL Server 7 with Service Pack 3. Be sure to store the backup copy of the database files (for example, EPO_.MDF and EPO_.LDF) in a safe and secure location.
Migrating Existing Databases to SQL Server 2000 Installing SQL Server 2000 Now that you have successfully backed up the ePolicy Orchestrator 3.0 databases, you can install SQL Server 2000. Use the installation or upgrade procedure that is recommended by Microsoft. At press time, the SQL Server and Microsoft Developer Network (MSDN) home pages were located at: SQL Server home page: http://www.microsoft.com/sql/default.asp MSDN home page: http://msdn.microsoft.com/default.
Migrating Existing Databases to SQL Server 2000 104 ePolicy Orchestrator™ software version 3.
Index A administrator user account, changing default password, 51 agent for NetWare system requirements, 21 agent for WebShield appliances system requirements, 22 agent for Windows system requirements, 18 audience for this manual, 7 AVERT Anti-Virus Emergency Research Team, contacting, 11 B beta program, contacting, 11 C Chinese reports, requirements, 18 client computer requirements on Windows 95, 18 configuring products via ePolicy Orchestrator (See product Configuration Guide) console requirements, 14
Index McAfee AutoUpdate Architect, requirements, 13 agent for NetWare, 21 K KnowledgeBase search, 11 Korean reports, requirements, 18 agent for WebShield appliances, 22 agent for Windows, 18 console, 14 database, 16 distributed repositories, 17 operating systems language support, L language support of operating systems, 22 language version of software, determining, 87 licenses for SQL, calculating, 16 M McAfee AutoUpdate Architect importing repositories, 82 McAfee Security customer contacts, 10 to 11
Index T technical support, 11 training web site, 11 troubleshooting list of messages, process, 91 92 U uninstalling ePolicy Orchestrator, 89 update repository requirements, 17 upgrade installation backing up databases, 59 calculating number of SQL licenses, downloading the software, 32 post-installation checklist, 78 pre-installation checklist, 26 remote consoles, 69 server and console, 60 upgrade web site, 11 16 V Virus Information Library, 11 virus, submitting a sample, 11 W Windows 95 computers req
Index 108 ePolicy Orchestrator™ software version 3.
