ESET Staff
  • Content count

  • Joined

  • Last visited

About VladimirVladimir

  • Rank

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,119 profile views
  1. What permissions are required for ESA

    You need to use an user which is in Domain Admins and Schema Admins groups. Because: you need to be able e.g. to extend schema, add DNS entry, create AD groups as far as I know, these operations cannot be delegated (if you mean the Delegation of Control Wizard in ADUC) - or do you believe they can be delegated? and that's why there are prerequisites in the installer which check specifically if you are in that groups - they do not check any delegation or actual permissions or ability to do the required operations But, note that you do not have to use the default Administrator account created while installing the domain. You can create a new arbitrary user and add that user (temporarily) to the Domain Admins and Schema Admins groups and use that user to install ESA. To install additional components then (e.g. Windows Logins), you can use the NO_DOMAIN_ADMIN_MODE (while adding the computer accounts to EsaServices manually).
  2. What permissions are required for ESA

    Hi there for ESA installation you need domain admin and schema admin. Schema admin is needed only initially (sometimes schema admin is included in the domain admin). For more details please check product documentation: LINK regards vladimir
  3. ESA without internet connection

    Hi there ESET Secure Authentication needs internet connection to be fully functional (during setup, license activation, user provisioning, Push authentication, SMS OTPs) but there is an option to choose authentication method such as generating OTPs in ESA mobile app (after provisioning of users which needs connection) or use of hardware tokens in offline environments. So if you are able to have it online during installation. activation, provisioning of users (in the case of mobile app) and then put it in offline state, it should work. If you are not able to keep it online during the initial steps, please contact ESET support directly to discuss what and if there are other options for the customer. regards vladimir
  4. ESET Cloud Administrator?

    Yes, with public release of the product.
  5. ESET Cloud Administrator?

    Hi Mike as this product is not yet publicly available, we are not able to share all the details. First and foremost, ESET Cloud Administrator will be a brand new product (not a successor to ERA6) designed for Small & Medium business customers, requesting simplistic & straight-forward operation without hassles. Despite the fact that it will be based on similar architecture and concepts known from ERA6. However some functionality was re-worked to support cloud hosting, some was omitted as is not valid for Small & Business Customers, and some added, in order to optimize user experience. Major difference will be a Quick setup - there will be only few simple steps which needed to be done to make the solution up and running. After creating an ESET business account it will take just a few clicks to create a dedicated cloud console. With the help of live-installers adding a computer will be a simple and streamlined activity. All the usual stuff, typical for on-premise software such as initial configuration, setup, suitable hardware, and related maintenance will be taken care of automatically in the background by ESET. Regarding the functionality, there will be a huge overlap with ERA6 functionality with focus on simplicity of use. We will share more details when the product will be publicly announced. regards vladimir
  6. ESA with Office 365

    Configuring AD FS for Office 365 has nothing to do with ESET Secure Authentication directly. ESA is just a plugin on the top of that, utilizing already configured environment. That´s why we do not cover such topics in related product documentation. How to properly configure ADFS to work with Office 365 can be found on Microsoft support pages: https://blogs.technet.microsoft.com/rmilne/2017/04/28/how-to-install-ad-fs-2016-for-office-365/ regards vladimir
  7. Hi there in general, it is really hard for us to provide help if we do not receive log files from the product to investigate possible issue, but it seems (according to the issue number) that it has to do something with compatibility between components. It seems that you have installed latest RDP plugin and ESA server (on the new server) and when accessing the new server via RDP (with ESA plugin), the newest plugin is connecting to the old ESA server , installed on the old server. Try to deactivate/uninstall ESA core on the old server. Or even better, before doing anzthing, trz to share as much details as possible with us, e.g. esa server versions, plugin version, better describe zour actual setup, what computer is connecting to which, domain description etc. So we can make a better decision. As we are at the moment guessing what could went wrong and there will be some follow up activities needed, please try to contact you regional reseller to create an official support ticket for you, so relevant team can help you. Or if you are an reseller/disributor, you are able to create a support ticket directly. v.
  8. ESA with Office 365

    Hi there mandatory prerequisite is to configure your AD FS to provide authentication to Office 365. If this was done and ESA plugin installed it should work. Did you configure your ADFS/365 correctly? v.
  9. Questions on ESA with office 365

    Hi regarding the SIEM. We do not have any plugins/APIs for such products. But we are happy to hear any details regarding such requirement. Which specific SIEM tools are you interested in? what would you like to manage/configure/monitor from such tool? do you prefer a dedicated API, or also specific plugins are required? Thanks regards v.
  10. Questions on ESA with office 365

    Hi there 1. We have a feature called IP range whitelisting where you can define IP ranges from which second factor is not required (see product guide for more details) 2. Importing phone numbers is up to the AD capabilities. ESA just utilized the AD functionality. I presume, AD has an option to import data in bulk. 3.We internal product logging for (product logs) some of the user login activities. But there is not a dedicated UI for accessing such information. Also administrator can find last successful login and last failed login per each user in the AD tab of dedicated user (see attached screenshot). 4. Not sure if I understand. ESA has a security mechanism to lock user after certain amount of unsuccessful login attempts. ESA does not have a capability to set policies. 5. ESA has an API. please find details in product documentation. User guide API guide regards vladimir
  11. ESA with AD FS issue

    Hi ESA support ADFS 3.0 (included in Win2012R2). Product manual: https://download.eset.com/com/eset/apps/business/esa/windows/latest/eset_esa_product_manual_enu.pdf regards vladimir.
  12. Hi there Yes. This Thursday. regards v.
  13. ESA lock out issues

    Hi this could happen if you checked "remember password" on the client. Which means it tries to log in with the same password (One time password) again and again. vladimir
  14. ESA questions for Windows Servers/admins

    Hi you can activate ESA (second factor) for any specific user in Active Directory You can protect the endpoint (server/PC) in two ways: By protecting the local login with a second factor or by protecting RDP connection with a second factor (if the user who is logging is enabled for 2FA). In both scenarios, ESA plugin for RDP/local login (just the plugin, no need to install auth server and management tools – on every machine) must be installed on each machine you want to protect (and activate 2FA for users accessing the machine). Regarding the Authentication server and management tools, its ok to have it installed only on one server in the domain. Yes regards vladimir
  15. Hi not sure what version of product manual you have. But I meant this part: see the screenshot. Product manual LINK Several things could went wrong, its hard to say but: as mentioned, official support for Server 2016 will be from ESA 2.6, so there could be some issues in general you need to install core service and management tools, then install the proper plugin and at the end, provision users for 2FA. But from your screenshot I do not see the plugin installed, so definitely something went wrong without a proper installation logs I am not able to investigate further. Could you please contact your local support, send them appropriate logs - they will take it from there and help you resolve this issues. Please mind the fact, these issues may be caused by product being installed on unsupported version of the OS Regards v.