Then, what is the difference between doing a manual installation (as we do) and deploy it from the epo console? I don't know about this task...
You can do a manual install with the framepkg.exe from the EPO server and it has all the embedded xml's etc, that are needed to communicate with EPO. That;s the same as deploying the agent from EPO.
The method we used was manually installing the "standalone" agent which means it will go out to the McAfee http site to get the updates and not the EPO server.
You can deploy the agent from EPO to have the agent communicate with EPO. (The agent gets reinstalled)
You can use the framepkg.exe /install=agent and that will also have the agent communicate with EPO. the framepkg.exe has to come from the EPO server.
The framepkg_upd.exe /install=updater method installed tha standalone agent therefore the system doesn't know the EPO server exists.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center