ePO Agent

[LXS]

Hi,
I am to despair. We are using ePO 3.0.2.236 (= SP2a) and i am not able to install the agent to the clients. It is the first time i using ePO and i want to deploy the agents over software distributing (f.e. NetInstall) and i using following command:

framepkg.exe /install=agent /domain=<domain> /username=<username> /password=<password

The user is domain admin and has admin rights on the client machines. The installation window is starting and finishing but, no Agent was installed. No Icon in the taskbar...sometimes. Sometimes the icon comes ...after a hour or two. It's strange! In this case, the agent is able to communicate with the Server but become no configuration from the server.

The installation over ePO-Server (pushing) was never successful.

The server is a Windows 2000 Server and the Clients have a Windows 2000 and Windows-XP OS.


Please, I need help.

Best regards,
Alex

 

[JimmyZ1]

Do you have your workstation names already in ePO? do a agent wakeup call, this should populate you directory. not to familiar with netinstall, but just try pushing it out with just the install=agent trigger with a /s for silent

Last cube on the left, next to the backdoor...

 

[LXS]

Hi,

i have already done a wakeup call. But nothing happens.
How can i see, if the agent was successfully installed?
(services?)

 

[JimmyZ1]

yeah, mcafeeframeworkservice, or find the log files
should be located under

\documents and settings\all users\application data\network associates\common framework\db

look at the .xml file should tell you what agent activity is taking place.

Last cube on the left, next to the backdoor...

 

[NickFerrar]

I'm doing a roll out currently, mostly the agents get pushed successfully - when they don't so far it's been one of the following issues:

1). ADMIN$ is shared on the client
2). User has removed Domain Admins from local admins (our users are devs so need local admin rights unfortunately)
3). Install gets stuck, generally a reboot and re-send of the agent has fixed this.
4). Lack of disk space

1 and 2 you can check by opening Computer Manager and connecting to the remote client. 3 I generally ntoice FRMINST process sitting there indefinetly. 4 is simple to check for as well.

I'm sure there's lots of other reasons.