1

https://kc.mcafee.com/corporate/index?page=content&id=KB76807

This can be added to ePO. Once the package has been added, don’t forget to wake the agents.

4 Spice ups
2

Thanks for the heads up!

3

Thanks Denis,

I’ve downloaded and checked in the Extra.DAT. But I have a question about how to deploy it as described on this page: https://kc.mcafee.com/corporate/index?page=content&id=KB67602

Deploy the extra.DAT

  1. Create a new ePolicy Orchestrator Agent Update task, and set the schedule to Run Immediately.
  2. Perform an Agent Wakeup call to send the new Update task to your clients and apply the extra.DAT.

Can anyone flesh out step 1 a bit?

4

I manually added it to the Master Repository and it pushed it out with the normal updates.

On ePO server: Menu->Software->Master Repository->Actions->Check in Package, Select Extra DAT

I am still pretty new to ePO, so there may be a different way to do this.

Cheers!

5

Thanks Brian,

I was able to check the DAT in with no problem, but just sending a wake-up to the agents wasn’t deploying the Extra.DAT.

I found the answer in (of all places) the ePo 4.6 Product Guide. It’s a two-step process:

First, under Menu → Policy → Client Task Catalog, Hit the ‘New Task’ button at the bottom of the page. Select ‘Product Update’ and hit ‘OK’. Name your new task (I chose Deploy Extra.DAT). See the attached picture for settings. Then save.

Next, Go to ‘System Tree’, and choose ‘Assigned Client Tasks’ at the top of the page. Click ‘Actions’ at the bottom of the page, and choose ‘New Client Task Assignment’. Choose ‘McAfee Agent’ in the first column, ‘Product Update’ in the second, and you new task (Deploy Extra.DAT) in the third, then click ‘Next’. Set Schedule Type to ‘Run Immediately’, and if you have many systems, you’ll want to check ‘Enable Randomization’ and set the interval over which you want ePo to spread out the deployment (Keeps you from flooding your network). Click ‘Save’.

*** Edit - the italicized text is not quite correct ***

The Extra.DAT should start deploying. You can check the progress under Menu → Automation → Server Task Log. The top entry (RunNow Task for …) should be the one you want.

*** Should be this ***

In ‘System Tree’, click ‘Systems’ at the top of the page. Select the check box nest to ‘System Name’ to select all, then click ‘Wake Up Agents’. Now you can check the progress in your Server Task Log, as described above.

Easy-Peasy, and sooo instinctive.

deployExtra.jpg
deployExtra.jpg792×643 95.2 KB
6

Nice.

“I found the answer in (of all places) the ePo 4.6 Product Guide.” - I probably should be reading that!

I wonder why I didn’t have to create a new task, though. Much to learn, but I am digging it!

7

To be honest, I didn’t have to go through that many steps. Just uploaded to repository into current branch. Wake up agent and Virusscan got the Extra.dat

8

In general with ePO, nothing happens unless you tell it to. An explicit McAfee Agent client update task that also is configured for the extra DAT would work.

Global Updating, which is disabled by default, would also work. On LAN based systems, Global Updating will take care of everything without any extra work. However do NOT enable this without careful consideration of your network/bandwidth/topology.

In practice, I use a combination of Global Updating and client agent update tasks.

9

Again, didn’t do anything more complicated than what I posted. I’m assuming because I loaded it into the current branch, ePO treated it as an update (yes an Extra) and once I woke the agents, it was deployed. Maybe I’m missing something here.

10

I’m with Denis. All that I did was check it in to the current branch. I have been randomly checking machines, and they all have the extra DAT.