Epolicy 3.5 not updating VSE 7.1 Clients

[n1koolkat]

I am about to upgrade or epo server to 3.6 but have just noticed that several recently added clients in the current server have not updated since their PCs were reimaged. They still have engine 4400 with DATS dated back to 30 August 2005 (which was on the original image). The agent is communicating so i thought that the problem was that the VS software was corrupt. If i manually go to the PC, uninstall the VSE 7.1 and run the latest SDAT file, all is well. I've notice that asking the client to update via the task does'nt seem to work.

I have uninstalled VSE 7.1 and reinstalled via the epolicy console however using the task to update the DATs and SDATs doesnt appear to work. Has anyone encountered this and how was it resolved. (They are all patched with fix 13 again applied via the epolicy console)

 

[bugguy51]

The contents of the agent activity log will tell you why updates are failing. It generally lives at \Documents and Settings\All Users\Application Data\McAfee (or Netrowk Associates)\Common Framework\DB\Agent_(machine name).xml. My suspicion is that every update that occurs ends with an "unable to locate valid repository." In that case, it may be a corrupted Sitelist.xml, invalid machine authentication to the Domain the repository is located in, or just a snakey management agent. In the case of a bad agent, a force reinstall should resolve the problem. WORD OF CAUTION: if you're currently running CMA 3.6.0.453, DO NOT force a reinstall over the existing agent. That version had a bug and you'll end up cleaning up the agent install by hand--update to CMA 3.6.0.546 instead. Hope this helps--The Bug Guy

 

[n1koolkat]

Thanks for you input Buggy, however extracts from the logs do not indicate that there is a problem locating a valid repository. The last entry in from one of the PCs is as follows:

Version [3.5.5.580] Computer name [ERH-80361] ePO server [ERHAVI01]
View debug logs: FrameSvc current / previous, NaPrdMgr current / previous
Date and Time Type Component Message
13 September 2007 09:45:32 Info Agent Package uploaded to ePO Server successfully
13 September 2007 09:45:32 Info Agent Agent communication session closed
13 September 2007 09:45:32 Info Agent Agent received POLICY package from ePO server
13 September 2007 09:45:33 Info Agent New server policy was successfully merged
13 September 2007 09:45:33 Info Agent Enforcing newly downloaded policies
13 September 2007 09:45:33 Info Agent Agent Started Enforcing policies
13 September 2007 09:45:33 Info Management Compiling policies
13 September 2007 09:45:33 Info Agent Agent will connect to the ePO Server in 180 minutes and 0 seconds.
13 September 2007 09:45:33 Info Management Enforcing Policies for VIRUSCAN7100
13 September 2007 09:45:33 Info Management Enforcing Policies for EPOAGENT3000META
13 September 2007 09:45:33 Info Management Enforcing Policies for EPOAGENT3000
13 September 2007 09:45:33 Info Management Enforcing Policies for ePolicy Orchestrator Agent
13 September 2007 09:45:33 Info Scheduler Added a new task Deployment to Scheduler's task list
13 September 2007 09:45:33 Info Agent Agent finished Enforcing policies
13 September 2007 09:45:33 Info Agent Next policy enforcement in 15 minutes
13 September 2007 09:45:34 Info Scheduler Scheduler: Invoking task [Deployment]...
13 September 2007 09:45:34 Info Script Checking update packages from repository ePO_ERHAVI01.
13 September 2007 09:45:34 Info Script Initializing update...
13 September 2007 09:45:34 Info Script Verifying catalog.z.
13 September 2007 09:45:34 Info Script Extracting catalog.z.
13 September 2007 09:45:34 Info Script Loading update configuration from: Catalog.xml
13 September 2007 09:45:35 Info Script Can't get uninstall command from plug-in area.
13 September 2007 09:45:35 Info Script Can't get uninstall command from plug-in area.
13 September 2007 09:45:35 Info Script Verifying VS710Det.McS.
13 September 2007 09:45:35 Info Script Verifying VS710Det.McS.
13 September 2007 09:45:35 Info Script Update Finished
13 September 2007 09:45:35 Info Script Closing the update session.
13 September 2007 09:45:36 Info Scheduler The task Deployment is successful
13 September 2007 09:45:36 Info Scheduler Scheduler: Task [Deployment] is finished

Everything appears to be okay however the PC still appears to be running engine 4400 with dats 4462. There are also no entries for the current signatures in the registry

 

[bugguy51]

What you're looking at there is one cycle of your Deployment task. That ran okay, but all it's supposed to do is install client applications. You need to search the log for a run of your update task (search by task name as it appears in your ePO task list)--it will appear in the first line of the task invocation (i.e., Scheduler: Invoking task [DAT Update-WS]...). Read all the way through to the end of the task (i.e., Scheduler: Task [DAT Update-WS] is finished) and it will tell you where the update task failed. BTW, the log is also published from the local machine on port 8081, so you can view it remotely in HTML without browsing to the machine. Syntax for that is:

explorer

http://machine-name:8081/agent_machine-name.xml

The Bug Guy