emilota

Hi @WebGreg, column with last connection IP is available in both ESET PROTECT and ESET PROTECT Cloud security management consoles (Computers section, Computer detail, Computer preview, etc.). Do you use EP/EPC? Does it make sense for you to duplicate this functionality also to ESET Business Account?

Hello @Frederik Schiller, please could you explain more details ? Do you use ESET PROTECT management console or ESET PROTECT Cloud? How did you deploy ESET products to your endpoints? Do you access EMA via API or portal? Did you notice this issue on specific company or on all companies? Please, send me name of your company in private message to investigate your issue further. I expect it could be caused by desynchronization between our backend systems but I would like to uncover also the root cause. In general, I recommend you to solve this kind of issues via ESET Customer Care. Greetings.

Hello @Mauricio Osorio, could you please send me your support ticket number via message?

I guess @Preston Price is asking for deleting company and related licenses directly in ESET MSP Administrator. Delete company is not available now in ESET MSP Administrator, you can just suspend either entire company (what deactivates all associated licenses) or the particular license. The good news is that we implemented Delete company feature to ESET MSP Administrator and it will be publicly available since next service release scheduled on Wednesday, October 27. Note: You can delete only already suspended company. Let us know your satisfaction with this feature or any other suggestions for ESET MSP Administrator via Feedback form in ESET MSP Administrator.

Hello @bencho, this issue might be caused by several reasons (e.g., your endpoints might use agent without connection to management server, however, it still tries to reactivate product locally) and it need to be investigated properly. Could you please describe (just copy the upper description) and send your issue to ESET Customer Care? Our support specialists will take care about this promptly.

Hello @brylerayandayan, can you please provide me your EBA e-mail (via private message)?

Hello @brylerayandayan, I recommend to use EBA instead of ELA for license registration. EBA provides more benefits while ELA is legacy portal.

Hello @Alain GUERIN, transfer tokens from one ESA app to another is unfortunately not supported, however, we have this on ESET Secure Authentication radar. You can solve this by 2FA re-enrollment: Sign in to license management system where you activated 2FA (ESET Business Account or ESET MSP Administrator) by using ESA on your old phone Go to Profile and deactivate 2FA Just for sure sing out from licensing system and sing in again (2FA should be not required anymore) Install ESA (or any other 2FA app supporting TOTP) on your new phone Sign in to ESET licensing system again Activate 2FA in your Profile and sync it with new app on your new phone If you are not ESET Cloud Account owner and you are forced to have 2FA enabled, please contact your ESET Cloud Account owner to allow you to deactivate 2FA for re-enrollment. Regards.

Hello, based on ESET security directive for cloud services, password change is allowed once a day. Could you please give us more details about your use case to reconsider frequency of changing password?

@Ryan_GCITS just one hint: you can clean up your devices manually via security management console ESET PROTECT or ESET PROTECT Cloud, find more details here.

You will be able set the time interval to deactivate your seats for all your MSP customers. Does it make sense to you to have option to set individual time period per MSP customer?

hi @karsayor, we appreciate your feedback, we have evidence about this in EMA2 backlog and we would like to deliver this in H2 2021. Regards.

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.