Simply deploy the agent from the ePO console.
It will take care of everything and turn the standalone clients into managed agents. No reboots are required for the agent installs. I've done it on production servers (by mistake) and not had any issues.
The only thing to consider is the policies on the clients. As pushing the agent onto the machines will override any custom local policies with the ePOs default policies.
1 of 1 people found this helpful
If none of your machines are in the current ePO server, then the best thing to do would be to setup a new/or upgrade to 4.6.4 ePO server. 4.5 goes end of life in December.
by standalone client- do you just mean VirusScan or the agent too? If so what version of agent?
You'd really need to get the structure setup and all the policies and tasks and check in the latest agent etc. first
You can do an AD sync to deploy agents (p126 in product guide) , or a GPO startup script etc etc
If you use the frampkg.exe (NOT the framepkg_upd.exe) that the epo server creates (once you checkin the software) (C:\Program Files (x86)\McAfee\ePolicy Orchestrator\DB\Software\Current\EPOAGENT3000\Install\0409) and deploy that, i'm pretty sure it will upgrade the current agent into managed mode (assuming it had a previous agent on it) and thus appear in ePO. easiest way is to test on one machine first.
ePO 4.6 also includes the guided deployment wizard (basically a dashboard on steroids that walks new users through the essentials)
That would help you enormously if you upgrade. Unfortunately that's a newer feature which does not exist in ePO 4.5
alex ....... wrote:
Deploying new ePo server??? if yes then go for the latest patch .it is ePo 4.6 patch 5.
Yes- just released (after i'd posted the version above)
Sometimes its good to wait a week or so incase issues arise, as in the past some releases have been revoked and had to have reposts.