EPO doesn't "see" installed agents

[geniph]

I've manually deployed the ePO agent on a number of machines, because my "push" deployment did not work (ePO Server 3.0 to W2K machines). There's no indication in the Server Events as to why it didn't work, and the account used has local administrator permissions on all machines in those domains.

Even after manually installing the agent, and several days later, the ePO server still reports those machines as having no agent installed. I can see the agent in a browser by putting in their IP address and ePO agent port. WTF? I can't control the policies until the server "sees" the agents. What is going on???

One thing I suspect may be causing an issue is that, when I did the old version of the ePO server, I used a custom port for agent-to-server communication. When I did my installation of the new server, I forgot about that and used the standard port. Even force-installing the new agent does not appear to have changed the agent-to-server port. How the hell do I get this to change on my agents and get the server to recognize their existence???

 

[AVChap]

Have you checked under "Lost&Found" to see if those "missing" agents have actually reported back?

If they're still not there, change the account the the ePO Server Service uses to run to one with Domain Admin rights. This will allow you to "push" the agents to the workstations.

HTH,

AVChap
... WARNING: The Surgeon General says to take my advise at your own risk.

 

[geniph]

No such luck. They're not in Lost and Found, and the account(s) used to push (as well as the accounts used for the manual installs) had domain administrator rights.

The agents are there. The server just refuses to "see" them. It's very frustrating.

 

[VulcanFyr]

I cant figure out how to change the HTTP communication port. You can change the Agent wakeup call port through Server Settings. Do you see any type of agent communication with the server when using the browser?

 

[Grunty]

I had the same problem when I upgraded from epo 2.5 to epo 3.0.

The solution was to remove the worksations from the epo domain and re-add them, a bit time consuming if you have lots of machines and some of them aren't switched on, but it was the only way I could get it to work.

It seems that when epo is upgraded it may retain the computer lists, but it loses the link to the agent. The same thing happens if a machine is rebuilt from a ghost image. The agent may be there, but epo will not see it.

 

[Jaderzaaaa]

Same problem here.. and we did a clean EPO3 install.

For some reason i think the application isn't 100%
Sometimes if u wait long enough the mark appears next to the pc icon .. sometimes 2 hours,2 days.. god knows why.