We are finally upgrading our McAfee ePO server so we can run the version that's compatible with El Capitan. I was able to get the install.sh from the server and manually installed it on some test 10.10.5 Macs without problems. In a Policy I'm using a script that automatically determines whether the -i or -u switches need to be used and it works great. However I did notice a few minor errors at the end so I commented those lines out and decided to run it again on the same Mac to see if it treats it as an upgrade (to the same version). I flushed the log on the policy and ran it again via Self Service and it almost immediately erred. The error indicated that the file can't be found to copy the install.sh to /Library/Application Support/McAfee/ This is very unusual because I just used that exact same policy to install it 5 minutes earlier. I rebooted and still got the same error. I decided to manually copy the .pkg file that contains the install.sh to the desktop and run it from there to see what happens. EXACT same problem! Now I know this pkg is good because I just used it this Mac and a couple others. I'm starting to think something in McAfee is blocking the installation of the pkg so I run the uninstall.sh script and remove everything. but I notice that /Library/Application Support/McAfee/ is still in place. I tried deleting it but the OS won't let me! I went into terminal and tried sudo rm -Rf on that folder and I get "permission denied"! The permissions are 775. WTF? I restart the computer and then I'm finally able to delete that folder.
What I've concluded is that this new version of McAfee (10.1.0) does something to protect the /Library/Application Support/McAfee/ folder so much that not even root can do anything with it until you completely uninstall AND restart the computer. At first I thought this was SIP gone haywire but then I remembered that this was a Yosemite Mac.
This makes me wonder how future upgrades or even re-installations are going to work since the install.sh goes into that folder, but once we're running the new version, that folder is protected from EVERYTHING. Clean installations work and upgrades from 2.3.0 work, but doing anything that equates to re-installing this new version fails every time.
Does anyone know how this is supposed to work on the new version?
