McAfee Agent 5.6 - Software Manager (ePO 5.9.1)

[jround]

How come in Software Manager within ePO 5.9.1 which is updated daily there is not yet an entry for McAfee Agent 5.6? (I have manually checked in the agent package etc. from the downloads site for now but not the extension yet due to a known issue with PIP)

Also, why would Agent 4.8 and 5.0 entries show up when the earliest Agent version in the repository is now 5.5?

e.g :-

https://ibb.co/BZdTmH0

[Hem]

I can see MA 5.6 in both ePO 5.9.1 as well as in 5.10.

Make sure that server task 'Download Software Product List ' is running.

[jmcg · Accepted solution]

I had same issue as @jround but since today i can now see the McAfee 5.6.0 with HF1264214 on ePO 5.9.1 catalog.

I thinks is due to the recent CVE found in all McAfee Agent, they made a new package (HF1264214). which is visible now.

[Olsen]

i had noticed the same my colleagues has write before. Since today i saw the MA 5.6.0 with HF xxxx in the Software manager.

If i tried to install it about a product deployment task on my test-systems, it will be delivered to the systems but the installation will be set to pending. The actually installed version of MA is 5.5.1.388.

Does anyone know what is wrong here? Does anyone have hints for me what i can do here.

thanks in Advanced#
best Regards
Olsen

[jmcg]

Installation of 5.6 with HF work great on 5.5.1 (just tested).

Little tips from me : Never use Product deployement page on ePO to deploy package, use client task product deployement to install any product 😉

[Olsen]

Thanks for your tip!
Until now i doesn't had any trouble with installing any package about the product deployment. the only diffrence i saw is that product deployment activate all by ePO supported OS as default. Choosing the OS for which the product deployment will be, would be an interesting feature for further version of ePO.

I think a great benefit of product deployment is that i can stop and change the task immediately and i get a quick view of the progress on installations.

Best Regards

Olsen

[cdinet]

One of the things about using product deployment is that it depends also on a response from the system.  When a new agent is installed, there has to be a restart of the agent services, so the stopping of the services stops that response from returning to epo.  Other product installs don't require a restart of the agent, so those responses are received.

So for agent deployments, use a client task instead.

[Olsen]

Ok, i understand what you are meaning. But until now it had works very fine.
Today i have noticed that the product deployment task has an problem with the command-line options. it seems that he has problems to interpret the following commandline option:

"l*v"C:\Install\LOG\McAfee"

When i delete this command-line option , all is working fine.

Were anything changed in the spelling of the parameters?

[cdinet]

Command line parameters with the agent have never really worked - there are built in commands for logging (and other parameters) already - it logs to windows\temp\mcafeelogs directory with verbose logging. 

[Olsen]

Unfortunately it seems so that it doesn't work anymore. On older version it had have works very fine. i would be happy it will give an solution for this issue, because "c:\Temp" will be often deleted without thinking and then all logs are away. on this cause i had choose an other path to save my install logs.

May it be, that -l -v "<path> instead of /l*v "<path>" works?