Skip to main content

We're looking at McAfee Endpoint Security for Mac 10.2.1 and it comes with four components that have to be installed in order:




  1. McAfee Agent (MA). The 1990's style install.sh script that you have to wrap and trigger via postinstall script in PKG.

  2. McAfee Threat Prevention for Mac (ENSM10_TP) installer PKG

  3. McAfee Threat Prevention for Mac (ENSM10_HF1159589_TP) Hot Fix

  4. McAfee Firewall for Mac (ENSM_FW) installer PKG



I guess they still have the old timer in the corner updating the 20 year old script (item 1) that has an embedded/encoded installer. #facepalm



I'm posting to see if anyone tested this. We've got deployment covered. But looking for any gotchas. So we can test and have an idea of any known issues. Happy to shout back with anything we run into as well.



FWIW, I joined their forum and the most of the feedback seems to be cries for help on how to uninstall. :)



TIA,
Don

I'm sure you found your answer already, but in case not... someone with access to the McAfee ePO web console will need to log in and generate a McAfee Agent installer for you and download it, then give it to you. It will be a zip file, that you extract, and then that will be an install.sh file. Once you have that file on a Mac, to install the agent, you run sudo sh install.sh -i. If upgrading, sudo sh install.sh -u. Normally, if you run -i, and the agent is already installed, it will detect this, and run the upgrade anyway. Obviously, if deploying via Jamf, it will run as root, so no need to use the sudo in front of the commands. Not sure how necessary the "sh" is in front of install.sh, but that is how McAfee has it documented.

Thank you @MichaelBlower Once thats done, would it just allow them to upgrade the rest of the parts via EPO or do I need to package and push those also via a Policy? Current systems Are on 10.14.6 and they want to take them to Big Sur, with the McAfee Agent and parts upgraded to Big Sur compatible versions (10.7.6 Agent)

Hey @Stubakka so, you could do it either way. You could deploy the updated products via the McAfee ePO server, or you could package and deploy via the Jamf server. In my experience in the past, deploying via ePO works really well, if the local firewall is turned off on the client. Maybe this has been fixed by now, but with the firewall on in the past, my machines would never get any of the deployments. I haven't run in to this same problem with Jamf.



As of right now, McAfee Agent is at 5.7.2, and Endpoint Security for Mac is at 10.7.6.

I deployed McAfee via Jamf by creating packages using Composer and deployed configuration Profile to allow extension and full disk access but still, I have to allow extension manually from System Preferences --> Security & Privacy --> General. Here Iattached my configuration details and scripts I used and please suggest anything missing or changes required.



#!/bin/bash



sudo /Library/Application Support/mcafeeapp/McAfee_SH/install.sh -i



## Wait 20 seconds

sleep 20



sudo installer -pkg /Library/Application Support/mcafeeapp/McAfee_TP/McAfee-Threat-Prevention-for-Mac-10.6.7-ePO-client-package-RTW-108.pkg -target /



## Wait 20 seconds

sleep 20



sudo installer -pkg /Library/Application Support/mcafeeapp/McAfee_ATP/McAfee-Adaptive-Threat-Protection-for-Mac-10.6.7-ePO-client-package-Release114.pkg -target /



## Wait 20 seconds

sleep 20



sudo installer -pkg /Library/Application Support/mcafeeapp/McAfee_DLP/DlpAgentInstaller.pkg -target /



## Wait 20 seconds

sleep 20



sudo installer -pkg /Library/Application Support/mcafeeapp/McAfee_MCP/McpDistribution.pkg -target /



#sleep 300



## removing complete packages after installation.

#sudo rm -r /Library/Application Support/mcafeeapp



#if [ -e /Library/Application Support/mcafeeapp ];then

#echo "mcafeeapp folder is exist."

#else

#echo "mcafeeapp folder was removed."

#fi


















Reply


Terms & ConditionsCookie settings