you should be able to just run the MSI package as per the SMS docs through anything.
For info on how to deploy a mcafee agent without EPO, It's best to talk to your professional services team.
Why wouldnt you just let EPO do this for you though?
I saw this KB article and it only speaks about the agent install, and nothing about the client install? Is the agent install the only msi I need to install? We do use ePO to deploy, however there are cases at low bandwidth sites that the application will be installed locally, as to not impact the site.
Thanks for the quick response.
I have a related question -- how can you force a WSUS style deadline for the required reboot after the dlp agent install? And how do you get the dlp agent to install without giving up a splash screen indicating that it's complete? A default product install task on ePO leaves a pretty prominent DLP Agent install finished click to reboot screen up for the user who'll invariably become a bit paranoid about it all.
(for this reason I too am considering a push outside of ePO)
The McAfee Agent policy in EPO allows the option to disable prompting the user to reboot. You can also set the MA to restart the machine automatically, if needed, after install has completed.
The McAfee Agent will need to be installed as well as the DLP agent's msi for EPO policy enforcement. You can use the msiexec command from Simon's article provided to perform the manual install of the DLP agent. The McAfee agent can either be pushed from the EPO server or manually installed from the framepkg.exe installation package.