Jump to content


Popular Content

Showing content with the most kudos since 11/11/2019 in all areas

  1. 2 points

    ESMC Upgrade

    For those of you in the same situation, I first had to install SP3 for SQL Server 2008 R2 Express because you can't directly upgrade to SQL Server 2017 Express unless you are running SP3. I was running SP2. Once this was done, I upgraded to SQL Server 2017 Express by using the custom install option. I then opened ESMC and went to Help->About. The DB version is now showing Microsoft SQL Server 2017 (RTM) Express Edition (64-bit) 14.0.1000.169. I then went to Help->Upgrade Product and a new client task was created. After a few minutes, I was kicked out of ESMC and I could not log back in. A few minutes later, the login page wouldn't even come up, but after some more time, it finally came up and I was able to log back in. ESMC is now showing it is v7.1717.0 and the Web Console is at v7.1.393.0. The last thing I did was install SQL Server Management Studio (SSMS) on my server so I could manage the DB a little easier. https://docs.microsoft.com/en-us/sql/database-engine/install-windows/supported-version-and-edition-upgrades-2017?view=sql-server-ver15 https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15
  2. 2 points

    Unknow status - new agent

    Just for clarification for others in case they encounter this issue: unknown state indicates that for specific application version ESMC is not yet aware of it's state. This normally happens when new version of application is seen for the first time and it should be resolved automatically in no more than 1 hour.
  3. 1 point
    @Marcos thanks for the clarification that it will be solved with the next update V13, but as asked by @BeanSlappers, any indication when this might happen? Will there also be communication that this issue is fixed? So users know when to setup again a new Phantom Account? I do want to avoid that I am too early and have to do it again Thanks.
  4. 1 point
    No the phantom account is part of eset Anti Theft - if you mark a device e.g as missing only the phantom account will work and possibly (although I'm unsure of this) if someone logs in it may help to detect their location. As someone who uses eset on their PC mainly (do not currently own a laptop) it is not something I have used
  5. 1 point
    According to this article: https://www.lifewire.com/how-to-download-install-directx-2624489 , DirectX 9 is supported on Win 10. Additionally, it might be required if an app requires use of one of its files. This appears to be the case for Eset. DirectX 9 can be downloaded from here: https://www.microsoft.com/en-us/download/details.aspx?id=35 . What I believe is the problem is the DirectX 9 file Eset requires somehow got deleted or corrupted on this Win 10 build. Installing DirectX 9 would be preferable to running a Win 10 repair or full install. Note: installing DirectX 9 does not replace or affect the running status of DirectX 12 which is the version used by Win 10.
  6. 1 point
    Why not release an intermediate patch now? All four of my Windows 10 computers with EIS are having the problem. In the mean time, I have no theft protection. Theft protection I paid for, as a key feature of EIS.
  7. 1 point
    Solved. I had OBDC version 5.3.13 After downgrade to 5.2.7. I was to able install Era ESET Agent Thank you very much
  8. 1 point
    This is a known issue of v13. It's been tracked as a bug and already resolved internally so a fix will be included in the next release of v13.
  9. 1 point
    A workaround should be already included in Endpoint 7.2. As for an actual fix in the VMWare driver, I have no clue if they have already included it in their products. However, a workaround on our part should suffice in order for the issue to not manifest.
  10. 1 point
    Please provide list of installer parameters you are using to deploy AGENT (only parameter names, no need for passwords or other sensitive details). From log it seems you are performing so called server-assisted installation, but probably with wrong hostname:port configuration, resulting in communication failure. Also once ESMC is installed, you might use also live installer created in console to deploy AGENT, it has no parameters so it would be much simpler.
  11. 1 point
    Try installing Eset using the off-line installer from here: https://support.eset.com/en/download-and-install-eset-offline-or-install-older-versions-of-eset-products
  12. 1 point

    ESMC blocked by ESET Endpoint

    This issue is fixed in the Internet protection module version 1382, which is currently in testing. You will be able to remove https://esmc from the whitelist when it's released for your product version(s).
  13. 1 point
    As I expected, this is a known issue. It's already fixed in the Internet protection module version 1382, which is currently in testing. Unfortunately it will take some time until it's released for your version of ESET Endpoint Antivirus. The fixed module will download automatically then. Until that time, you can keep using the value of 443 for Ports used by HTTPS protocol; alternatively, you can try the less invasive change of the default value with the value of "443, 0-79, 81-65535" or "443, 0-79, 81-6567, 6569-65535"
  14. 1 point
    To me it seems weird that you're getting an error about missing a DirectX 9 dll since DirectX 12 is a part of the OS. Moreover, there is no stand-alone DX12 installer that you could run on Windows 10 to repair it.
  15. 1 point

    problem with ESMC upgrade 7.1.503.0

    Hello, you are using unsupported MySQL version (5.5) which is no longer supported in ESMC 7.1. The only option is to upgrade your database to the one supported by ESMC 7.1 or downgrade ESMC back to 7.0 till you are able to process the upgrade.
  16. 1 point

    Anti theft optimization

    I'm with 13v now and I believe same thing happened when upgraded from 11 to 12. On a top of it.... I optimized about an hour ago and just couple of minutes ago it asked me to do it again.
  17. 1 point

    Anti theft optimization

    Have you encountered the issue always after upgrading to a newer version? E.g. from v11 to v12.A, from v12.A to v12.B,C,.. ? It's a known issue with upgrade to v13 but we are not aware of older versions being affected and we didn't get any such reports from users to my best knowledge either.
  18. 1 point
    @MartinK if I install Version 5.3.10 it works. But why I have to use a version from 20-Jan-2018? And why are there are no hints in the docs that a special version must be used?
  19. 1 point

    HIPS problem

    Join the club. I and many others have been asking for file wildcard capability for years.
  20. 1 point
    This seems like an issue we are already aware of. Please proceed as described here: https://support.eset.com/kb7272/ , but please enable Protocol filtering advanced logging as well. Don't forget to disable logging before Part II. Then please send me the created logs via PM. Then, you can try if changing this setting makes any difference: F5 -> Web and email -> Web access protection -> Web protocols -> Ports used by HTTPS protocol Change the current value (I expect there is 443, 0-65535) to 443. We don't need any logs from the state when the setting is changed, at least for now. Thanks.
  21. 1 point
    that's a great news. we are waiting for it. thanks a lot!
  22. 1 point
    Hello tbsky, thank you very much for your post, don't worry, we plan to release mentioned versions in the middle of November. Stay tuned!
  23. 1 point
    @schuetzdentalCB Thank you for your feedback. With regards to the automated network isolation, something like that (possibility to trigger network isolation from the console) is being added in ESMC 7.1 / Endpoint 7.2 for Windows. We plan to further expand this concept to allow autonomous response in the future. With regards to the application whitelisting, this is a bit more tricky topic. However it is on our long term roadmap. I will link your comment to the already tracked internal IDEA. Internal tracking IDEA-1510
  24. 1 point

    ESMC blocked by ESET Endpoint

    I think this behavior has been already reported and probably fixed in the meantime. Maybe @Marcos will know more details of whether module responsible for scanning network has been updated in the meantime. It is also possible that update was canceled which might explain why only specific devices were affected.
  25. 1 point

    Clients not showing in ESMC

    I would recommend to start by checking whether ESMC Agent installed on client machine is actually connecting to ESMC. For this purpose please follow troubleshooting part of documentation - especially status.html log present on client machine might be helpful in this case. In case ESMC Agent will be connecting to ESMC, most probable issue is that is is using different name in ESMC or is located in different group, which prevented ESMC to remove "dead" duplicate that is rendered as unmanaged. In case AGENT is not connecting to ESMC, it is crucial to resolve connectivity issues as described in referenced documentation.
  • Create New...