Jump to content

Rebooting and future changes


Guest
Go to solution Solved by Marcos,

Recommended Posts

Hi

 

With the new update noticed it needs a reboot again, but it isn't a major update? will there be a time when this isn't required for minor or maybe even major updates. Also how risky is it to update and the leave the reboot for out of hours. Noticed some computers only recommended a reboot others say it must be rebooted,

hxxp://repository.eset.com/v1/com/eset/apps/business/ees/windows/v8/8.0.2039.0/ees_nt32.msi.changelog.html

 

Link to comment
Share on other sites

  • Administrators
  • Solution

A so-called uPCU update from older Endpoint v8 will be available in a month after the release. This is to ensure that the new version has been available for long enough to discover possible issues should there be any.

In order to update Endpoint to the latest version automatically when available, set the program update mode to "Auto update" in the advanced update setup via a policy. Prior to installing the new version, an administrator will have to approve EULA in the ESET PROTECT console.

image.png

As to your question re. the restart after update, we recommend doing it asap. If you have upgraded from a recent version of Endpoint, no issues should occur if you reboot after a couple of hours. Issues could occur if you upgraded from an old version (e.g. v5 or v6) and let the machine without a restart. This is because of the combination of very old drivers loaded in memory and the latest ekrn.exe running.

Link to comment
Share on other sites

Does setting update mode to Auto-update mean the endpoints will update to the latest releases (e.g. 8.0.2039) without having to create a task? I created a task to update to 8.0.2039 and about half of my endpoints still required a reboot. Much better than all requiring a reboot, but still.

And a month seems a bit long.

Link to comment
Share on other sites

  • Administrators
1 hour ago, FRiC said:

Does setting update mode to Auto-update mean the endpoints will update to the latest releases (e.g. 8.0.2039) without having to create a task?

Correct. There is currently a 30-day period after the release before we make uPCU available. This is to prevent millions of computers worldwide to upgrade to the latest version automatically which would be a problem if a bug affecting a lot of users was discovered after the roll-out. Even Microsoft doesn't push the latest version of the OS to all users immediately.

Currently if you want to upgrade asap, you'll need to send a software install task to clients which may require a reboot after upgrade.

Link to comment
Share on other sites

2 hours ago, Marcos said:

Correct. There is currently a 30-day period after the release before we make uPCU available. This is to prevent millions of computers worldwide to upgrade to the latest version automatically which would be a problem if a bug affecting a lot of users was discovered after the roll-out. Even Microsoft doesn't push the latest version of the OS to all users immediately.

Thanks for the info. Will try auto-update next time. Incidentally my latest update to 8.0.2039 did not go smoothly. I've done the upgrade task countless times without any problems but this time a number of computers (out of 100+) could not complete the update. Had to remove (some even in safe mode) and reinstall.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

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