5.0.2122 --> 5.0.2126

Discussion in 'ESET Smart Security' started by jlpeifer, Aug 1, 2012.

Thread Status:
Not open for further replies.
  1. jlpeifer

    jlpeifer Registered Member

    Joined:
    Jul 5, 2012
    Posts:
    14
    Location:
    USA
    I've been waiting with some anticipation for the release of v5.0.2126 because of the BSOD problems I reported in version 5.0.2122 (https://www.wilderssecurity.com/showthread.php?t=327596). Today I noticed in the Remote Administrator console that all of my client machines are still running 5.0.2122. Does this mean that I'm going to have to manually push even minor core updates of ESET to all my clients every time they're released?

    Is there a way for this to happen automatically?
     
  2. Temp Member

    Temp Member Registered Member

    Joined:
    Mar 28, 2009
    Posts:
    263
    Location:
    Glasgow
    Why not use 5.2.9.1?
     
  3. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    Because 5.2.9 is Home version without business features.
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    I wouldn't recommend upgrading when a minor update is available unless you've experienced issues that the update addresses. Security software integrates deeply in the system so it's better to minimize potential risks with updates to the bare minimum.
    You can upgrade clients via ERA by selecting Remote Install -> Upgrade Windows Clients.
     
  5. jlpeifer

    jlpeifer Registered Member

    Joined:
    Jul 5, 2012
    Posts:
    14
    Location:
    USA
    Sorry for the delayed response... But yes, it's exactly because of a bug that existed in 5.0.2212 that was addressed in 5.0.2216 (a bug that was causing my client's computers to reboot randomly, see https://www.wilderssecurity.com/showthread.php?t=327596). I'm sure the app has gone through several more iterations of updates since my original post. I'll have a go at "Remote Install -> Upgrade Windows Clients". Thanks Marcos.
     
Thread Status:
Not open for further replies.