JRV 1 Posted February 14, 2018 Share Posted February 14, 2018 (edited) ERA 6.5. Scheduled an after-hours push install of 6.6.2072.2 over the previous version via ERA Client Task. The option to Automatically Reboot if Needed was set in the Task, but none of the computers rebooted. Why? Does it not reboot if a user is logged on (as likely they were)? Edited February 14, 2018 by JRV Link to comment Share on other sites More sharing options...
Administrators Marcos 5,071 Posted February 14, 2018 Administrators Share Posted February 14, 2018 That appears to be a known issue and is listed here: https://support.eset.com/kb5949/. Link to comment Share on other sites More sharing options...
JRV 1 Posted February 14, 2018 Author Share Posted February 14, 2018 Thanks, Marcos. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 14, 2018 ESET Staff Share Posted February 14, 2018 Please check my previous comment where I provided simple workaround for task configuration, using parameter REBOOT_WHEN_NEEDED=1. This will invoke the same behavior as will be automatic for future release of ERA. Link to comment Share on other sites More sharing options...
JRV 1 Posted February 14, 2018 Author Share Posted February 14, 2018 (edited) Excellent! Thanks Martin. Edited February 14, 2018 by JRV Link to comment Share on other sites More sharing options...
JRV 1 Posted March 7, 2018 Author Share Posted March 7, 2018 I added REBOOT_WHEN_NEEDED=1 to the Client Task that installed ESET File Security for Microsoft Windows Server v6.5.12014.1 on my servers last night. (The "Automatically Reboot When Needed" checkbox was also enabled, FWIW.) None of the servers rebooted. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted March 7, 2018 ESET Staff Share Posted March 7, 2018 Unfortunately this workaround won't work for server-based products until next release. Link to comment Share on other sites More sharing options...
JRV 1 Posted March 7, 2018 Author Share Posted March 7, 2018 Next ERA release? Next ESET File Security release? ETA? Thanks! Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted March 7, 2018 ESET Staff Share Posted March 7, 2018 Next EFSW release will enable you to use this workaround. Once both products are released, this workaround won't be required anymore. I will leave answer to ETA-part to @MichalJas I am not sure. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted March 8, 2018 ESET Staff Share Posted March 8, 2018 Both should be available towards the end of Q2, but please take this as a plan, that could change. Link to comment Share on other sites More sharing options...
plittlefield 0 Posted March 12, 2018 Share Posted March 12, 2018 I've got this on my Windows Server now when upgrading from 4.5 to 6.5... "ERA SoftwareInstallation: Installation need to allow reboot." ...so, what's the solution? Link to comment Share on other sites More sharing options...
JRV 1 Posted March 12, 2018 Author Share Posted March 12, 2018 Summarizing this thread: No solution for now, for ESFW. Have to reboot manually until the next ERA and/or EFSW are released towards the end of Q2. (-ish.) For ESET Antivirus, add REBOOT_WHEN_NEEDED=1 as an "Installation Parameter" in the installation Task. Link to comment Share on other sites More sharing options...
JRV 1 Posted April 4, 2018 Author Share Posted April 4, 2018 ESFW v6.6.2072.4 is now in the Repository. Does this version include the auto-reboot fix? Do I need to add REBOOT_WHEN_NEEDED=1 as an "Installation Parameter? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted April 4, 2018 ESET Staff Share Posted April 4, 2018 5 hours ago, JRV said: ESFW v6.6.2072.4 is now in the Repository. Does this version include the auto-reboot fix? Do I need to add REBOOT_WHEN_NEEDED=1 as an "Installation Parameter? Not sure what product you actually meant, as there does not seems to be EFSW of such version ... in case you meant EES/EAV, adding parameter REBOOT_WHEN_NEEDED=1 required. It will be required until new ERA Agent is available and installed on client machines. In case you actually meant EFSW, I don''t think support for this parameter will be available before upcoming major release is available. Link to comment Share on other sites More sharing options...
JRV 1 Posted April 11, 2018 Author Share Posted April 11, 2018 You're right; the filter was set for EAV; didn't notice that. Catches me every time. (IMO, browsing the repository for a product should automagically filter for that product.) Clarifying: "Major Release" = 7.x? ESFW, ERA, or both? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted April 11, 2018 ESET Staff Share Posted April 11, 2018 3 hours ago, JRV said: "Major Release" = 7.x? ESFW, ERA, or both? EFSW 7.x will add support for installation parameter REBOOT_WHEN_NEEDED which is crucial in this case. ERA Agent 7.0 will use this parameter automatically. This means that you will need both application in version 7.x for reboot to work automatically, or at least EFSW 7.x for workaround mentioned in this topic. If I recall correctly, both products will be release simultaneously, as was mentioned in previous comments. Link to comment Share on other sites More sharing options...
Recommended Posts