Incomplete ENS upgrade from Sept. to Nov.

[nashcoop]

I've been upgrading W10 systems from ENS Sept 2021 release to the November 2021 release.  I have 500 systems that only upgraded Threat Prevention to 10.7.0.3210, but Security Platform still reports in EPO 10.7.0.3012, and ATP still reports 10.7.0.3183.  A screenshot of the task that's applied to the systems has been attached to this and shows Platform (3132) listed first for installation, TP second (3210), and ATP third (3252).  How do I end up with 500 systems reporting to EPO that they only upgraded TP to 3210, and how do I correct the problem?

[awbattelle]

Here is how to fix it.

Create indvidual tasks for each thing. except for the paltform.

You actually DON"T NEED to have a task for the ENS Platform. Installing any "blade" component, will also install the platform by default. So. make 2 tasks, One for TP, and the other for ATP. Set the to deploy immediatly. All your problems wil go away. I promise.

-Cheers!

[nashcoop]

Thanks for the advice.  Although, it begs the question why McAfee provides a separate installation package for the Platform if it gets installed by default with Threat Prevention?  One of the nice things about VirusScan was it existed as a single package, and ENS seems overly complicated by making it three or four (if you include firewall) separate packages.

[awbattelle]

Well, I too have noticed when running our ENS Task, which contains TP and the host firewall, that many times, we see just TP (and the platform) install without the firewall. If we examine the "Edit Policies on a Single System" on a target machine, we will see that "Task Up-To-Date" = True. This means that the client thinks it has already run this task (Even if ALL the products did not install) and will NOT attempt to run the task again unless it changes scomehow. By deploying each product as a single task, we avoid this issue. AND since you willbe running these as new tasks, the clients will dutifully process them.

Yes, I see your point. We SHOULD be able to deploy and mutitude of products with a single task, and this is how the engineers desgned it. That said, (Like many well intended and engineered features) It doesn't always work. Oh BTW, if my reply was helpful, please press the Kudos button.

Cheers!

[nashcoop]

Just to clarify...  Since I have 500 systems with the November release of Threat Prevention, September release of Platform, and September release of ATP the recommended solution is to create one task to deploy the November release of Platform, and a second task to deploy the November release ATP.  Is that correct?

[awbattelle]

Yes, that should work for you. You may also want to create a task for TP deployment if you are having an issue with that too. Normally TP will also deploy the platform at the same time. however, if you need to deploy a later version of the platform than TP comes with, you would need to create a separate task for that as well. Separate tasks assure that the system will process it, without "dumping" subsequent products in the task..

-T