McAfee EPolicy Orchestrator 5.10.0 Installation Guide

2y ago
22 Views
3 Downloads
1.42 MB
100 Pages
Last View : 4d ago
Last Download : 4m ago
Upload by : Raelyn Goode
Transcription

McAfee ePolicy Orchestrator 5.10.0Installation Guide

COPYRIGHTCopyright 2018 McAfee, LLCTRADEMARK ATTRIBUTIONSMcAfee and the McAfee logo, McAfee Active Protection, ePolicy Orchestrator, McAfee ePO, McAfee EMM, Foundstone, McAfee LiveSafe, McAfee QuickClean, Safe Eyes,McAfee SECURE, SecureOS, McAfee Shredder, SiteAdvisor, McAfee Stinger, True Key, TrustedSource, VirusScan are trademarks or registered trademarks of McAfee,LLC or its subsidiaries in the US and other countries. Other marks and brands may be claimed as the property of others.LICENSE INFORMATIONLicense AgreementNOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THEGENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASECONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANY YOUR SOFTWARE PACKAGING OR THAT YOU HAVERECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEBSITE FROM WHICH YOUDOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IFAPPLICABLE, YOU MAY RETURN THE PRODUCT TO MCAFEE OR THE PLACE OF PURCHASE FOR A FULL REFUND.2McAfee ePolicy Orchestrator 5.10.0 Installation Guide

Contents1Installation overview7Which type of installation do you need? . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Single server installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Cloud services installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Cluster installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Upgrade installation workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102345Planning your installation13Considerations for scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Examples of organization size and network components . . . . . . . . . . . . . . . . .Factors that affect McAfee ePO performance . . . . . . . . . . . . . . . . . . . . .Internet protocols in a managed environment . . . . . . . . . . . . . . . . . . . . . . .Things to do before installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1314161717System requirements19System requirements and recommendations . . . . . . . . . . . . . . . . . . . . . . . .Software requirements and recommendations . . . . . . . . . . . . . . . . . . . . . . .Operating system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Supported virtual infrastructure software . . . . . . . . . . . . . . . . . . . . . . . . .Supported SQL Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configure TCP/IP access to the SQL Server . . . . . . . . . . . . . . . . . . . . . . . . .Supported Internet browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Agent Handler server requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . .SQL Server installation documented in this guide . . . . . . . . . . . . . . . . . . . . . . .Required SQL permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Supported SQL database user name and password formats . . . . . . . . . . . . . . . . . . .Port options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Automatic product installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Distributed repository requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .Supported products and known issues . . . . . . . . . . . . . . . . . . . . . . . . . .192021212222232424252525262727Installing McAfee ePO on a single server29Install McAfee ePO on a single server . . . . . . . . . . . . . . . . . . . . . . . . . . .29Installing McAfee ePO on a cloud server33Using an AWS server for McAfee ePO . . . . . . . . . . . . . . . . . . . . . . . . . . .Using a Microsoft Azure server for McAfee ePO . . . . . . . . . . . . . . . . . . . . . . .Port requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Configure the Microsoft Azure server for McAfee ePO . . . . . . . . . . . . . . . . . . . . .Install McAfee ePO on an Azure server . . . . . . . . . . . . . . . . . . . . . . . . . .Update McAfee ePO public DNS name . . . . . . . . . . . . . . . . . . . . . . . . . . .Manage your Agent Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Distributed Repository connections . . . . . . . . . . . . . . . . . . . . . . . . . . . .3333343536363637McAfee ePolicy Orchestrator 5.10.0 Installation Guide3

Contents6789Installing McAfee ePO in a cluster environment39Create the McAfee ePO application role . . . . . . . . . . . . . . . . . . . . . . . . . .Create the Client Access Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Add the data drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Install McAfee ePO software on each cluster node . . . . . . . . . . . . . . . . . . . . . .Create the Generic Service resources . . . . . . . . . . . . . . . . . . . . . . . . . . .Test the McAfee ePO cluster installation . . . . . . . . . . . . . . . . . . . . . . . . . .404041414344Setting up your McAfee ePO environment45Configuring your environment automatically . . . . . . . . . . . . . . . . . . . . . . . .Install products automatically on your McAfee ePO server . . . . . . . . . . . . . . . .Configuring your environment manually . . . . . . . . . . . . . . . . . . . . . . . . . .Things to consider before manual configuration . . . . . . . . . . . . . . . . . . . .Manual methods for adding systems to be managed . . . . . . . . . . . . . . . . . .Installing the McAfee Agent and licensed software . . . . . . . . . . . . . . . . . . . . . .Install product packages manually on your McAfee ePO server . . . . . . . . . . . . . .Deploy agents to your systems to be managed . . . . . . . . . . . . . . . . . . . .Deploy the McAfee Agent using a URL . . . . . . . . . . . . . . . . . . . . . . . .Deploying the McAfee Agent using third-party tools . . . . . . . . . . . . . . . . . . .Best practice: Using Active Directory to synchronize McAfee Agent deployment . . . . . . . . .Best practice: Adding the McAfee Agent to your image . . . . . . . . . . . . . . . . . .Add systems to the System Tree manually . . . . . . . . . . . . . . . . . . . . . .Complete your server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .Define proxy settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Enable software license . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Confirm that your systems are being managed . . . . . . . . . . . . . . . . . . . .Confirm that your protection software stops a sample threat . . . . . . . . . . . . . . .Confirm the threat response in McAfee ePO . . . . . . . . . . . . . . . . . . . . .What to do next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4545464646474949505051515354545454555556Upgrading McAfee ePO to a new version57Preparing your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Backing up McAfee ePO databases and directories . . . . . . . . . . . . . . . . . . .Make sure that your Windows Server has enough disk space . . . . . . . . . . . . . . .Make sure that the Windows 8.3 naming convention is enabled . . . . . . . . . . . . . .Product Compatibility Check tool . . . . . . . . . . . . . . . . . . . . . . . . .Upgrade checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Pre-Installation Auditor . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Prepare your SQL database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Verify your SQL Server environment . . . . . . . . . . . . . . . . . . . . . . . .Update your database server certificates . . . . . . . . . . . . . . . . . . . . . . .Upgrade your McAfee ePO software . . . . . . . . . . . . . . . . . . . . . . . . . . .Download and extract the software . . . . . . . . . . . . . . . . . . . . . . . . .Stop McAfee ePO services . . . . . . . . . . . . . . . . . . . . . . . . . . . .Stop Agent Handlers services before upgrading . . . . . . . . . . . . . . . . . . . .Start and complete the InstallShield wizard . . . . . . . . . . . . . . . . . . . . . .Upgrade your Agent Handlers . . . . . . . . . . . . . . . . . . . . . . . . . .Restart updates and verify the upgrade . . . . . . . . . . . . . . . . . . . . . . .Migrate SHA-1 certificates to SHA-2 or higher . . . . . . . . . . . . . . . . . . . . .Upgrade your McAfee ePO cluster server . . . . . . . . . . . . . . . . . . . . . . ting installation69Troubleshooting and log file reference . . . . . . . . . .Common installation messages with their causes and solutions .Log files for troubleshooting . . . . . . . . . . . . . .Installer logs . . . . . . . . . . . . . . . . .4McAfee ePolicy Orchestrator 5.10.0 Installation Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69. . 69. . 71. . 71

ContentsServer logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73McAfee Agent logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74AAdding an SSL certificate to trusted collection77Replace the server certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Install the security certificate for Internet Explorer . . . . . . . . . . . . . . . . . . . . . .Install the security certificate for Firefox . . . . . . . . . . . . . . . . . . . . . . . . . .777879BInstall Agent Handlers81CRestoring McAfee from a Disaster Recovery SnapshotDisaster Recovery Snapshot prerequisites . . . . . . . .Restore McAfee ePO software in a single server environment .Restore McAfee ePO software in a cluster environment . . .Restore Agent Handler connections . . . . . . . . . .DE. . . . . . . . .83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83838587Using McAfee ePO in FIPS mode89FIPS basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .McAfee ePO operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .The cryptographic boundary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Install McAfee ePO in FIPS mode . . . . . . . . . . . . . . . . . . . . . . . . . . . .Upgrade from an earlier FIPS-compliant McAfee ePO server . . . . . . . . . . . . . . . . . . .Restoring McAfee ePO server in FIPS mode . . . . . . . . . . . . . . . . . . . . . . . . .Verify that Agent Handler is in FIPS 140-2 mode . . . . . . . . . . . . . . . . . . . . . . .Verify that the Apache server is in FIPS 140-2 mode . . . . . . . . . . . . . . . . . . . . . .Verify that the application server is in FIPS 140-2 mode . . . . . . . . . . . . . . . . . . . .899091919292929393Remove the software95Uninstall McAfee ePO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Uninstall McAfee ePO from a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 95IndexMcAfee ePolicy Orchestrator 5.10.0 Installation Guide975

Contents6McAfee ePolicy Orchestrator 5.10.0 Installation Guide

1Installation overviewContentsWhich type of installation do you need?Single server installation workflowCloud services installation workflowCluster installation workflowUpgrade installation workflowWhich type of installation do you need?Install McAfee ePO software as a single-server installation or as a cluster, cloud, or upgrade installation.Each installation scenario includes a workflow and procedure. Planning your installation and reviewing systemrequirements are also part of the installation process.McAfee ePolicy Orchestrator 5.10.0 Installation Guide7

1Installation overviewSingle server installation workflowSingle server installation workflowBefore you can install McAfee ePO software for the first time, you must ensure your SQL Server software isconfigured for TCP/IP access and install a supported operating system on the McAfee ePO server.1Ensure your SQL Server is configured for TCP/IP access.2Download and extract the McAfee ePO software from ds/my-products.html or the McAfee download site using a grant number.3Verify the latest Microsoft updates are running on the SQL Server and the McAfee ePO server.4Run the setup utility on the McAfee ePO server to install McAfee ePO. As part of the installation process theMcAfee ePO Pre-Installation Auditor checks for compliance issues.5Choose a deployment method to deploy McAfee Agent.6Confirm that systems are managed by ensuring that McAfee Agent can successfully connect to McAfee ePO.Cloud services installation workflowSet up a cloud services account and configure your virtual environment to run cloud services with McAfee ePO.18Set up a cloud services account and configure these items: Virtual server to use as your McAfee ePO server Virtual SQL Server Security Group2Assign an elastic IP address to each virtual server.3From a management computer, use Remote Desktop to connect to the virtual McAfee ePO server.McAfee ePolicy Orchestrator 5.10.0 Installation Guide

Installation overviewCluster installation workflow4From McAfee.com, copy the McAfee ePO software to the virtual McAfee ePO server.5From the McAfee ePO server, run the setup utility.6Using a remote browser, log on to McAfee ePO using https:// elastic IP / DNS of virtualMcAfee EPO server : port .1 Update McAfee ePO Server Public DNS in Server Settings with elastic IP address or DNS of virtual McAfee ePOserver. Update Published DNS name or the IP address of Agent Handler (if any) with elastic IP address or DNS ofvirtual Agent Handler server. Create a McAfee Agent deployment URL or extract the McAfee Agent deployment package.7Choose a deployment method to deploy McAfee Agent.8Confirm that systems are managed by ensuring that McAfee Agent can successfully connect to McAfee ePO.Cluster installation workflowMcAfee ePO provides high availability for server clusters with Microsoft Cluster Server (MSCS) software.1Install Microsoft Cluster Server (MSCS) software on all your servers and configure these items: Shared data drive Quorum drive Failover groupMcAfee ePolicy Orchestrator 5.10.0 Installation Guide9

1Installation overviewUpgrade installation workflow2Configure shared storage.3Configure SQL Server and database settings.4Download and install McAfee ePO software on all servers.5Choose a deployment method to deploy McAfee Agent.6Confirm that systems are managed by ensuring that McAfee Agent can successfully connect to McAfee ePO.Upgrade installation workflowUpgrade your existing McAfee ePO software to a new version.1Download and extract the software to your McAfee ePO server.2Prepare the McAfee ePO server environment.The McAfee ePO Pre-Installation Auditor runs, checking compliance with all requirements.103Configure SQL Server and database settings.4From the McAfee ePO server, run the setup utility.McAfee ePolicy Orchestrator 5.10.0 Installation Guide

Installation overviewUpgrade installation workflowMcAfee ePolicy Orchestrator 5.10.0 Installation Guide111

1Installation overviewUpgrade installation workflow12McAfee ePolicy Orchestrator 5.10.0 Installation Guide

2Planning your installationTo use your McAfee ePO server effectively, McAfee recommends creating a comprehensive plan specific to yourenvironment.Considering the unique needs of your environment in advance can reduce the time it takes to get started. How many systems do you manage? Do you have systems located in one network or multiple geographic areas? Do you have any specific security needs, such as a firewall? Do you use Network Address Translation (NAT) in an external network? Do you have any bandwidth restrictions to remote network segments? Do you need to manage laptops that are connected to the Internet and outside the corporate network? Do you have multiple administrators with different permissions across different products, groups ofsystems, or different functions within the management console?ContentsConsiderations for scalabilityInternet protocols in a managed environmentThings to do before installationConsiderations for scalabilityYour ability to manage growth on your network depends on whether you install McAfee ePO on multipleservers, use multiple Agent Handlers, or both.You can grow your McAfee ePO infrastructure by moving the McAfee ePO SQL database to a larger and morepowerful SQL Server, adding more Agent Handlers, or increasing CPU and memory.With McAfee ePO software, you can scale your network vertically or horizontally. Vertical scalability — Adding and upgrading to bigger, faster hardware to manage larger and largerenvironments. Scaling vertically is accomplished by upgrading your server hardware, and installing McAfeeePO on multiple servers throughout your network, each with its own database. Horizontal scalability — Increasing the size of the environment that one McAfee ePO server can manage.Scaling horizontally is accomplished by installing additional Agent Handlers, all sharing the same database.Managed systems and serversThe number of systems your McAfee ePO server manages dictates the number and size of the servers needed.The number of managed systems also dictates the recommended server sizing needed to manage thesesystems.McAfee ePolicy Orchestrator 5.10.0 Installation Guide13

2Planning your installationConsiderations for scalabilityOption 1,500systems1,500–10,000systems10,000–25,000 25,000–75,000 75,000systemssystemssystemsVirtual McAfee ePO serverYesYesYesYesYesVirtual SQL database serverYesYesYesOptionalOptionalMcAfee ePO server and SQL Yesdatabase on the same serverYesOptionalOptionalMcAfee ePO server andseparate SQL databaseOptionalYesYesYesAdd distributed repositoriesOptionalOptionalYesYesAdd Agent Handlers (virtual)OptionalOptionalYesYesWe recommend one Agent Handler for every 50,000 systems.There is no upper limit on the number of systems McAfee ePO can manage. The main limitation is the SQLdatabase performance, specifically disk performance (IOPS - 10 per Seconds). You can scale the SQL database,add distribution repositories and Agent Handlers to manage more systems as needed.Examples of organization size and network componentsThe number of systems and products you manage, and the data retention period, determines the servercomponents you need to use McAfee ePO.These examples provide guidelines for determining your server component requirements based on the size ofyour organization. These guidelines provide the minimum requirements. To improve performance and allow forgrowth, McAfee recommends you exceed these requirements wherever possible.Example 1 — Fewer than 10,000 managed systemsIn an organization with fewer than 10,000 managed systems, you can reduce hardware costs by installing theMcAfee ePO server and SQL database on the same physical server or virtual machine (VM). You can use theMicrosoft SQL Express database if you have fewer than 1,500 managed systems. Microsoft doesn't allow theSQL Express database to exceed 10 GB, and the memory available for the SQL Express Database Engine islimited to 1 GB. The SQL database can be installed on the same server.You can move the McAfee ePO database to a dedicated SQL Server to increase the size of your environment.Figure 2-1 Fewer than 10,000 managed systems McAfee ePO network components14McAfee ePolicy Orchestrator 5.10.0 Installation Guide

Planning your installationConsiderations for scalability2Example 2 — 10,000–25,000 managed systemsIn an organization with 10,000–25,000 managed systems, with the Endpoint Security product installed, addingadditional products to manage can increase sizing recommendations. Adding distributed repositories (as shownin example 3), might be needed depending on WAN and the number of distributed systems.As your managed systems count increases above 10,000 managed systems, consider separating the McAfee ePOserver and SQL servers onto separate servers. For optimal performance, have the DB administrator operate andmaintain the SQL Server.1SQL Server2McAfee ePO serverIf you have the budget for additional server resources, exceed this recommendation for improvedperformance.Figure 2-2 McAfee ePO network components for 10,000–25,000 managed systemsExample 3 — 25,000–75,000 managed systemsIn an organization ranging from 25,000–75,000 managed systems on one McAfee ePO server, separate SQLServer, with only the Endpoint Security product installed and properly placed repositories to update contentand software.1SQL Server2McAfee ePO server3Distributed Repositories to store and distribute security content for your managed systemsFigure 2-3 McAfee ePO network components for 25,000–75,000 managed systemsMcAfee ePolicy Orchestrator 5.10.0 Installation Guide15

2Planning your installationConsiderations for scalabilityExample 4 — 75,000–150,000 managed systemsIn an organization ranging from 75,000–150,000 managed systems on one McAfee ePO server, separate SQLServer, additional Agent Handlers, and properly placed repositories to update content and software to theagents.1Separate Agent Handlers coordinate McAfee Agent requests between themselves and McAfee ePO. AgentHandlers require constant communication back to the SQL database. They check the server database workqueue about every 10 seconds to find which tasks to perform. Agent Handlers need a relatively high speed,low latency connection to the database and must not be distributed. We recommend one Agent Handler foreach 50,000 managed systems.For organizations with 75,000–150,000 managed systems, install an Agent Handler on the same networksubnet with the McAfee ePO server for redundancy, allowing the McAfee ePO server to manage agent-servercommunications if the connection to the Agent Handler fails.2SQL Server3McAfee ePO server4McAfee ePO distributed repositories store and distribute important security content for your managed clientsystems.Figure 2-4 75,000–150,000 managed systems McAfee ePO network componentsFactors that affect McAfee ePO performanceIt's important to know which factors affect the performance of your server and the attached SQL database.For example, a McAfee ePO server and database can manage up to 200,000 client systems with only theEndpoint Security product installed. But as you add more software products and clients, that same serverhardware can no longer provide the performance you expect.Consider these factors as your managed network grows and your security needs change.16 McAfee ePO server hardware SQL Server — This server is the main engine within the McAfee ePO infrastructure and affects theperformance of the McAfee ePO server, queries, dashboards, and McAfee ePO console. Number of software products installed — Each software product you install adds processing load on theMcAfee ePO server and the SQL database.McAfee ePolicy Orchestrator 5.10.0 Installation Guide

Planning your installationInternet protocols in a managed environment 2Number of managed clients and their Agent Handlers — These numbers are proportional to the McAfeeePO server and database performance. Each Agent Handler places these fixed loads on the database server: Heartbeat updates (every minute) Work queue checks (every 10 seconds) Pool of database connections held open to the database (two connections per CPU to the Event Parserservice and four connections per CPU to the Apache service)Internet protocols in a managed environmentMcAfee ePO software is compatible with Internet Protocol versions: IPv4 and IPv6.The McAfee ePO server work in three different modes: Only IPv4 — Supports only IPv4 address format Only IPv6 — Supports only IPv6 address format Mixed mode — Supports IPv4 and IPv6 address formatsThe mode in which your McAfee ePO server works depends on your network configuration. For example, if yournetwork is configured to use only IPv4 addresses, your server works in Only IPv4 mode. Similarly, if yournetwork is configured to use IPv4 and IPv6 addresses, your server works in Mixed mode.Until IPv6 is installed and enabled, your McAfee ePO server listens only to IPv4 addresses. When IPv6 isenabled, it works in the mode in which it is configured.When the McAfee ePO server communicates with an Agent Handler on IPv6, address-related properties such asIP address, subnet address, and subnet mask are reported in IPv6 format. When transmitted between clientand McAfee ePO server, or when displayed in the user interface or log file, IPv6-related properties are displayedin the expanded form and are enclosed in brackets.For example, 3FFE:85B:1F1F::A9:1234 is displayed as:[3FFE:085B:1F1F:0000:0000:0000:00A9:1234]When setting an IPv6 address for FTP or HTTP sources, no changes to the address are needed. But, whensetting a Literal IPv6 address for a UNC source, you must use the Microsoft Literal IPv6 format. See Microsoftdocumentation for more information.TLS 1.0 is disabled by default for communication to external servers, such as SQL Server. For more informationabout TLS support, see KB90222. This version of McAfee ePO requires enabling TLS 1.2 support on your browser.Things to do before installationBefore you start the McAfee ePO installation, make sure that you have the information you need for the stepsyou must take. Run the McAfee ePO Pre-Installation Auditor to reduce or prevent installation or upgrade issues. McAfee Product License Key (not required for evaluations) Microsoft SQL authentication requires one of these credentials: Windows authentication credentials — Domain credentials that have Database Owner (dbo) rights on theSQL Server SQL authentication credentialsMcAfee ePolicy Orchestrator 5.10.0 Installation Guide17

2Planning your installationThings to do before installation Destination folder for McAfee ePO software installation (required for Custom and Cluster installations) Installed SQL Server — Provide these details (depending on your configuration) on the DatabaseInformation page: 18 The SQL Server name or the SQL Server name with instance name The dynamic port number used by your SQL ServerIf you intend to restore the McAfee ePO server from a database snapshot, you must: Have previously restored the McAfee ePO SQL database using one of the Microsoft SQL restoreprocesses Know the server recovery passphrase used with your Disaster Recovery Snapshot records. Thispassphrase is used to decrypt the sensitive information stored in the SQL Snapshot recordsMcAfee ePolicy Orchestrator 5.10.0 Installation Guide

3System requirementsContentsSystem requirements and recommendationsSoftware requirements and recommendationsOperating system requirementsSupported virtual infrastructure softwareSupported SQL ServersConfigure TCP/IP access to the SQL ServerSupported Internet browsersAgent Handler server requirementsSQL Server installation documented in this guideRequired SQL permissionsSupported SQL database user name and password formatsPort optionsAutomatic product installationDistributed repository requirementsSupported products and known issuesSystem requirements and recommendationsMake sure that your environment conforms to all requirements and recommendations before installing McAfeeePO software.Run the Pre-Installation Auditor to make sure that your environment meets the minimum requirements for asuccessful installation. For information about downloading and using the Pre-Installation Auditor, see the tool'srelease notes.ComponentRequirements and recommendationsDedicated serverIf managing fewer than 250 systems, McAfee ePO can be installed on a pre-existingserver, such as a file server. If managing more than 250 systems, use a dedicated serverfor McAfee ePO.Domain controllers(Recommended) The server must have a trust relationship with the Domain Controlleron the network. For instructions, see the Microsoft product documentation.Installing the software on a Domain Controller is supported, but not recommended.File systemNT file system (NTFS) partition.Free disk space20 GB — Minimum.McAfee ePolicy Orchestrator 5.10.0 Installation Guide19

3System requirementsSoftware requirements and recommendationsComponentRequirements and recommendationsIP addressUse static IP addresses for McAfee ePO.Static IP addresses are recommended for McAfee ePO and Agent Handlers.McAfee ePO supports IPv4 and IPv6 networks.Memory8-GB available RAM minimum.Network InterfaceCard (NIC)100 megabit minimum.Ports Make sure that the ports you choose are not already in use on the server system.If using a server with more than one IP address, McAfee ePO uses the first identified IPaddress. To use more IP addresses for agent-server communication, create AgentHandler groups for each IP address. For more information, see KB56281. Notify network staff of the ports you intend to use for McAfee ePO and McAfee Agentcommunication.Processor 64-bit Intel compatible (Recommended) 4 cores minimumSoftware requirements and recommendationsMake sure that you have the required and recommended software installed on your server system beforeinstalling McAfee ePO.SoftwareRequirements and recommendationsMicrosoft updatesRecommended — Make sure that your Microsoft Windows andMicrosoft applications are running the latest updates.Turn off Windows updates before you begin installing or upgradingyour software.Microsoft Visual C 2010Redistributable Package (x64 andx86)Required — Installed automatically.Microsoft Visual C 2015Redistributable Package (x64 andx86)Required — Installed automatically.MSXML 3.0 and 6.0Required — Installed automatically.Security softwareRecommended. Install and update the anti-virus software on the server and scan forviruses prior to any installation. Install and update firewall software

4 From McAfee.com, copy the McAfee ePO software to the virtual McAfee ePO server. 5 From the McAfee ePO server, run the setup utility. 6 Using a remote browser, log on to McAfee

Related Documents:

McAfee ePolicy Orchestrator web API Scripting Guide McAfee ePolicy Orchestrator Log File Reference Guide These guides are available from the McAfee Support Website. Preface About this guide 8 McAfee ePolicy

users with installed McAfee Endpoint Encryption*, this solution provides an enabling framework to re-motely and securely unlock the hard drive. SOLUTION ARCHITECTURE McAfee ePolicy Orchestrator Deep Command is an add-on module that

Security Target McAfee, Incorporated v9 May 2007 CHAPTER 1 1. Security Target Introduction This Security Target (ST) describes the objectives, requirements and rationale for McAfee Host Intrusion Prevention (HIP) v6.0.2 and ePolicy Orchestrator (ePO) v3.6.1 (Patch 1). The language used in this Security Target is consistent with the Common

McAfee Drive Encryption made up of the encryption software installed on client systems and the managing component on the servers. It is deployed and managed through McAfee ePolicy Orchestrator (McAfee ePO ) using policies. A policy is a set of rules that determines how McAfee Drive Encryption software functions on the user's computer.

McAfee Management of Native Encryption (MNE) 4.1.1 McAfee Policy Auditor 6.2.2 McAfee Risk Advisor 2.7.2 McAfee Rogue System Detection (RSD) 5.0.4 and 5.0.5 McAfee SiteAdvisor Enterprise 3.5.5 McAfee Virtual Technician 8.1.0 McAfee VirusScan Enterprise 8.8 Patch 8 and Patch 9 McA

You also need to determine the number of McAfee ePolicy Orchestrator (McAfee ePO) /McAfee NAC servers required to protect your network. The Sensor is purpose-built for the monitoring of traffic across one or more network segments. For more information, see the McAfee Network Security Plat

McAfee Suite Installer Setup Guide Page 6 McAfee Suite Installer Configure the McAfee ePO Server Log in to ePolicy Orchestrator Log in with the User Name of Admin and the password that you designated during the installation. On first login, y

American Board of Radiology American Board of Surgery American Board of Thoracic Surgery American Board of Urology ABMS and 24 Boards (Consolidated) Cash, Savings and Investments by Board Total Liabilities: Deferred Revenue, Deferre d Compensation and All Other by Board Retirement Plans: Net Assets, Inv Inc and Employer and Employee Contributions by Board ABMS and 24 Boards Board, Related .