1 of 1 people found this helpful
MVT content is updated very frequently, may be every other day or two. Hence it is recommeded for you to configure a Common Updater pull task to bring down the latest content from the "Common Updater" website automatically and push the latest content to the client regularly.
Latest version of ePO-MVT Content is 188.8.131.52.
"I checked the walkthrough guide and can see there is a policy to force a health check even if mvt content is out to date which suggests its out of date on the particular machine but the the content appears to be the same (184.108.40.206). I am not sure against it is actually checked?"
Content Ageing policy is set to 2 days by default,which means MVT will flag the content is out of date if the content on particular end node was updated 2 days earlier with respect to the current date. However one could change the "Content Ageing" policy to the desired number of days, this can be modified using the ePO-MVT policy. Content Ageing policy is available under the "User Permission" tab of the ePO-MVT policy. Refer the attached screenshot.
"One confusing thing is a release note for version 5.2.2. which I do not understand at all as I downloaded the packages just days ago and this release note refers to May."
Standalone MVT is available for non ePO users and the product version is MVT 5.5.2, you may have stumbled on the Read Me for the Standalone version. You are having the latest version of ePO-MVT. You just need to keep the content updated as mentioned above.
Let us know if the above answered your queries.
Do revert if you still have queries, Happy to Help you!
Thanks a lot for your quick reply. That explains it
Glad to hear that
Can this thread be marked as "Answered" ?