[upgrade to 7.3.2032 - computer gets shut down after scheduled scan]

14 hours ago, JChurchill said:

I have upgraded about 140 endpoints since last night and none of them have rebooted automatically.  Do you have an assigned ERA (or SMC) client task that initiates a reboot when the endpoint reports it is needed?  (I do have one but it schedules the reboot for 1 AM.)

ah yes thanks for the hint! From last upgrade process i had a dynamic group with task to reboot the client!
I'm going to try it again without the autoassigned reboot task ^.^ oopsie
 

EDIT: I tried it again to upgrade to the newest version and everything went as expected.

[upgrade to 7.3.2032 - computer gets shut down after scheduled scan]

2 minutes ago, da_yoshman said:

I also updated 200+ Clients today from mostly 7.2.2055.0 to 7.3.2036.0 and didn't have the problem with an unplanned reboot.

I did it with 3 clients from 7.3.2032 to 7.3.2036 and all 3 did an unexpected reboot though the option for reboot were unchecked.

[upgrade to 7.3.2032 - computer gets shut down after scheduled scan]

I just tested the new version and updated my version through eset task.
Selected no reboot but eset reboots my client anyway... that is not acceptable for our enterprise - user should be given the option to reboot their client when they want to (or at least forced reboot in the middle of the night).