ePO Client installing but not working

[mizzy]

Hi There,

I have a problem where by the ePO client is not running correctly on a small but significant percentage of my Windows XP workstations.

These problem clients are NOT receiving any dat updates and none of the scheduled tasks are being downloaded to these problem clients.(There is a folder which conatins scheduled tasks and its empty)

These problem clients are appaearing in the console so this seems to say that the initial install is working. But once installed they refuse to update dats or fixes.

I have configured port 82 as the client-server communication port. Telnet seems to prove that this port is open. Are there any other ports used in the client-server communication? Perhaps its as simple a solution as that, open a port.

Regards

 

[VictorySabre]

Hi Mizzy,

From within the ePO Console, select the name of one of the PCs that appears to be having problems with DAT updates, then select the Properties tab on the right hand side of the window, and then expand System Information.

If you look at the Last Update entry, check and see if the agent is even communicating with the ePO Server. If the date/time appears to be off, try and Agent Wakeup Call on the client PC and then refresh the Properties tab and see if the client information changes.

We want to verify that the agent is even communicating first and then use that to try and isolate where the problem may be occuring at.

 

[mizzy]

Many thanks for your help VictorySabre,

I should have advised that my ePO server is 360 (no pacthes) and that the majority of my ePO clients are 3.5.580.
I am piloting VS85 and ePO client 360 at the moment and even this does not resolve the problem, but lets stick with 8.0 and 3.5.580 to avoid confusion.

I checked the last update date and it says todays date.
I did try the agent wakeup but that did not work.

I deleted one of the problem machines from the console but it has not appearred back in the console.

I checked various log files but perhaps this one is the most interesting is this one (taken from a Spanish machine)

c:\Documents and Settings\All Users\Datos de programa\McAfee\Common Framework\Db\Agent_<PCNAME>.log

it contains the following entries

20070605103204 I #3212 Logging Enforcing policies
20070605103204 I #3212 Manage Enforcing policies
20070605103204 I #3212 Script Enforcing policies
20070605103204 I #3212 Updater Enforcing policies
20070605103204 I #3212 UsrSpCt Enforcing policies
20070605103204 I #3212 Sched >>--CSchedule::EnforcePolicy
20070605103204 I #3212 Sched <<--CSchedule::EnforcePolicy
20070605103204 i #3212 Agent Agent finished Enforcing policies
20070605103204 i #3212 Agent Next policy enforcement in 5 minutes
20070605103704 i #3212 Agent Agent Started Enforcing policies
20070605103704 I #3212 Agent Thread time-out occured
20070605103704 I #3212 Manage Enforcing policies
20070605103704 i #3212 Manage Enforcing Policies for VIRUSCAN8000
20070605103704 I #3212 Manage CManage::EnforcePolicies() - FAILED - "VIRUSCAN8000" Error(-1207)
20070605103704 i #3212 Manage Enforcing Policies for EPOAGENT3000META
20070605103704 I #3212 Manage CManage::EnforcePolicies() - FAILED - "EPOAGENT3000META" Error(-1207)
20070605103704 i #3212 Manage Enforcing Policies for EPOAGENT3000
20070605103704 I #3212 Manage CManage::EnforcePolicies() - FAILED - "EPOAGENT3000" Error(-1000)
20070605103704 i #3212 Manage Enforcing Policies for ePolicy Orchestrator Agent
20070605103704 I #3212 Agent CePOAgent::EnforcePolicy priority=-2
20070605103704 I #3212 Agent Enforcing policies
20070605103704 I #3212 LstnSvr Enforcing Policies
20070605103704 I #3212 InetMgr IP address for ePO Server =<correct IP address of our ePO server>
20070605103704 I #3212 Logging Enforcing policies
20070605103704 I #3212 Manage Enforcing policies
20070605103704 I #3212 Script Enforcing policies
20070605103704 I #3212 Updater Enforcing policies
20070605103704 I #3212 UsrSpCt Enforcing policies
20070605103704 I #3212 Sched >>--CSchedule::EnforcePolicy
20070605103704 I #3212 Sched <<--CSchedule::EnforcePolicy
20070605103704 i #3212 Agent Agent finished Enforcing policies
20070605103704 i #3212 Agent Next policy enforcement in 5 minutes


I have read that the errors above mean that the package has not been checked into the repository. Well VS8.0 is in the repository as is the ePO client.

I'm always very wary about checking things into the repository as it always seems to do alot more than I expect (packages being replaced with the package being added).

Any help would be great.

Regards,

 

[VictorySabre]

Hi Mizzy,

I'm not familiar (have not encountered it on my end) with the error you've reported in your log. Since I haven't experienced it on my end, I probably would perform the following actions to see if any of it helps: (Best to try it on one of the PCs you can easily access locally)

Have you tried pushing out the ePO Agent reinstall on one of the problem clients? Assuming that doesn't work, have you tried uninstalling the ePO Agent, then VirusScan, then reinstall VirusScan followed by the ePO Agent?

The other thing I've seen on some PCs intermittently is that the end user would use up all the physical memory and the allotted pagefile until the system was critically low on available resources. The services still appear to be running, but agent communications would stop, DAT updates would fail, etc. Even though the user is no longer consuming those resources, I found that only after I got the user to reboot the PC does it correct the problem.

Let us know how things go.

 

[mizzy]

Thanks VictorySabre,

I've tried all your suggestions but still have a problem.
If I find a solutuion I'll post it here.

regards