I am currently maintaining ePO 126.96.36.1995, & have just updated CMA to 188.8.131.529. When I update the agent on PC's the DAT's will not update. The agent log states that the PC is running the latest DAT. PC is running VSE8.0i patch 13. I have been able to resolve this by uninstalling/reinstalling VScan. Here is a copy of the agent log & McScript log.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Wednesday, 28 November 2007 9:18:05 AM Info Script Extracting PkgCatalog.z. Wednesday, 28 November 2007 9:18:05 AM Info Script Loading update configuration from: PkgCatalog.xml Wednesday, 28 November 2007 9:18:06 AM Info Script Verifying V2datdet.mcs. Wednesday, 28 November 2007 9:18:07 AM Info Script Searching available updates for DATs. Wednesday, 28 November 2007 9:18:07 AM Info Script Product(s) running the latest DATs. Wednesday, 28 November 2007 9:18:07 AM Info Script Verifying VSE850Det.McS. Wednesday, 28 November 2007 9:18:07 AM Info Script Verifying PatchTmpDet.McS. Wednesday, 28 November 2007 9:18:09 AM Info Script Update Finished Wednesday, 28 November 2007 9:18:09 AM Info Script Closing the update session. Wednesday, 28 November 2007 9:18:09 AM Info Scheduler The task Immediate DAT update is successful Wednesday, 28 November 2007 9:18:09 AM Info Scheduler Scheduler: Task [Immediate DAT update] is finished
if i remember correctly, the datdet.mcs script reads the application plugins\Virusscan8000 key to see if the product is running the correct dat version. this reg key should be updated as part of the CMA update process.
it might check other keys too, i dont recall.
if the reg key is missing, then CMA will pass over VSE, and see if there are any other products that need updates, if not it will quit.
you can increase the logging level of the mcscript.log, but it becomes very hard to understand without an unencrypted copy of the .mcs script beside you, to step through the logic
it might be worth checking the reg key, to see if it is present on computers that are seeing the issue...
Thanks Boobah, unfortunately the reg key is there on the affected PC's. You mentioned datdet.mcs, but these PC's seem to be using v2DATDET.mcs. Don't know if that makes a difference. Do you know if there is a way of getting an unecrypted version of the MCS to see exactly what it is doing?
I have pushed the agent to only 4 PC's. They all have the problem. I was able to correct the issue by uninstalling & reinstalling VSE. Any new istalls work fine. There have been a couple of servers built since the agent update so they are getting brand new install. These are working fine.
The work around is not really acceptable as I have 5000+ nodes & don't want to do a re-install on all of them
We are planning to move to ePO 4 & VSE 8.5 early in the new year, so this is not a huge issue. I will only push the updated agent to any PC's that I need to as part of another project & update VScan on this limited number of PC's, which is only about 20 or so.