ENS Components Not Showing When Trying to Create a New Client Task

[tmelville]

Hi All- I'm trying to create a client task to deploy the Common Client 10.6.1.1206 and Threat Prevention 10.6.1.1273. I'm not seeing it on the drop down menu when trying to creat the task. Is there a step I need to do so these are made available for client tasks? Thanks-

[cdinet]

The products need to be checked into the master repository for them to show up in a task - not the patches, but full installs.

[tmelville]

Above is a snip of my repository. I need to check in the 'Install' of ESTP and the Platform? (190514) And these are obtained from downloads on McAfee as zip files?

Also, can I get rid of all these old patches and hotfixes and installs? My orgnization is at:

Agent 5.6.157
ENS Security Platform 10.6.1.1449
ENS Threat Prevention 10.6.1.1550

Unless there is a compelling reason, we don't need any other patches, installs, hotfixes etc for other versions. We've tested on a test group then rolled these out systematically. They are working fine for everyone.

[cdinet]

Yes, you can remove older versions from your master repository if you don't need them anymore.  Full installs go out through deployment tasks, but the patches and hotfixes should be pushed out in an update task.  So hotfix 190514 would need to be an update.  In your update task, just enable ens items under patches and service packs and it should then be pushed out as long as they are in the current branch.

[tmelville]

One other question- are hotfixes cumulative? I take it they are if we can delete older ones.

In my repository I have ENS hotfixes 181113, 190212 and 190514. Deleting 18113 and 190212 should be OK as long as 190514 is in the current branch?

Another question I had- we don't use the Endpoint Security firewall, nor Web Control. I tried deleting these but they came back after a Pull. Do we have to live with these extras even if we don't use them?

Thanks for your help, I definitely like having this as a support resource.

[cdinet]

You would need to ask the ENS team or check release notes to see if ENS hotfixes are cumulative to know for sure. 

A Master repository pull task should never bring in new products, only content updates - they aren't even located on the update site where the pull is getting data from.  Are you sure you aren't checking in a bundle again of ENS somewhere?  Check the audit log for when you see those items show back up.