przemocf

Thanks for quick replay, somehow WU didn't install KB---628 😑. After manual install - 9.0 installer works (would be nice if it would say that it missing sha2 components, etc...). Sorry for jumping guns 😅 I remember on W7 I had some issues too with missing SHA2...

Hello, I can not install Eset Server Security (9.0.12013.0). OS: Windows Server 2008r2 (64bit) On Web page where I download installer it says w2k8r2 IS SUPPORTED. Which last version SUPPORT Win2k8r2 server?

Hello, I have updated my Win10pro to this buggy Creator Update , the "Great Windows Defender" gave me a PITA, I managed to kill this "piece of junk" by: 1. change service "SecurityHealthService" autorun to "manual" by reg-fix: Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SecurityHealthService Value name: Start Value: change from "2" to "3" 2. Reboot, this stopped WD for me, but EEA didn't want to work, not uninstall nor update, so I had to do clean install 6.5.xx.... 3. Reboot to SafeMode, then I run esetuninstaller.exe , removed all Eset software (I had ver. EEA 6.3.xxx & RemoteAgent) 4. Reboot to SafeMode again, and check f all eset products are removed using esetuninstaller.exe 5. Normal reboot, install EEA 6.5.2107.1

Hello, There is not much more to "debug" in snmpwalk (on linux ,and snmpb on windows) . In I 'll try to update the FS and ERA console to latest available. Here is a screenshot of this "error packet" from wireshark:

Hi all, I have a WS server running ESET File Security and ERA, I collect some statistics via SNMP, whenever I try to scan OID tree (run "walk") of server the SNMP client always get stuck (print error and ends scan) at node: 1.3.6.1.4.1.29171.2.2.0 . Here is result of snmpwalk from debian linux - for windows snmp clients they thrown error at this node too. user@DEB:~$ snmpwalk -v2c -On -c securePublic 10.0.3.3 .1.3.6.1.4.1.29171 .1.3.6.1.4.1.29171.2.1.0 = STRING: "ESET, spol. s.r.o." .1.3.6.1.4.1.29171.2.2.0 = STRING: "6.0.993.0" Error in packet. Reason: (genError) A general failure occured Failed object: .1.3.6.1.4.1.29171.2.2.0 I think, the problem is with the snmp module from ERA that is being registered in windows in SNMP service... Here is my version-info: ******** ERA ver.: ESET Remote Administrator (Server), Version 6.3.136.0 ESET Remote Administrator (Web Console), Version 6.3.114.0 Microsoft Windows Server 2008 R2 Standard (64-bit), Version 6.1.7601 Service Pack 1 ******** Installed on server: ESET Remote Administrator Agent 6.3.136.0 ESET File Security 6.3.12006.0 ESET Rogue Detection Sensor 1.0.1049.0 ESET Remote Administrator Server 6.3.136.0 I can provide packet capture from Wireshark too for ESET tech. Ps. It took me a bit of time to find the ESET MIB - so for others that are looking for it , it's here: C:\Program Files\ESET\RemoteAdministrator\Server\ESET_RAS.mib