Overview The McAfee ePO Agent is required to use any of the McAfee enterprise security tools for Mac. It is installed using a script created by the McAfee ePO Server. (This script includes connection details unique to the ePO Server that creates it.) This article explains how to deploy and run the script on clients using a policy in the JSS. Procedure Note: If your JSS is hosted on a Windows server and you have certificate-based authentication enabled, logs may fail to submit to the JSS if you follow the procedure below. See the 'Additional Information' section for a workaround. Deploying the the McAfee ePO Agent involves the following steps: • Obtain the necessary McAfee components. • Build a package of the McAfee components.

• Add the package to Casper Admin. • Deploy the McAfee components and installation script. Note: Step 4 is different depending on which JSS version you are using. Follow the instructions for the appropriate version. Step 1: To obtain the necessary McAfee components: • Log in to a Mac with a local admin account.

• Create a directory for the script in the Application Support folder by executing the following command: sudo mkdir -p /Library/Application Support/McAfee/ • Download the install.sh script from your McAfee ePO Server. For more information, see the 'Install on UNIX-based and Mac systems' section of the McAfee Agent 4.8 Product Guide, available at: • Copy the install.sh script to the directory you created in step 2 by executing the following command: sudo cp ~/Downloads/install.sh /Library/Application Support/McAfee/ • Modify the permissions on the install.sh script as needed. • Modify the install.sh script to make it an executable script by executing the following command: sudo chmod +x /Library/Application Support/McAfee/install.sh • Open the directory you created in step 2 by executing the following command: sudo open /Library/Application Support/McAfee/ Step 2: To build a package of the McAfee components: Use Composer or a third-party packaging tool to build a DMG containing the script.

Tip: You can also access mysupport.mcafee.com from the Admin Console computer by selecting Start Programs McAfee McAfee Firewall Enterprise v8 Online. Product updates. Visit go.mcafee.com/goto/updates to download the latest Firewall Enterprise, Virtual. Appliance patches. Download IPS signatures and enable automatic signature. Manage SmartFilter using the firewall Admin Console. McAfee Firewall Enterprise 8.3.2 Product Guide 7.

For information about using Composer, see the Casper Suite Administrator's Guide. Step 3: To add the package to Casper Admin: Upload the package you just created containing the install.sh script to the JSS using Casper Admin. For more information, see the Casper Suite Administrator's Guide.

Step 4: To deploy the McAfee components and the installation script (v9.0 or Later): • Log in to the JSS with a web browser. • Click Computers at the top of the page. • Click Policies. • In the General payload, enter a display name for the policy. • Choose “Once per computer” from the Execution Frequency pop-up menu.

• Click the Scope tab and configure the scope of the policy. • Select the Packages payload and click Configure. • Click Add for the package you just created. • Select the Files and Processes payload and enter the following command in the Execute Command field: /Library/Application Support/McAfee/install.sh -i • Click Save. When the policy is run on clients, the ePO Agent will be installed and it will begin to check in with the McAfee ePO Server.

Step 4: To deploy the McAfee components and the installation script (v8.x): • Log in to the JSS with a web browser. • Click the Management tab.

• Click the Policies link. • Click Create Policy. Then, choose the Create policy manually option and click Continue. • Enter information about the policy and choose a trigger, execution frequency, and scope. For more information, see the Casper Suite Administrator's Guide.

• Click the Packages tab, and then click the Add Package link. • Locate the install.sh package and choose Install from the Action pop-up menu across from it. • Click Add Package(s). • Click the Advanced tab and enter the following command in the Run Command field: /Library/Application Support/McAfee/install.sh -i • Click Save. When the policy is run on clients, the ePO Agent will be installed and it will begin to check in with the McAfee ePO Server. Additional Information If you are deploying the McAfee ePO Agent using a JSS hosted on a Windows server with certificate-based authentication enabled, the policy must include a script with the following: #!/bin/sh/Library/Application Support/McAfee/install.4.6-current.sh -i sed 's//elp/g' For more information, see the Casper Suite Administrator's Guide.

I must be missing something for how to incorporate this into an imaging workflow (because it isn't working for me). If I understand correctly, you follow steps 1-9, and you'd have to create a new script (let's call it installepo.sh) with the following content: #!/bin/sh sudo /Library/Application Support/McAfee/install.sh -i Add both the package and your script to your Configuration and set this script to 'After'.

I did this, and it put the script into place, but did not install. Anybody got any tips? Hi All, I am using /Library/Application Support/McAfee/install.sh -i. Job gets executed but not seeing ePO installed. Following is the status of policy status.

How To Install Wifislax On Windows. Verifying DMG. Installing McAfee ePO. Closing package. [STEP 2 of 2] Running command /library/Application Support/McAfee/install.sh -i. Result of command: space required to copy archive is 33264500 bytes space available at mferCruyu is 56 bytes extracting archive to mferCruyu. Please wait 216+0 records in 216+0 records out 110592 bytes transferred in 0.000615 secs (179789329 bytes/sec) 32255+1 records in 32255+1 records out 16515022 bytes transferred in 0.099910 secs (165298955 bytes/sec) Archive: mferCruyu/package.zip error: expected central file header signature not found (file #3).

(please check that you have transferred or created the zipfile in the appropriate BINARY mode and that you have compiled UnZip properly) inflating: mferCruyu/MFEcma.dmg error: invalid compressed data to inflate inflating: mferCruyu/reqseckey. Error: invalid compressed data to inflate cp: mferCruyu/sitelist.xml: No such file or directory cp: mferCruyu/srpubkey.bin: No such file or directory cp: mferCruyu/reqseckey.bin: No such file or directory cp: mferCruyu/sr2048pubkey.bin: No such file or directory cp: mferCruyu/req2048seckey.bin: No such file or directory cp: mferCruyu/agentfipsmode: No such file or directory Could not find key data files. Installation cannot continue Any idea on failure? Thanks Nelson.

Is STEP 4 (deploy to Casper v9 or Later) correct? Items 10/11 in STEP 4 say: 10 - Select the Scripts payload and click Configure. 11 - Choose “After” from the Priority pop-up menu. I'm using 9.81 and when I click Scripts I would have to choose a script, but at no point have I been instructed to upload a script directly to Casper - or am I missing something? STEP 1 - 3 is fine, add the script to a directory, create a DMG and add this to Casper. I can think of ways to get the install.sh to run, but I thought it was strange that this seems incomplete [or I can't follow it correctly].

I was curious if the POST-FLIGHT or POST-INSTALL scripts within the DMG should be used to run the command, e.g: #!/bin/sh%1 -i. If you're deploying the additional firewall modules, you'll want to have the ePO Agent talk to the server immediately after the install, as indicated by 's script. The last command tells ePO Agent to talk to the server. #!/bin/sh ## Install agent /private/tmp/install.sh -i ## Start agent /Library/McAfee/cma/bin/cma start ## Wait 30 seconds /bin/sleep 30 ## Talk to server /Library/McAfee/cma/bin/cmdagent -P exit 0 PS, we noticed some folks are using '/P' in their scripts. For OS X the switch is '-P'. Couple questions regarding packaging this up and using composer. In the first step it says to create the folders and run terminal commands and place everything in place, then step 2 is to run composer, do I drag and drop the folders that just created and the script into Composer and then create the DMG?

Or would I want to run composer first to make a new snap shot? And then run the commands and then make the DMG? I realize i might be overcomplicating this - I'm just trying to understand the logic of the directions.

I wanted to follow up with this again as Im a little confused still on the package creation + deployment So i have install.sh on Library/Application Support/McAfee I drag and drop the install.sh into composer >create DMG >save as McAfeeAgent.dmg Do i still need to upload the install.sh into JSS or just the McAfeeAgent.dmg i created which points to Library/Application Support/McAfee/install.sh? And in the instructions in the Policy creation do I still add: /Library/Application Support/McAfee/install.sh -i it only says if the JSS is v8. My problem is that everything works without any errors, but the agent still doesn't show up on the target Mac, at least not in the GUI (in system preferences or menu bar), and in the McAfee admin console the Mac shows up there, but as 'unmanaged'. I've tried almost all of the solutions on this page. Hi and I was hoping someone might be able to help me out. As posted, we are also having the same issues on getting the McAfee Agent to successfully install on a managed Mac. (Tested installing by policy, and manually) After the installation completes, the ePO Policy fails to install the McAfee GUI Mac app (toolbar menu) LaunchDaemons and LaunchAgents do not get created for McAfee MSS folder does not get created in /Library/Application Support/McAfee Testing of the same /Library/Application Support/McAfee/install.sh on a unmanaged Mac: The Mcafee agent successfully installs, including the McAfee GUI Mac App, and successfully loaded the Toolbar menu.

All appears to be working fine, only difference is that this on a unmanaged Mac. Any advice, and assistance would be greatly appreciated. Thanks In Advance, Lee.

Incase it's useful, Checks to see if agent is installed and will; - Update if earlier agent version is found - Install if no agent found - Exit if same agent version is found #!/bin/sh INSTALLVERSION='504283' #if no agent then install CONFIGPATH='/etc/cma.d/EPOAGENT3700MACX/config.xml' if [! Snap shot before, copy file, then snap shot again. Locate your script on your computer.

Open Composer and make a new package. Snapshot the drive. When the scan is done waiting for you to do the install, copy the file to /Library/Application Support/McAfee/ on your computer. Go back to composer and snapshot the drive again. In the window will be the file structure for /Library/Application Support/McAfee/install.sh. Then put the script in with the package (click on the drop down next to the package name and right click on scripts and pick postinstall) Install agent /Library/Application Support/McAfee/install. Voter Id Card Form 6 Download Hindi Bihar. sh -i Wait 30 seconds /bin/sleep 30 Talk to server /Library/McAfee/cma/bin/cmdagent -p Clean up rm -f /Library/Application Support/McAfee/install.sh I dont run the 'start script' part as mcafee starts with the installer. We have an agent handler in the DMZ pre-populated in the install.sh so it phones home on or off net.

I also have not figured out what voodu we need to put it in the right folder of the system tree, mine also go to lost&found. McAfee changed their command line switches again for version 5. Switches are now lower case.for example to 'Collect and send properties to the ePO server', the command was /P. Then was switched to -P, and most recently got changed to -p. Would suggest putting this KB link into the article, else deployment will be risky. McAfee will enable all options by default until it can talk to ePO.so you kind'a want to set the switches to run immediately after install, or get calls about being unable to connect to the computer.

Relevant part of KB52707.