Before you can create mappings, please make sure you meet the following pre-requisites:
- Companies need to have an active contract in Autotask PSA
- Contracts should have atleast one (mapped) Service Item, the script will only create adjustments to existing service items, it will not add or remove them.
Step 1: Getting the EmaCompanyPublicId
- Run Invoke-EmaSyncCompanies
- Find the emaCompanyPublicId of the company you want to map:
- in our case it is: f160f3d6-1a73-48ec-9f17-16e4eb1c4874
Step 2: Getting the autotaskContractId
- Run Get-autotaskContracts
- find the contractId of the contract we want to map:
- in our case it is: 29684190
Step 3: Creating the mapping
- open mappings.json and use the information from previous steps to create the mapping
- Example (highlighted lines were added):
Step 1: Getting the EmaLicenseProductCode
- run Invoke-EmaSyncCompanies
- Find the EmaLicenseProductCode for the license you want to map:
- in our case it is 2015
Step 2: Getting the AutotaskServiceId
- run Get-autotaskServices
- find the AutotaskServiceId for the service you want to map:
- in our case it is 11
Step 3: Creating the mapping
- open mappings.json and use the information from previous steps to create the mapping
- Example (highlighted lines were added)
note: this is only used for Invoke-EmaSyncCompaniesExperimental Step 1: Getting the EsetProductName
- Log into ESET MSP Administrator
- Open a company
- Go to "Activated Units"
- Find the relevant ProductName(s) that you want to map:
- in our case it is "ESET Endpoint Security for Windows"
Step 2: Getting the AutotaskServiceId
- run Get-autotaskServices
- find the AutotaskServiceId for the service you want to map:
- in our case it is 11
Step 3: Creating the mapping
- open mappings.json and use the information from previous steps to create the mapping
- Example (highlighted lines were added)