FRiC
-
Posts
83 -
Joined
-
Last visited
Posts posted by FRiC
-
-
21 hours ago, StefanSa said:
i have already restarted various VM's where v9 was reinstalled because they hung on restart after the upgrade, all start after this reinstallation without problem.
One could assume that this is an initial problem immediately after the upgrade Installation.That's what I thought at first too. But when I installed the May OOB update I had several VM stuck at restarting. Resetting the VM causes the update to revert. I'm uninstalling V9 for now.
-
Has there been more reports or any suggestions what we should do? Originally I thought this issue only affects upgrades, so I uninstalled V8 manually then cleaned installed V9 to avoid upgrading. But today after installing the OOB update and my test DC is stuck booting again. Uninstalling for now.
-
5 hours ago, Marcos said:
In that case the cause of the issue in unknown and developers will need a complete memory dump from the freeze to determine the root cause.
Thanks, can confirm exluding extension doesn't work since we don't have ESET Inspect agent.
-
8 hours ago, Marcos said:
If you have the ESET Inspect agent installed, it's most likely a known issue and excluding the MUI extension in the real-time protection setup should work around the issue.
Otherwise we recommend generating a complete memory dump from a frozen state of the system as per https://support.eset.com/en/kb380 and supply the dump to ESET for perusal and to determine the cause of the issue.
So if we're not using Inspect agent (EDR) then excluding the mui extension doesn't work?
-
On 5/10/2022 at 7:07 PM, Marcos said:
We assume that excluding the MUI extension in the real-time protection setup could resolve the issue:
Is this a Server Security thing or should MUI extension also be excluded for Endpoint Security?
Also, we don't have ESET Inspect agent. Is that the EDR agent?
-
Glad I'm not the only one. 2 out of 10 servers got stuck after updating. One with applying computer settings, and one just completely blank. The applying computer settings one managed to right itself after I rolled back the checkpoint, but the blank one (which happens to be a DC) had to be booted into safe mode and cleaned with ESET uninstaller.
-
Thanks, I managed to get the DC to boot in safe mode, removed ESET with the uninstall tool, then it could successfully finish booting. Event logs didn't seem reveal anything since it appeared to get stuck at a different place every time. Tried installing again with an installer instead of an install task and it worked fine.
After that, I tried installing V9 to another virtual server (not DC) and it got stuck at Applying computer settings after the reboot. Rolled back to the snapshot but strangely enough after booting up again V9 is installed. Probably used checkpoint wrong somehow.
Three others I updated (mixed physical and virtual) went just fine. This is Windows Server 2019 on Hyper-V. Never had this much trouble with updates before.
-
The forum update notice and download links always appear slower than ESMC.
I tried installing on a secondary DC and the DC can't boot after installing. 🤪
-
A bit late, but you can get the USB serial number from device manager.
-
-
Yeah, I have the same dynamic group created, and suddenly noticed it's not working correctly and when I tried to activate EDTD they all became LiveGuard Advanced. I see why now.
-
I'm wondering if manually doing the "Update installed ESET products" task is any different than the automatic upgrade process? I've been using the manual task for years and was glad for the automatic upgrade, but the waiting...
I understand the need to release slowly in case of issues, but 30 days is a bit too much for us, and our auditors are not happy we're not updating a security software after seeing that huge red bar.
-
Hi Marcos, I wrote ELA by mistake, I meant EBA (as in first post).
Yes, the clients are connecting to the on-premises ESET PROTECT fine, that's why I didn't realize they weren't activated for EDTD. I also noticed one thing different on EBA, the ones I've just activated show that they're activated with my name, while the ones activated previously show that they were activated by the company.
-
Hi Marcos, thanks for replying, pls see attached.
While looking at my ESET PROTECT I discovered some clients that had the product activation task ran on and shown as succeeded but when looking at the computer detail are actually missing license and also not registered on the ELA site. I ended up creating a dynamic group to display clients missing the EDTD license so I won't miss them in the future.
I wonder if this has to do with renaming computers? A lot of clients listed on my ELA site have wrong device and/or seat name. When activating the EDTD license computer names from years ago reppeared.
Thanks.
-
Hi, earlier this month we upgraded to ESET Advanced which came with EDTD, so I enabled the feature and activated the license for all our users. Today I looked in EBA and to my surprised a whole bunch of clients showed that they have not connected since when I initially installed the license, and sure enough, looking at each computer in ESET PROTECT (on-premises) shows the same. I ended up activating the license all over again.
Is this a known issue? ESET PROTECT doesn't have a way to show which computers don't have the license, but I imagine this is by design.
-
I get this once in a while on my domain connected machines. (100+ endpoints, all wired, behind the same router.) And it goes away when the client is rebooted. Can the warning be safely ignored? Shouldn't it continuously try to connect to LiveGrid servers, or does the connection only happen once when booted?
-
The question is does ESET still run in full functionality just without the new functions before a restart? It looks like the new version will automatically install when the computer is powered on.
-
18 hours ago, Marcos said:
Is that also the legacy EFSW 6.5? Unfortunately this version didn't support advanced update engine logging so in case the issue continues, I'd recommend raising a support ticket. As I recollect, a logging dll will be necessary to install to generate the desired update logs.
Nope, for me it's Endpoint Security 8.1. Probably an ESET issue since it went away and I haven't seen it since.
-
Had same issue this morning on one of our standalone clients which went away after reboot.
-
I have a similar question. We bought "Endpoint Protection Advanced" couple years ago which seems to have turned into ESET Protect Entry. I upgraded to the latest ESET Protect 9 yesterday and now I have a useless Dynamic Threat Defense tab in my dashboard. The sales blurb looks interesting but how is it different from cloud based protection that I already have? More info? Trial?
-
6 hours ago, Command IT said:
So is the upgrade from 8.1.2031.0 to 8.1.2037 classed as uPCU ? and it should just roll out at some point?
It will roll out after like a month or two. The difference is that if you update manually, it will (most likely) show a warning that you need to reboot for all changes to take effect. With the uPCU update, there's no warning that you need to reboot, but it still won't take effect after you reboot.
We have some computers that are only restarted every 2-3 months or longer. Was hoping that the uPCU update didn't require a reboot.
-
I ran into probably the same issue a few times over the past few years. Was never able to figure it out so I kept adding things to the whitelist whenever I ran into the problem. But last year when we moved to Windows 10 the problem went away. (Or maybe it went away because we also upgraded to small SSD's and got rid of the D drive.)
Hope you figure it out.
-
I have the same issue and reinstalling is not an option for me. Hope this is fixed soon.
-
Hmm, does the warning pop up on the user's computer? I didn't see anything but the endpoints stop connecting to ESET PROTECT and I have to manually disable the firewall for them to connect. After connecting everything returns to normal.
ESET Support response times
in ESET Products for Windows Servers
Posted
Hi Marcos, can you refer some instructions on how to generate a memory dump? My servers are Hyper-V VM's, and the VM's don't appear to be frozen when the issue occurs. Thanks.