Mountain Lion (10.8) has been in developer preview for a few months (will be released this week), what is the current support level for McAfee Security for Mac.
Currently I'm seeing application hangs (other apps, iTunes, Office) when it is installed. Also hang on restart or shutdown:
unmount of /home failed (45)
After talking with support yesterday, Security for Mac 1.2 is supported on Mountain Lion.
Security for Mac 1.2 requires McAfee Agent 4.6 patch 2 which went RTW today. Hope that helps.
Is it necessary to upgrade all clients to 4.6P2, or can you just upgrade the Macs? I dread the notion that I'd have to initiate an entire ePO/VS product upgrade job on every single device/machine just to accommodate a single OS - of which we have none yet installed.
So, can you just:
... without affecting clients on Windows, Linux, etc?
It is not neccesary to upgrade all clients to MA46P2, only the Mac clients where you plan to install VSM 9.2.
Because the Client packages for all platforms are different, you dont have to worry about upgrading Non-Mac clients.
Just update the MA extensions in ePO.
So your plan looks good. By the way, the VSM extensions for 9.2 are the same as for 9.1 so if you already have the 9.1 extensions, you dont have to import the extensions again.
As stated the McAfee Agents for the 3 platforms are separate check-in items and extensions so updating the Mac one will not impact the Windows or Linux systems. However... if you only want to update the agent on specific Mac systems you need to be careful in how you check it in. If you want certain Mac systems to continue running the older version then you need to check the new version into the Evaluation branch and then change their deployment tasks to update from there instead of the Current. Otherwise as soon as you add it to the Current branch all of your Mac systems will start updating to it even though you haven't updated your deployment tasks. I found that little bug by mistake recently...
Also wait to add in the VSM package until after the MA has deployed. I noticed the same little bug as above with it in that if you check it in Mac systems will start updating to it even if you don't tell them to. My deployment tasks were still listed as the old version yet they all grabbed it like it was a normal hotfix update on their own instead of waiting for a deployment task.
We're having a couple issues:
Please keep in mind. According to the below KB. If you are using a the custom option for Desktop Firewall you will need to modify the policy under Rules to Allow all connetions. Otherwise, there is a chance that Desktop Firewall will block incoming connections. This must be done before checking in the Desktop Firewall exetension.