Page tree

Contents

If you are using McAfee ePO (ePolicy Orchestrator) to manage your endpoint software, you can integrate Endpoint and subsequently install it on your endpoint devices to redirect DNS traffic to BloxOne Threat Defense Cloud.

System Requirements

The Endpoint and ePO integration supports the following:

  • ePO 5.3 and 5.9
  • BloxOne Endpoint 1.7.0
  • Client platforms:
    • Windows 7 x86
    • Windows 7 x64
    • Windows 8 x86
    • Windows 8 c64
    • Windows 10 x86
    • Windows 10 x64
    • MAC OS X 10.10, 10.11, 10.12, 10.13, 10.14, and 10.15.

NOTE: For a successful installation, 20 Mbytes of free space is required. Additional space (up to 100 Mbytes) is necessary for storing log files.

Prerequisites

Before you deploy Endpoint in ePO, ensure that you complete the following:

  • Download the Endpoint Package (MAC OS X or Windows) downloaded from the Cloud Services Portal. For information see Downloading Endpoint.

NOTE: The signatures of the service binaries are generated with McAfee-provided certificate.

  • Open the customer_id_txt file that was part of the download and copy the customer ID. You enter this ID in the Command Line field when deploying Endpoint in ePO.

NOTE: Ensure that you save the customer_id_txt  file in the same folder as the Endpoint Package.

  • Install the McAfee agent on your client machine.

Deploying Endpoint in ePO

To deploy Endpoint in ePO, complete the following:


NOTE: The instructions given here for ePO are guidelines only. Please refer to the official ePO documentation for details.


  1. Log in to the Cloud Services Portal.
  2. Go to Administration -> Downloads.
  3. Select either the MAC OS X or Microsoft Windows package and download it to your system.
  4. Log in to your ePO console.
  5. Click the menu icon (upper left corner), and then click Master Repository in the Software section.
  6. On the Master Repository page, click Check in package.
  7. On the Check in package page, complete the following:
    • Package type: Select Product or Update (.ZIP).
    • File path: Click Choose file and navigate to the Endpoint package that you downloaded earlier, and then click Open.
  8. Once the check-in process is complete, double check the package information, and then click Save.
    NOTE: The package is signed by the McAfee certificates.
    The Endpoint package is now displayed in the Master Repository list.
  9. Click the menu icon, and then click Client Task Catalog in the Policy section.
  10. On the Client Task Catalog page, select Client Task Types -> Product Deployment, and then click the New Task button to create a client task for deployment.
  11. In the New Task dialog, ensure that Task Types = Product Deployment, and then click OK.
  12. On the Product Deployment page, complete the following and then click Save:
    • Task name: Enter a task name for this deployment.
    • Description: Optionally, enter the description for this task.
    • Target platform: Select the correct platform for your downloaded package.
    • Products and components: Select the Endpoint package and the corresponding action and language. In the Command Line field, enter this: CUSTOMER_ID=<customer id>. You can find the customer ID in the customer_id.txt file when you download the Endpoint package.
      Example:
       CUSTOMER_ID=12345678901234567890123456789012
  13. After you save the new task, go to System Tree in ePO.
  14. On the System Tree page, select the system that you have created under My Organization. If necessary, you can create a group to separate the MAC and Windows machines.
  15. Select the checkbox of the applicable system on the system list.
  16. From the Actions menu (at the bottom of the page), select Agent -> Run Client Task Now.
  17. On the Run Client Task Now page, select McAfee Agent -> Product Deployment -> <Your Task>, and then click Run Task Now.
  18. You can go to System Tree to monitor the deployment status. When the deployment is successful, ePO displays the “Complete” status.

Once the deployment  is complete, Endpoint is installed on the client devices that are managed through the ePO.

  • No labels

This page has no comments.