Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

EPO Deployment

Status
Not open for further replies.

bulkmail

MIS
Jun 11, 2002
345
US
Hi,

Has anyone had a tough time deploying the 2.5 agents?
It seems that when I send an install most comps get it and report back (NT machines). How ever some install but don't ever report back. I see the install folder and the files on the remote machine.

Plus, has anyone set up a new Task for an update or an upgrade and subsequently crash the AV (Dr. Watson) or crash the comp itself?

Thanks,

BM
 
bulkmail,

I know when I initially deployed ePO 2.5.0 and created at least 2 AutoUpdate tasks for teh same VirusScan version (4.5.1), I would see Dr Watson errors on my client PCs whenever it was about to run the scheduled task. If I manually delete the task info from the clients, the PC would be fine until the 2 tasks are downloaded by the agent and enforced.

After I upgraded to ePO 2.5.1 (AKA ePO 2.5 SP1), the Dr. Watsons disappeared and I have created many tasks for the same AV software product and version.

As for the ePO Agents not reporting on NT machines, did you wait sufficient time (About 600 seconds) from when you deployed the agent and when you checked the inventory? If you roll out the ePO agent and want to find out when the agent is going to upload its info to the ePO Server, open up a web browser and type in PCNAME is the name of the PC and 8081 is the Agent Wakeup Call port.

Usually on a fresh ePO Agent install, doing the above will show a line somewhere that says " Agent will attempt to connect to server in: 106 seconds". The 106 seconds I have in my example is what is shown on my PC, but I have seen many PCs where it shows as high as 550 seconds.

Hopefully some of the info above may be of some help to you.
 
Hi yes deploying of agents takes some technic, my servers exist on virtual IP address and after I added the IP address in the host file, some agents managed to communicate back. I'm not able to get that URL But I noticed servers with IE 4, ie 5, are not able to communicate. Does IE version play a part too? Pls advise
 
IE version required is IE 5.01 SP1. The workstations should have at least this version. Safest is to update to IE 5.5

HTH, AVChap
... take my advice, I don't use it anyway!
 
BTW, you can manually push the agents to communicate to the ePO server by running this command:

C:\ePOAgent\cmdagent.exe /p

HTH, AVChap
... take my advice, I don't use it anyway!
 
Thanks for the feed back people. It's very helpful.

BM
 
Here's another one; Autoupgrade.
I did what the instruction says but the update fails. I am trying to update the engine to the lastest version from a share on a remote server but it fails. I renamed the SDAT to setup and I did extrcat the files for the zip file called autoupg.zip and copied them over. I am stuck with engine 4.70
Thanks,
BM
 
Make sure you've given sufficient rights to the shared folder. If you're using 9x, you probably have to make it a null session share.

HTH, AVChap
... take my advice, I don't use it anyway!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top