Agent Handler in DMZ priority

[Jmac24]

We have a new agent handler in the DMZ which appears to be functioning as expected. I know that we can't wake up systems connected to that AH. If we wanted to do a run immediate client task to push an install or update, would that fail? 

Asking because we have the agent handler assignment rule set to use all agent handlers so there's about 10% of our systems connecting to the one in the DMZ, most are not remote systems. We typically use some run immediate client tasks to get old versions updated or run client task now if we find systems without an endpoint product.

[LKS · Accepted solution]

No it will not fail. Product deployment/update only requires pure communication between agent to server. If Agent is communicating, then deployment will work.

Was my reply helpful?

If you find this post useful, please give it a Kudos! Also, please don't forget to select "Accept as a Solution" if this reply resolves your query!

[cdinet]

A run client task now is preceded by a wakeup call to tell the client to come get the task.  So your best option is to use modify task on single system and assign it a run immediately client task.  It won't be immediate, but it will get it anytime between its last asci and next asci.  

One thing to consider, however.  If you have dxl deployed or the agent that has dxl integrated and are using dxl brokers, wakeups will then go through dxl instead of epo sending it directly to the agent that it may or may not be able to reach.  If the dxl client is talking successfully with the dxl brokers, then that eliminates inability to reach a client over a natted environment.

[Jmac24]

We're in the process of setting up a broker on the AH system in the DMZ, and have DXL deployed to all endpoints.

[cdinet]

That's good, then your run client task now should work with dlx connected clients.

[LKS]

Ahhh yes i totally forgot that DXL concept. @Jmac24  ensure you have DXL broker in place, because DXL client will communicate via DXL broker.