Jump to content

Auto-update Policy Not Working


CMS
 Share

Recommended Posts

Hi folks,

I have an auto-update policy which is on and set to apply to all clients.

I just spotted on my dashboard that all endpoints are out-of-date, most are on an older version of 9 e.g. 9.0.2032.6 rather than 9.0.2046.0.

Why are they not updating?

Also, should auto-update update the agent as well?

Thanks

Link to comment
Share on other sites

Thanks. Is there a reason that the dashboard shows it as out-of-date?

Where can I check to see which versions are genuinely out-of-date?

Link to comment
Share on other sites

  • 3 weeks later...
  • Administrators

Automatic update to v9.0.2046 is available, we've started distributing it about a week ago. Clients with auto-update enabled should gradually upgrade to the latest version automatically.

Link to comment
Share on other sites

Sure would have been nice if Eset would have chose a different notification in the console other than red to indicate a endpoint needs to restart to apply the update. Seeing a bunch of endpoints with a red status waiting for a restart ...the endpoints with serious issues with a red status get lost in all the restart clutter

Link to comment
Share on other sites

Now that it is being distributed, how long does that take? The whole process is not very clear for people needing to manage a lot of endpoints. 

Link to comment
Share on other sites

  • Administrators

It may take about 2-3 weeks until all clients get updated. Of course, this depends on users' reports and in the event of an issue we would stop the distribution.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...