emilota

Hello @Riaan, if your EBA account activation link expired, please run through registration process again and new activation link will be sent to you. Regards.

Hello @NvD. When we checked your license, all worked as expected. To solve this on your side, please refresh your browser cache (via Ctrl+F5) or open your MSP account in different browser. If this will not work, reach out to ESET Technical Support. We will proceed to fix this frontend issue additionally on our side. Regards.

Hello FCALPS, we identified two same e-mails registered on your license. We recommend to erase one of them before migration to EBA. Regards.

To deploy 2FA and use ESET Secure Authentication app or 3rd-party 2FA app, you need to go to Profile and enable Two-factor authentication. If you require to change your authentication app while you have active 2FA in EBA, you must deactivate it and activate again. System gives you option to deploy ESET Secure Authentication app or synchronize with any third-party app which support TOTP. To find more details, please follow ESET Business Account online help / 2FA

Hello LesRMed, this is rare known issues. To fix this on you side try to reload the ESET MSP Administrator portal without cache (Ctrl+F5). If this does not work, please follow this: Login to ESET MSP Administrator Press F12 Go to Applications > Local Storage > https://msp.eset.com Delete the key PendingRequests Reload the ESET MSP Administrator portal (Ctrl+F5) If this still does not work, please contact ESET Technical Support. Regards.

Unfortunately, we are overwhelmed by new functionality, which we plan to release in next few months. We expect to address this issue afterwards.

Hello Martin, no yet, however, this is currently in development and we expect to release this option in the turn of the year. Best regards.

Hello twok, this might be a bug on our side. Let me check this internally with team and I will get back to you.

Hello theory, this behavior happens for example when the same device is re-activated by the same license but the configuration of the device was changed, e.g. in case of re-image of the virtual machine. As I can see the different prefix of SEAT NAME, I assume the device name was changed additionally. Is this your case?

Hi all, this email was sent to all Security Administrators, who accepted ToU during ELA registration process. The reason behind is that new Terms of Use include legal changes and Security Administrators must be notified about this (despite ELA is not in active development mode). Identifying respective changes could help you get through this, anyway, you must accept ToU as a whole.