Mcafee clients not updating log file Pne on one video sex chat
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.
13 September 2007 Info Script Extracting catalog.z. 13 September 2007 Info Scheduler The task Deployment is successful 13 September 2007 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.
I've notice that asking the client to update via the task does'nt seem to work.Hope this helps--The Bug Guy 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 [126.96.36.1990] Computer name [ERH-80361] e PO server [ERHAVI01]View debug logs: Frame Svc current / previous, Na Prd Mgr current / previous Date and Time Type Component Message 13 September 2007 Info Agent Package uploaded to e PO Server successfully 13 September 2007 Info Agent Agent communication session closed 13 September 2007 Info Agent Agent received POLICY package from e PO server 13 September 2007 Info Agent New server policy was successfully merged 13 September 2007 Info Agent Enforcing newly downloaded policies 13 September 2007 Info Agent Agent Started Enforcing policies 13 September 2007 Info Management Compiling policies 13 September 2007 Info Agent Agent will connect to the e PO Server in 180 minutes and 0 seconds.HOW TO TROUBLESHOOT CLIENT UPDATE/DEPLOYMENT FAILURES The e PO 5.9 and 5.10 install guides have a section in them for Troubleshooting and log file reference information.NOTE: Always be sure the product versions you are installing are supported versions for the specific build of OS/platform you are installing on.