1 of 1 people found this helpful
Which version of ePO are you using ?
ePO 4.6 is required as a minimum per McAfee support article KB73109
Thx rackroyd, that clarifies a lot, we're still running epo 4.5.
ePO 5.0 is on our roadmap.
But can I deploy in in the meanwhile via a remote ssh session?
In essence, yes. But you do need to be root.
The details are in the MA 4.6 product guide, and come down to this:
1 Copy the install.sh file from the ePO server file system to the target systems. For example, if checked in to the Current branch of the McAfee ePO software repository, for MAC the path on the ePO server of the required files is:
C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3700MACX\Install\0409
3 Open Terminal (or in your case ssh), then switch to the location where you copied the install.sh file.
4 Run these commands, giving root credentials when requested:
sudo chmod +x install.sh
sudo ./install.sh -i
If you've got a lot of them to install, it's much easier to do the deployment after ePO upgrade.
Separately, please note that ePO 4.5 reached end of life Dec 31st 2013. I'd strongly recommend you get ePO upgraded before then to maintain a supported status.
Thx again, you're certainly bringing me closer to the solution.
That only leaves me the question on how to get the "install.sh" file from windows to the mac.
I tried with the "scp" copy command via ssh but it seams to have dificulties with UNC paths (\\epoRepository\Current\EPOAGENT3700MACX\Install\0409)
After some googling I bumped into an article explaining to use "smb:" to access UNC shares
but this results into a popup window on the mac requesting for an account with permissions to that path (while the ssh session is started with an account with permissions?)
It's more in the realms of the OS & network than McAfee software so it's hard for me to comment on what is best there. One suggestion might be you host and copy the install.sh to an internal ftp site ?
There's plenty of free small ftp servers for Windows and/or mac i'm sure.
Just a thought. Your company security rules will also dictate what can & can't be allowed in this respect.
FYI: Succeeded in copying & installing the agent remotely
I've used the securecopy tool from putty pscp.exe to copy the install file.
The rest was done via ssh using the manual install instructions.