Jump to content

Ufoto

Members
  • Content Count

    33
  • Joined

  • Last visited

Kudos

  1. Upvote
    Ufoto gave kudos to Marcos in ESET EDTD - Is it enabled?   
    The "Enable" button currently doesn't change state. Since it's confusing now for users, we plan to change it in future versions.
    To find out if files are submitted to EDTD for analysis, open the "Submitted files" window and check the information in the "Sent to" column. Undetected files that might potentially carry malware are submitted to EDTD while already detected files are sent to LiveGrid:


    You can also find this information on clients:

  2. Upvote
    Ufoto gave kudos to MichalJ in Access to multiple ESET Protect Cloud tenants   
    Hello @Ufoto
    As of now, this is indeed not possible. I assume, that you are a reseller, and you have more than one customer, that has their own EPC instances. As of now, you will have to have a different aliases for every such instance, as one "EBA USER" can be linked only to one EBA instance, and one EPC Instance. 
    We are working on a new reseller focus portal, which will allow you to have a "service level login" to all your customers EPC instances. So yes, there is plan to add multi instance access, however I can´t confirm exact timeline at this moment. But our target experience is similar to the one you are referring to. 
    Regards,
    Michal 
  3. Upvote
    Ufoto gave kudos to Matus in Endpoint for macOS - protect configuration   
    Hi Kostadin,
    If you set policy via Protect, you can't change that locally. 

    Password protected settings are meant in case you're not managed or some settings are not managed... If you set every setting like that (even defaults) from Protect, user can't change that.
    On Mac, ESET Agent password protection is not present. To limit/protect against uninstallation ensure, that users are not administrators (root access) of a machine. In UNIX world, root can do everything. 
  4. Upvote
    Ufoto gave kudos to MartinK in Manual VS Automatic ESET Protect Upgrade   
    Component upgrade task upgrades only ESMC/EP components, as is ESET Management Agent, ESMC Server and ESMC WebConsole, but it does not upgrade other, especially third-party components as is Apache Tomcat, Apache HTTP Proxy or MS SQL Server.

    Thus benefit of performing manual upgrade using all-ine-one installer for Windows, or performing upgrade ot EP/ESMC Appliance using "migration" to new version, is that also third-party and and possibly other support tools are upgraded. Also note that manual upgrade is less prone to failures caused by environment issues, as are those network related, but also those caused by missing dependencies (for example minimal supported version of OS or database itself).

    My recommendation would be to perform manual upgrade, as it is fairly simple from users perspective, and it offers more control. Also I would recommend to perform database backup before doing so, but hat should be case also for automatic upgrade.
  5. Upvote
    Ufoto gave kudos to Rendekovic in Management of native encryption for Windows?   
    Hello @Kostadin_k,
    EFDE for mac utilizes FileVault because there is no other way to FDE macOS. Apple prevents its system to use FDE from 3rd party vendors.
    EFDE for win is a different story. Microsoft allows for vendor´s proprietary encryption and we have this covered.
    So we are pretty much covered on both macOS and Windows. But yes, adding Bitlocker management to ESET Protect (Cloud) is an option, but even if we go this direction in the future, it will not work as seamlessly as you described. Taking over management of an already encrypted machine is more than complicated because of recovery password that belongs to a particular encrypted system. Migration of these recovery passwords from Active Directory (where Bitlocker stores them)  to our console followed by a seamless "takeover" of the machines by the console is very complicated (if even possible).
    At this moment, adding management of Bitlocker to our EFDE/EP(C) solution is not on our roadmap.
    Ervin Rendek
    PM for Encryption solutions
  6. Upvote
    Ufoto gave kudos to Peter Randziak in MacOS 11 Update Issues   
    Hello guys,
    thank you for your reports, I checked it with the QA and Dev, they are aware of this issue.
    Once the upgrade fails, can you please collect the logs as described at https://support.eset.com/en/kb3404-use-eset-logcollector-on-macos-and-send-the-logs-to-eset-technical-support?ref=esf 
    upload them to a safe location and send me a private message with the download details and reference to this forum topic? 
     
    Once you do, the work-around is to disable the Web access protection to apply the upgrade.
     
    We apologize for the inconvenience caused,
    Peter
  7. Upvote
    Ufoto gave kudos to MichalJ in ESET Endpoint encryption and ESMC HTTP proxy   
    Hello, in case you mean "ESET Full Disk Encryption", then the answer is yes, as this is managed via ESET Protect / Security Management Center Server / agents, which use HTTP Proxy. If you want to use ESET Endpoint Encryption, with a dedicated server, then this solution uses a separate Cloud Proxy component. 
  8. Upvote
    Ufoto gave kudos to JPritchard in ESET Endpoint encryption and ESMC HTTP proxy   
    Good afternoon,
    I am a technical support engineer for ESET's Encryption product family.
    You have mentioned a few things that I feel need clarifying, some of which may require in-depth explanations in order for you to come to your own conclusion on how best to deploy ESET Endpoint Encryption in your own environment.
    First I feel I need to address an important concept regarding ESET Endpoint Encryption. EEE uses a "cloud proxy", which is our patented technology which simply acts as a pigeonhole (or middleman) for communicating commands/client updates between the EEE server and EEE client workstations.
    If your environment has an Internet proxy to control traffic, then you will need to add your proxy details to your EEE Server.  For complete details on this, please read our article here: KB7607 - Add internet proxy server settings to ESET Endpoint Encryption Server
    Providing everything is configured correctly, your EEE client workstations will be able to communicate with your EEES (through the cloud proxy) as normal.
    Regarding your questions about deployment, I am not familiar with deploying EEE from ESMC itself, but I know there isn't a repository for EEE, so it cannot be installed that way. However, the EEE Server has a "Push Install" feature which allows you to install the EEE client (MSI) on clients across the network.
    Sadly this may not be suitable, as you said your users never connect to your internal network. In which case I would ask, how do you currently manage software deployments for users off your network?
    Regardless, EEE's installer is an MSI file, which can be easily deployed through 3rd party tools. Just ensure your Workstation Policy is configured correctly before generating the MSI for the endpoints, as the Workstation Policy is bundled into the MSI itself. Additionally, depending on your requirements you may need to create a separate Merged Installer for each Workstation Team you have set-up in your EEES. 
    I hope this sheds some light on your situation and what you can do to deploy EEE in your environment.
  9. Upvote
    Ufoto gave kudos to Marcos in endpoint version 8   
    For Endpoint v8 you can find a changelog on the download page or here: https://forum.eset.com/topic/26629-eset-endpoint-products-for-windows-version-802028-have-been-released/
    ESET PROTECT and ESET PROTECT Cloud are to be officially released later today. At that time a changelog will be available on the standard channels (ESET's website, forum, etc.).
×
×
  • Create New...