If TIE wont be use nor TIE providers then the only benefit with that scenario will be the ability to send wake up calls via the DXL Broker, this might come handy when you place a broker with a public IP and you want to wake up your clients over the internet, more info on
Server to Agent communication (wake-ups):
Is there an advantage in "threat detection" communication between agents?
If an external AH is in use, what is the advantage of having a DXL Broker externally available also? Just to have another avenue of communications available?
Mcafee Agent is the bridge between the ePO server/Agent Handler and the point products installed on the end nodes, it doesnt have any threat detection capabilities, is not designed to do that, for example ANS and ATP will have those capabilities.
Having a DXL broker available externally allows you to manage those nodes that wont have any means of communicating to your internal network indeed
DXL has no threat capability's, understood...but would DXL communications have an advantage with threat detection communications between nodes?
SO, in this scenario, the External DXL Broker and External AH would have the same functionality, right?
My purpose with this post is to try to justify DXL Brokers/DXL Communications in our environment. Is there any?
Hello User38911914 ,
For mainly ePO use, DXL can offer a near real time messaging framework that ePO can leverage to perform wakeup calls and run client task now operations. DXL is also required for MAR/EDR integration if you have any plans for that and is used by Mvision ePO in the cloud to perform local operations like AD sync.