cancel
Showing results for 
Search instead for 
Did you mean: 

EPO 4.0 incorrectly listing clients as compliant

I cant update some of the clients on the network, but EPO 4.0 will show them as having been updated correctly.

The autoupdate  says the updates were not applied because the files were not in the repository. But some clients are up to date with the latest DAT's.

Labels (1)
14 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 15

Re: EPO 4.0 incorrectly listing clients as compliant

Make sure you do a pull and replication on ePO to make sure the ePO repositories are up-to-date. From there, check your client update tasks to make sure the correct products are selected. You can also create a new update task to see if that helps.

It's possible that the machines that are up-to-date simply went to the McAfee "fallback" repositories and updated from there.

Re: EPO 4.0 incorrectly listing clients as compliant

I did a manual Pull into the Master Repo. Even my own PC is showing that the DAT has not been updated since Sep. 2008, but EPO is showing the last time I ran an update manuallly, this morning.

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 4 of 15

Re: EPO 4.0 incorrectly listing clients as compliant

Are you looking at the "Last Update" time in ePO? This is the last time the agent connected to ePO and not when it updated the DAT.

Do the properties of the machine show the current DAT in ePO, but the VSE help screen on the local system show an out of DAT value? If this is the case, it's most likely VSE not refreshing the values. The VSE plugin queries the engine directly to get this information for ePO so it is as accurate as possible.

Re: EPO 4.0 incorrectly listing clients as compliant

OK then the Last update was only when it connected to EPO, but it is not updating the DAT. Both EPO and the local workstation are showing an out of date DAT, 5381.

I have tried reinstalling the VSE 8.7.0i, and deleting and reinstalling the agent, but it wont update.

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 6 of 15

Re: EPO 4.0 incorrectly listing clients as compliant

On one of the problem clients, try running an "Update Now". The window that pops up should tell you what repository the machine is going to and any error messages. This will also bypass any settings you may have in ePO created update tasks that would prevent the DAT's from updating.

From there you can check the ..\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Db directory for the McScript.log and the Agent_<machinename>.log for any further information as to why the update did not succeed.

Re: EPO 4.0 incorrectly listing clients as compliant

It is going to the correct repository, but just not installing the DAT. The files are in the C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework dir, but still not getting installed right.

here is from the McScript.log

2009-11-05 16:24:05    I    #3232    naInet    HTTP Session initialized
2009-11-05 16:24:05    I    #3232    imsite        Download to: C:\WINDOWS\TEMP\SiteStat.xml
2009-11-05 16:24:05    I    #3232    imsite        Download from: (ePO_SPLATAPPS) SiteStat.xml
2009-11-05 16:24:05    I    #3232    naInet    Open URL: http://128.1.5.3:80/Software/SiteStat.xml
2009-11-05 16:24:05    I    #3232    naInet    Trying to download using libcurl
2009-11-05 16:24:05    I    #3232    MueEep    Script progress details : Event Type = " 3" Progress = " 1"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:05    I    #3232    SessMgr    Using repository ePO_SPLATAPPS for script
2009-11-05 16:24:05    I    #3232    ScrptMgr    Loading and parsing:  C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\InstallMain.McS
2009-11-05 16:24:05    I    #3232    MueEep    Script progress details : Event Type = " 0" Progress = " 20"  Progress MAX = " 1"  Message = "
2009-11-05 16:24:05    I    #3232    ScrptMgr    Initializing update...
2009-11-05 16:24:05    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:05    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:05    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:05    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:05    I    #3232    ScrptUtl    Undefined variable bOk, assuming the value to be %%bOk%%
2009-11-05 16:24:05    I    #3232    ScrptUtl    Undefined variable bOk, assuming the value to be %%bOk%%
2009-11-05 16:24:05    I    #3232    MueEep    Script progress details : Event Type = " 3" Progress = " 3"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:05    I    #3232    ScrptMgr    Verifying catalog.z.
2009-11-05 16:24:06    I    #3232    MueEep    Script progress details : Event Type = " 3" Progress = " 4"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:06    I    #3232    ScrptMgr    Extracting catalog.z.
2009-11-05 16:24:06    I    #3232    MueEep    Script progress details : Event Type = " 3" Progress = " 5"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:06    I    #3232    ScrptMgr    Loading update configuration from: catalog.xml
2009-11-05 16:24:07    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:07    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:07    I    #3232    MueEep    Script progress details : Event Type = " 3" Progress = " 7"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:07    I    #3232    ScrptMgr    Verifying VSE870Det.McS.
2009-11-05 16:24:07    I    #3232    ScrptMgr    Setting the working dir as C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700
2009-11-05 16:24:07    I    #3232    ScrptMgr    Loading and parsing:  C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700\VSE870Det.McS
2009-11-05 16:24:07    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:07    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:07    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:07    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:07    I    #3232    ScrptMgr    Setting the working dir as C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework
2009-11-05 16:24:07    I    #3232    MueEep    Script progress details : Event Type = " 3" Progress = " 7"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:07    I    #3232    ScrptMgr    Verifying VSE870Det.McS.
2009-11-05 16:24:07    I    #3232    ScrptMgr    Setting the working dir as C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700
2009-11-05 16:24:07    I    #3232    ScrptMgr    Loading and parsing:  C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700\VSE870Det.McS
2009-11-05 16:24:07    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:07    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:07    I    #3232    ScrptUtl    Always use %%%%VariableName%%%% to dereference a variable.
2009-11-05 16:24:07    I    #3232    ScrptUtl    Continuing in backward compatibility mode for syntax ….
2009-11-05 16:24:07    I    #3232    ScrptMgr    Setting the working dir as C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework
2009-11-05 16:24:07    I    #3232    MueEep    Script progress details : Event Type = " 4" Progress = " 0"  Progress MAX = " 0"  Message = "
2009-11-05 16:24:07    I    #3232    ScrptMgr    Update Finished
2009-11-05 16:24:07    I    #3232    MueEep    Invoking EndUpdateDialog withTitle " Update Finished" Message " Please check the update log for more details." CountdownMessage " Auto close in" CountdownValue" 10"
2009-11-05 16:24:07    I    #3232    ScrptExe    Attempting to run OnExit section on current script
2009-11-05 16:24:07    I    #3232    ScrptExe    Cleanup section OnExit not implemented in the script
2009-11-05 16:24:07    I    #3232    ScrptExe    Attempting to run OnExit section on current script
2009-11-05 16:24:07    I    #3232    ScrptExe    Cleanup section OnExit not implemented in the script
2009-11-05 16:24:07    I    #3232    ScrptMain    Run script return code: 0
2009-11-05 16:24:07    I    #3232    ScrptMain    McAfee Update Engine is exiting with return code: 0
2009-11-05 16:24:07    I    #3232    MueEep    Invoking events withEventId " 0" Severity " 0" Productid " EPOAGENT3000" Locale " 0409" UpdateType " N/A" UpdateError " 0" New Version " N/A" Date Time " N/A" Script Id" 1097"
2009-11-05 16:24:07    I    #3232    MueEep    Deinitlaizing entry execution point
2009-11-05 16:24:07    I    #3232    MueEep    Deinitializing container
2009-11-05 16:24:07    I    #3232    ipcchannel    Closing IPC connection
2009-11-05 16:24:07    I    #3232    MueEep    Deleting container
2009-11-05 16:24:07    I    #3232    Thread    Exit program

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 8 of 15

Re: EPO 4.0 incorrectly listing clients as compliant

Is th after doing an "Update Now"?

Re: EPO 4.0 incorrectly listing clients as compliant

Yes, after doing Update Now.

dvo
Level 9
Report Inappropriate Content
Message 10 of 15

Re: EPO 4.0 incorrectly listing clients as compliant

I cant update some of the clients on the network, but EPO 4.0 will show them as having been updated correctly.

The autoupdate says the updates were not applied because the files were not in the repository. But some clients are up to date with the latest DAT's.

I cant update some of the clients on the network

how are you trying to update?

when you do it what makes you think it didnt update? as in what does the dat/engine show for the machine when you update versus what epo actually have in the repo?

"The autoupdate  says the updates were not applied because the files were not in the repository"

what items did that message actually say the update didnt happen on, extradat1000, vscandat1000...etc?

anything else besides engine and vscandat1000 should be ignored.