JRV

So this was just released today: [NEWS8134] ESET Windows products compatibility with Windows 11 Good enough!

Thanks, and noted, but holding out for seeing it listed on KB2893 first! If Marcus is correct, it will probably be updated soon.

Windows 11 is not mentioned in [KB2893] What operating systems are ESET products compatible with? (Business users). I know it was just released, so I'm not surprised, but we've been holding off on a hardware refresh until now. Any idea when I should check back for confirmation of ESET Endpoint AV support?

Thanks, Martin; have now upgraded to ESET Complete.

I pushed ESET Endpoint AV v8.1.2037.2 over v8.1.2031.0 from EP v8.1.1223.0. In the Software Install task, "Automatically reboot when needed" is enabled. All of the computers installed the update, but none of the computers restarted.

Running EP 8.1 on-prem, ESET Server Security 8.0 and ESET Endpoint AV 8.1. Does our license allow us to migrate to EP Cloud at no expense, or does EP Cloud require a purchase? Thanks!

Martin, that's the most arcane way to determine a version number that I've seen in...well, maybe ever! What if I lose my ESET version number secret decoder ring?😨 Thanks!

Thanks, for your reply, Martin. So going forward, when the RSS Feed on the Dashboard announces a new ESMC version, I should disregard it unless I get an update notification from ESMC. That raises another question. How do I know I'm running 7.0.72.0? Nothing in ESMC Help/About reports that version number.

Current ESMC Help/About: ESET Security Management Center (Server), Version 7.0 (7.0.577.0)ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) I've not received an update notification yet to update ESMC to v7.0.72.2. I'm logged on as local Administrator; not a permissions issue. No Update Product command is available on the Help menu, as per https://help.eset.com/esmc_admin/70/en-US/update_product.html. What is the correct procedure for me to use to update ESMC to v7.0.72.2?

I misinterpreted what was happening. THe server DID restart last night for MS updates. But if the log is written each time the ESET installer runs, then that's what I'm seeing, not a result of the computer restart. The installer runs each week because my site visits are on Wednesdays. Therefore, we want updates (from ESET or MS) to install on Wednesday early AM (02:00 or 03:00) so that if there are any issues, I can address them upon arrival at 08:00. We install on servers EXCEPT hosts at 01:00, hosts at 02:00, so guests can finish before hosts reboot (thereby rebooting guests). Since the system is small, we don't worry much about 8 servers downloading and installing simultaneously. If there's no new version available, MSI discovers that (I assume...) and aborts the install. The WSUS model is how ESMC should work. ESMC should show when a new version is available, then I approve it for install, and it gets pushed on a schedule I set. I don't see a way to do that in ESMC, but with limited time at the site, I'm trying to get as close to that as I can. If there's a way to accomplish that without adding more steps, I'm all for it!

was it a clean install or an upgrade? Upgrade if an upgrade, from which version? 7.0.12014.0 How does the task execution window look inside ESMC? Details? The one that shows failure was actually successful...it's on the current version. Can you share the screenshot of either the machine protection status from ESMC or from the machine locally? Where is the "pending reboot" displayed? Too late now; all have been rebooted. But in the Computers node in ESMC, they had "!" status and Details showed that they needed a reboot, were identified as "Security Risks" on the Dashboard, etc. Can you ship us the agent trace log, and install log from the affected machine? One would be enough. Attached. Software-install.log appears to be overwritten during each bootup. The servers restarted last night for MS updates, and all were restarted at least once before after the install, so you're not seeing the log current at time of installation; don't know if it will tell you what you need to know. ESETLOGS.zip

@MichalJ, thanks. I now remember that the reboot DID work the first time I pushed the first 7.0 File Security release after upgrading to ESMC 7.0. The reboot did NOT work when I upgraded from the first 7.0 File Security release to the 2nd, which also occurred after upgrading ESMC from whatever it was to 7.0.577.0. I used the same Client Task for both installs; only thing that changed was the selection from the Repository. I will be back at this site Wednesday, 19 Dec, and will gather the information you requested at that time.

I have a Client Task in ESMC 7.0.577.0 to install ESET File Security for Windows Servers 7.0.12016.0 on 8 servers. It ran overnight last night and installation was successful. However, while the option to "Automatically reboot when needed" was enabled in the Client Task, the reboots did not occur. I now have 8 servers which ESMC reports I need to reboot, and will need to do so after hours tonight, manually. I had the same issue with ERA 6.x and posted on this forum about it. I was assured at the time that it would be fixed in 7.x. Any idea when it will REALLY be fixed?

Marcos, I can't give you specifics. This is a general observation from nearly 3 decades of IT experience...but none of it in the last few weeks where I could look it up in logs. It is, however, a fact that when I take over a site that doesn't have scheduled scans (which is most of them) and add one, malware is found. Thereafter, malware is rarely but occasionally found in a scheduled scan that was missed by a real-time scan. I will not be stopping scheduled scans, but I will eagerly look forward to ESET making the scheduler smart enough so that the 3 OTHER scans, scheduled by default and not by me, don't all run simultaneously. That's ridiculous.

Marcos, thanks for your reply. A little wary about backing off on the scheduled scans. At all sites I manage, including ESET sites, scheduled scans pick up malware that real-time scans miss. Presumably because of updated virus definitions. Managed AV, including ESET usually doesn't include a default scheduled scan, but I've learned to always implement one when I inherit a site. And as soon as I do, the console is flooded with malware missed by real-time scans. So the question I have to answer is, how long am I OK with leaving malware on the machine? But even if I eliminated my scheduled scan, it appears that the other 3 would have run anyway, simultaneously, and that's still 2 too many. Hope the scheduler is re-worked soon!

A Windows 10/ESET AV 7.0.2091.0 user complained of slow performance. Checked Task Manager and found disk was 100% utilized, mostly by ESET. Opened ESET and discovered 4 Scheduled Scans running at the same time. User says she never turns computer off, but it does sleep after a timeout. In ESMC, the Policy for Scheduler has an entry for Scheduled Scans to run at 12:00. As it was shortly after 13:00, that's the only one I'd expect to be running. Looking at the start times for the scans, I woke the computer from sleep via ESMC Wake-Up Call 3 times earlier today to update its ESET Agent, which I had missed earlier. I think those wake-up calls correspond to the scan start times. In ESMC, those are not "Scheduled Scans" but "Automatic Startup File Checks". But I don't know if ESET AV uses the same nomenclature. Would those be 3 of the 4 scans, with the 4th being the one that starts at 12:00? I guess one of those scans would have been initiated after the Agent update? Are scans interrupted by the computer sleeping, or do scans keep it awake (or can they be set to do so)? The Scheduled Scan was originally set to run ASAP if a scan is missed; I've just modified that to scan only if a scan has not been completed in the prior 24 hours. My goal is to avoid having more than one Scheduled Scan running at a time; will this achieve it?

Thanks, that would be great!

Thanks, FONEIL. Since there is no mention of the April 2018 update (or any other feature update) on these pages, does that mean version 6.1x and higher officially support W10 v1803, and that there's no need to wait for "ESET Endpoint Security / Antivirus with declared RS4 support should be released during the upcoming week."?

Thanks all. I need official guidance; too much liability to rely on anecdotes. Until it's officially supported, I can't afford to install it on clients' systems. And even then I'll wait a few weeks. I like ESET, but you need to post a KB page like Trend does: https://success.trendmicro.com/solution/1119685. Post it a couple weeks before release date, and update it until every product is supported. (But don't do the other thing Trend does...wait until 4 months after release to issue an update to support a new W10 feature update!)

Is Windows 10 April 2018 Update/v1803/Redstone 4 supported by ESET Endpoint Antivirus 6.6.2072.4? Is there a KB article to that effect that I missed?

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?

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?

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.

Next ERA release? Next ESET File Security release? ETA? Thanks!

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.