Jump to content

deszynda

Members
  • Content Count

    27
  • Joined

  • Last visited

Profile Information

  • Location
    Poland
  1. Thank you for quick response! I've just check and it's working It is a little bit confusing when you create a new "Security Management Center components upgrade" task and see: "ESET Security Management Center Server; version 7.2.1278.0 for windows (WINDOWS)". Netiher version isn't right nor system, but when it's running it knows what to do So thanks again 👍
  2. Hello, Managing macOS clients is a new experince for me. Since Windows clients Agents can be easily updated with "ESMC Security Management Center" -> "Security Management Center Components Upgrade" task I thought it can be done the same way on macOS clients. Looks like it's not. Could you please let me know if there is a way to update Agent remotly on macOS clients? Updating EEA works fine with "Software Install" task. Thanks!
  3. Thank you for directions. As I see in ESET repository - language abbreviation was removed with version 7.0 and newer. It was in the file name till version 6.6. I tried to add this three letters but it didn't help. Still the same issue: fatal error: Failed to locate the Installer package in the MSI cache. Maybe someone can review this ESETInstallationFixer_64.exe file and find what should be correct msi file location or file name.
  4. Yes. It is working. The problem is that it always requires to ask for a Team Viewer connection and for a free time of a user. I'm not able to do it on a users computer, just remotly. I thought that I can resolve it directly with Installation Fixer.
  5. I would like to fix issue "Installation failed with: (0x643)" with Installation Fixer https://support.eset.com/en/kb3544-how-do-i-use-eset-installation-fixer#i2 Missing MSI Registry. I follow steps written in instruction but running Fixer always ends with error: InstFix.exe - ESET Installation Fixer 1.5.0.0 Copyright (c) ESET, spol. s r.o. 1992-2014. All rights reserved. Fixing Missing MSI Registry ... Product lookup ... info: Found product: ESET Endpoint Antivirus 7.2.2055.0 fatal error: Failed to locate the Installer package in the MSI cache. C:\Windows\Temp\ESETInstallat
  6. Thanks for fast response. Is it possible that it was paused by any other application or Windows system? Or user only.
  7. Is there a way to find out who and when paused antivirus protection in EFS v6.5?
  8. I have the same situation for a last weeks. Today I've installed EFS v6.4.12002.0 on 3 virtual machines - one Windows Server 2008 R2 Enterprise and two Windows Server 2008 R2 Standard. On Enterprise everything was fine - activation was made during running installation task from ERA console. On one of Standard machines EFS didn't activate but I was able to activate it manually using my Security Admin account. On the second Standard machine I was not able to activate it at all - Error Code: ACT.21.
  9. Exactly - fixing potential problems. From time to time we had issues with "Windows Security Center indicates that the feature is not installed or is not running properly." Just restarting agent remotly helped in that cases. It is happening very rare but still it was very quick solution.
  10. Since ERA Agent 6.3 was released there is no option to restart EraAgentSvc service. Will this be available with next versions again? It was very usefull in some situations.
  11. After installing hotfix KB2664888 on all of our 2008 servers and updating ESET to version 6.2.12007.0 problem disappeared. Servers are running withour issues for a last few months. Now I'm updating to version 6.3.12004.0 and will monitor servers. But as Mairnh we met the problem with server 2012 and EFS v 6.2. I've updated it and agent to v 6.3 and will monitor it. Are there any fix from Microsoft side?
  12. Instead of installing the hotfix, you can disable protocol filtering in the advanced setup if you don't browse the web or receive email as doing so will effectively disable http/pop3/imap communication. Is it a kind of permanent solution or ESET is working to resolve this? We are installing now hotfix at severs with this issue. Servers are working for the list 2 weeks. We also met this issues on server 2012.
  13. I hope it will work. I'm also updating it on the problematic servers. We have a few of them.
  14. Hello again, There is around 1200 clients in my company. The thing is that our security policies requires as small traffic outiside company as possible. That's why we have ERA server so every client is connecting inside our LAN and only one server is downloading virus signatures from ESET servers. Best solution in this situation is to do it via ERA server. I think it should be change.
  15. Sounds good. We didn't notice any freeze after turning off service Columbus.exe. Hotfix didn't help in the past. From my side it's rather EFS vs. Columbus.
×
×
  • Create New...