This article contains global Instructions for:

  1. New MSPs
  2. Existing MSPs

New MSPs

Step 1

After ordering licenses from Ingram Micro's marketplaces, partners must complete the following:

  1. Accept invitation email to EMA to configure first user.
  2. Add any additional users that require access to licenses and provide the proper access rights


Step 2

The installation process is based on whether the product type is On-Prem or Cloud.

On-Prem

  1. If the MSP is going to be using an On-Prem installation of ESET PROTECT they would need to ensure the perquisites are met: https://help.eset.com/msp_getting_started/en-INT/protect_requirements.html 
  2. Then complete one of the following installation steps
  3. Next they would need to import the licenses to the ESET PROTECT Server
  4. After adding the licenses, the MSP can continue with the deployment process by either using the MSP setup option or any of the other deployment options
  5. Any additional licenses provisioned will automatically show in the ESET PROTECT Server if the user used to import the licenses has read or write access to the customer in EMA.


Cloud

  1. If the MSP has provisioned a cloud eligible license, they would need to complete the activation process in the EMA portal
  2. If additional users require access to ESET PROTECT Cloud they must first be created in EMA
  3. Next the MSP can complete the desired deployment process : https://help.eset.com/protect_cloud/en-US/msp_process.html

Existing MSPs

For existing MSPs, account should have already been migrated to the new version of EMA

Step 1

Create/ Verify EMA user access rights

  1. If the MSP places an order for a new license, they will have to verify any existing EMA users have the proper access rights to view and access the licenses. If a new user requires access, they will have to be created in the EMA portal by a user with current write access to the MSP and assigned the proper permissions.


Step 2

If licenses are not showing in the ESET portal

  1. If the licenses are not showing in the ESET PROTECT or older management console it may be required to import the license with a user with proper access rights and/or upgrade to ESET PROTECT