ESET MSP Administrator 2 (EMA 2) is a license management system for ESET Managed Service Provider (MSP) partners.

An MSP offers customers ongoing support and active administration for network, applications, infrastructure, and security.

A phased transition will affect all current ESET MSP Administrator 2 users.

ESET PROTECT Hub will replace the ESET Business Account and ESET MSP Administrator 2 license portals. We will transition all accounts from both platforms in phases. After their accounts have been transitioned to ESET PROTECT Hub, users will not be able to access the older license portals.

A mixed account is where a user uses the same login for their ESET MSP Administrator 2 and ESET Business Account license portals. Mixed accounts will be merged into one if they are connected by an ESET PROTECT instance. In any other case, we will treat these accounts as separate. Users will be able to change the persona via a drop-down menu to access both accounts.

After the release of ESET PROTECT Hub for customers (formerly known as ESET Business Account users), the self-registration process has shifted from ESET Business Account to ESET PROTECT Hub.

For ESET MSP Administrator 2 users who have not yet transitioned, we recommend creating an ESET Business Account directly from their ESET MSP Administrator 2 account (located under the “My Company” section).

This recommendation comes from the fact that if an ESET MSP Administrator 2 user initially created an ESET PROTECT Hub account to manage their own licenses instead of using ESET Business Account, they would end up with two separate ESET PROTECT Hub accounts after transitioning, rather than a single MSP account that includes the "My Company" section for managing their licenses.

We transition users with API access to ESET PROTECT Hub. API users are not affected by the End of Life, as the API keeps its full scope of functionality in ESET PROTECT Hub.

Updated on October 29 2024: We want to inform you about several important ESET MSP Administrator 2 API (EMA2 API) changes as part of the ongoing End of Life process. 

Custom Identification in API (applies to Non-SF Partners)

For API users who do not provide a Custom Identification, an identifier will now be automatically generated as a timestamp. This identifier will not be editable later.

Usage of "One-User-Many-Companies" Functionality in API

API users should be aware that utilizing the One-User-Many-Companies (OUMC) functionality is entirely at their own risk. This feature was not designed for API users, and we cannot guarantee its correct operation.

Unilicense Categories and Usage Reports

Unilicense Categories and Usage Reports will not be implemented in the ESET PROTECT Hub UI. These reports will only be accessible via the ESET PROTECT Hub API.

Terms of Use

Accepting the Terms of Use (ToU) for ESET LiveGuard Advanced will no longer be required in ESET PROTECT Hub. The ToU will be accepted during the activation of newly created users.

VAD Field for Divisions

The ESET MSP Administrator 2 API currently includes a VAD field for Divisions. The ESET PROTECT Hub has no equivalent for the Distributor entity. Therefore, we will decommission this field, and this endpoint will always return a false response.

These changes are not considered "breaking changes" for migration purposes.

ESET PROTECT Hub includes all existing ESET MSP Administrator 2 and ESET Business Account features, as well as new features.

New features include:

•Expanded hierarchy view, providing an overview of child companies, customers and their licenses

•Opportunity to sell standard licenses and enhanced visibility into standard customers (self-managed and co-managed)

•On-demand access to cloud security solutions through impersonation

•Comprehensive security management for your own company, eliminating the need for extra tools or products

To start using ESET PROTECT Hub, users must transition from the legacy portal to ESET PROTECT Hub. ESET is transitioning users from ESET MSP Administrator 2 to ESET PROTECT Hub in phases.

To ensure a smooth transition, each ESET partner or office will be assigned to a specific transition phase, following a pre-agreed timeline.

When the transition is complete, access to the legacy portals will be discontinued. From then onward, license management and all related tasks will be handled exclusively through ESET PROTECT Hub.

After the transition, all users will receive an ESET PROTECT Hub invitation email and must use their ESET MSP Administrator 2 credentials to log in to ESET PROTECT Hub. The entire hierarchy of companies, customers and licenses, together with cloud consoles, will be transitioned automatically. If you have any questions about the transition, contact your regional partner or your sales manager.

Customer action is not required. All affected users will be notified by email about the transition process.

We plan to transition all MSP accounts from all countries during the phases; see the Transition phases mentioned below.

Note that the table below serves an informative purpose and may be subject to change. We will provide you with all the essential details after we schedule your transition.