Jump to content

Zoltan Endresz

Members
  • Posts

    32
  • Joined

  • Last visited

  • Days Won

    1

Zoltan Endresz last won the day on January 11

Zoltan Endresz had the most liked content!

About Zoltan Endresz

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Hungary

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dear ESET Staff, Our clients using sometimes IPv6 communication for reach our enviroment. Looks like our SCCM server is not able to communicate with our clients on IPv6. If I turn off the ESET Firewall on a test client there is no problem, the SCCM <> client communication works fine. Could you please help me how to configure our Firewall Policyes for allow this kind of traffic? Thank you for your help in andvance!
  2. I really don't know, but the red "Computer restart required" error messages are dissapears, in other words usually I have only a few of them in same time. So, from my point of view it works.
  3. Hi ESET Staff, As I wrote before a several times, I had a lot of pain concerning the ESET updates: https://forum.eset.com/topic/22216-the-older-version-of-eset-endpoint-security-cannot-be-removed/ https://forum.eset.com/topic/23738-the-older-version-of-eset-endpoint-security-cannot-be-removed-2/ In these cases I had only one chance to fix the broken installations: Ask the remote colleague for log in to his computer, describe the issue, identify myself, and so on... > copy the ESET uninstaller into the affected computer > reboot it in Safe Mode > run the ESET remover script > reboot it again in Normal Mode > start an ESET install task It is no way if you have a few thousand computers in 20 countries worldwide, and a few dozen or hundred computers of them will be corrupted during each ESET version update. So, my colleague found a pretty simple and really useful solution. If you purge a few ESET registry entries manually or by a script, it will be possible install the ESET Endpoint Security on the client WITHOUT using the ESET Remover script in safe mode. So, simply run the following script as Admin then start again the EES installation: " REM Script to delete ESET Endpoint Security leftovers in registry for /f %%a in ('REG Query HKCR\Installer\Products\ /s /f "ESET Endpoint Security" /d /e ^|findstr /ri "HKEY_CLASSES_ROOT"') do set key=%%a ECHO %key% reg delete %key% PAUSE " So, I would like recommend to integrate a kind of similar "registry entry cleaner" option something like this into the ESET Protect admin surface, if it is possible for fix the broken ESET installation without the painful safe-mode script method. Based on my experiences it helps in the 98% of the cases.
  4. Hi Thomas, My solution is the following: 1.: - I created a dynamic group for collect the computers with error message "Restart required" : 2.: - Then I defined a CRON triggered task for send a pop-up window message into the affected computers: "Hello Collegue, please restart your computer as soon as possible because an ESET software update...bla..bla" or something like this You can configure the CRON for example launch the message hourly, every 10 minutes or as you want It works pretty fine
  5. Hello All, As a friendly reminder I would like ask again: do you have any update for me? Thank you for your reply in advance
  6. Hello All, As a friendly reminder I would like ask again: do you have any update for me? Thank you for your reply in advance
  7. Hello Marcos, I tried again the upgrade from EES 7.1.20xxx to EES 7.3.2032.0 on five computers. It fiished on two but failed on three clients. I got the following error messages when started the ees_nt64.msi installer manually: then After this I started the esetuninstaller.exe in safe mode and reinstalled the EES, it helped as always. Do you have any news concerning my previously uploaded log files? Thank you.
  8. Dear Marcos, I uploaded the contain of the folder C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs from the affected computer, then started the LogCollector on it. You find the results in the attached files. The test installation task was started on 29.05.2020 Thank you for your efforts in advance. ELC_logs.zip install_report.pdf Logs.zip
  9. Dear ESET staff, I had a topic with same contain, but it is already archived: The older version of ESET Endpoint Security cannot be removed https://forum.eset.com/topic/22216-the-older-version-of-eset-endpoint-security-cannot-be-removed/ So, I was happy because the EES 7.3.2032.0 release, as you can in read my previous archived topic I had a lot of problems with the version 7.2.2055.0 . For testing I triggered an EES upgrade task from EES 7.1.20xx version to EES 7.3.2032 on three computers. The upgrade finished on two computers but failed on one with the known error message: SoftwareInstallation: Installation failed with: (0x643), Fatal error during installation (0x643), The older version of ESET Endpoint Security cannot be removed. Contact your technical support group. , see software-install.log for more information loc... I known, the recommended solution is log on the affected computer, restart it in safe mode, run the remover tool called esetuninstaller.exe, reboot again in normal mode and reinstall the ESET. I manage more than 3500 computers in Europe, Asia and Americas. If the software update will fail on the 33% of these computers and I have to log in remotelly on each computers for fix the failed updates in safe mode, I will be in a huge trouble... Could you please advise a solution or a best practice concerning my next steps? What can I do? Thank's a lot for your help in advance. Best regards
  10. Hi ThomasMC, Based on my experiences, the best way to solve the Double Pulsar problem to identify the source computer then intall the ESET system on it also. The Double Pulsar scan the network and try to find further unprotected computers. This scan process cause a lot of warning messages from the right protected clients - time to time and again and again from each of them. So, do not search the problem on your screenshot listed clients, but check the "OBJECT" column for the source IP and try to identify the unprotected computer. I hope I helped.
  11. Dear ESET experts, I would like inform you that the expand buttons on the latest version of the ESMC Console are disappear from time to time, then come back again: Accurately, they are still exist but are invisible. This "feature" appeared after the ESMC upgrade. The ESMC Console version is: I hope I helped.
  12. Indeed, it is really annoying to re-hide a and browse trough the whole folder structure each time when I click on the "Computers" manu option. Click-click-click to roll down the structure, then check for example the state of the tasks then again click-click-click for reopen the right subfolder under the "Computers". The previous version was more user friendly.
  13. Hello ESET Team, For your information only I would like to inform you about the following issue. 1.: I tried to update the EES to the latest version 7.2.2055.0, but it is failed a several times. (Task failed, try to install software manually) 2.: The client is a Windows 7 / 32 bit industrial computer 3.: I tried to start the installer msi manually, but got a really interesting error message: "ESET Endpoint Security wird auf Ihrer veralteten Version von Microsoft Windows nicht mehr unterstützt." 4.: Then I started the EES v7.1.2053.0 and it works, no error message I 5.: The most interesting thing that we have other Windows 7 / 32 bit computers in the ESET system with EES v.7.2.0255.0 as well. Maybe there is something wrong in the backgorund, failed error message or something like this. It is not neccesary to do anything from my point of view, just wanted to inform you. I hope I helped.
×
×
  • Create New...