Updating point products on external devices

[Aj-richer]

Hi guys,

I have an agent handler in place so that machine can report back and give alerts in case anything is found, it also helps us keep track our estate.  With that being said i am unable to send client taks to these machines for the reason i believe is they sit behind their personal firewalls which 443 inbound would be blocked.

So my question - The agents communicate back to the ePO as per schedule every hour or so.  Is there a way i can make is so that when these agents call back to the ePO it is able to pick up a policy / task that will tell the agent to check for available missing products / patches and then initiate the download from client side hence avoiding the inbound 443 issue.  

I expect this would work much the same as when i go to one of these machines communicating through the agent handler, right click on the mcafee shield and click "Update Security" from the options it goes through and checks avaialbale patches.  I cannot find the way for the agent to initiaite this themselves?

Is this possible or am i approaching this the wrong way?

Many thanks

Aj

[cdinet]

Check the product guide for epo on setting up client tasks.  In the system tree at my organization, go to the assigned client tasks tab.  Click on new client task assignment, choose McAfee agent, update, then create new task for updating content and patches.  Schedule it as desired.  You can also set up tasks for deploying new products, etc. as a product deployment task.  Patches normally are pushed out through update tasks, where upgrades to new versions or new products are deployments.  Release notes for each product will indicate what install method is needed.

[cdinet · Accepted solution]

Additionally, see KB58818 - wakup calls to vpn (or any natted device) cannot be performed.  The epo server and agent handlers listen on 443, agents listen on 8081, 8082, 8083.  If you are using run client task now to run updates, that will fail as it requires the same type connectivity to the agent as a wakeup call would, over the agent listening ports.  The agent then responds to epo on 443. 

Assigned client tasks are tasks that get sent to the client with normal asci same way policy updates do.  The tasks are then local to the system and invoked by the agent at the scheduled time.  This process does not require any wakeups or contact from the epo server to initiate it.  In this way, then the clients will reach out to epo or any distributed repositories for the necessary content.