Node-RED Flow: AD Computer and ePO System Compare 1.0.0

This flow pulls all systems from ePO and creates a set difference with all systems from AD.

This flow pulls all systems from ePO and creates a set difference with all systems from AD. Each AD computer is evaluated based on FQDN and Hostname to identify if it already exists in ePO. The same process occurs for all systems in ePO with AD. The result is an HTML table with all of the results.


Prerequisites

  • The OpenDXL and McAfee ePolicy Orchestrator (ePO) DXL modules have been added to the Node-RED palette.
  • A DXL client has been configured in Node-RED (see Client Configuration).
  • An ePO DXL service is running and available on the DXL fabric. If version 5.0 or later of the DXL ePO extensions are installed on your ePO server, an ePO DXL service should already be running on the fabric. If you are using an earlier version of the DXL ePO extensions, you can use the ePO DXL Python Service.
  • The Node-RED DXL client is authorized to invoke the ePO DXL service, and the user that is connecting to the ePO server (within the ePO DXL service) has permission to execute the "system.applyTag" remote command (see Client Authorization).
  • Following Node-RED modules installed in palette:



The output appears as follows:




Here is the Node-RED flow content for this solution: