Am I able to install McAfee Agent on a Server not connected to our domain?

[wlampert]

We have a server not on the domain. Want to deploy an agent to it but obviously can't through ePO. I did that you can simply download the McAfee agent and run the frameworkpackage.exe to install it. My question is will it automatically find and show up in our ePO server?

[Dutchman39]

Absolutely. You will just have to either:

PULL install it form the Server

- or -

PUSH install it from ePO, referencing local admin creds on the target device

(I do this all the time)

[wlampert]

I don't understand what you mean by Pull or Push?

I can't push it from the ePO server since the server is not recognized because it is not on the domain.

Are you referring to manually installing it on the server then doing a "collect and send props"?

[wlampert]

Also, do I just download the latest McAfee Agent package from my downloads online or do I want to copy the FramePkg.exe that is on my ePO server:

<System Drive>\Program Files\McAfee\ePolicy Orchestrator\DB\Software\Current\<Product Id>\Install\0409

[kmc]

if you want to install it on standalone you can download from site, else download it from epo and install (make sure that your system is able to connect to epo if you want to manage the machine from epo)

[kmc]

even you can install it from epo by using the IP addressee of the non domain machine, end point should not be domain machine only.!

[wlampert]

How do you install it from ePO by using the IP Address?

[wlampert]

If it just download the agent package and install it on the server, how does it automatically know to connect specifically to my ePO?

[wlampert]

And when I say download the agent package - I mean going out to McAfee's Product Downloads page > inputting Grant Number > and downloading from there. And I missing something?

[Dutchman39]

PULL install - log onto the serve you want to run M/A and install the file manually.

PUSH install - via the ePO console. For a non-domain machine, the easiest mechanism would be add the IP address of the destination system (this is also useful for dealing with DNS issues), and for using credentials, reference the remote machine name as the domain.