MVT content for version 1.1.1 has gone from version 84 in my master repository to 37 from McAfee as of today. My master repository is no longer downloading the content updates. Any reasons for the change in the content update numbering? Will this content be automatcially updated or do I need to delete the previous/evaluation versions? Been this way for several months. I've downloaded and attempted to update the extension/installation packages, but the system replies back it's already at these versions.
I'm not sure what would cause that: I've checked and the version on the commonupdater site is still 84.
If you delete the MVT content package, and run the pull task again, does that have any effect?
Tried your suggestion, it still pulled 84. From the Support Site, Tools, ePO-MVT the latest is:
|ePO-MVT ClientContentUpgrade Package|
I'm just confused as to which version number should be showing up in the master repository, and if I should be manuall downloading and checking in the lower version number.
I've spoken to the team responsible, and they're aware of the issue: it should be fixed either today or Monday, hopefully, with a new version posted that brings everything back into sync.
unfortunately the issue is not fixed yet, our ePo continues to download MVT Content 18.104.22.168 after the Pull Task.
I also tried to check-in manually the latest content update from support.mcafee.com:
But it seems to be bugged.
I tried to run a health check using that content package but the result is always the attached one.
As you can see we already have McAfee Virusscan 8.8 Patch 4 and the On-Access Scanner is not disabled.
How can we trust in this tool?
Thank youMessaggio modificato da failover on 23/04/14 3.30.12 CDT