NetLock RMMNetLock RMM Docs
IV — Administration

ServiceDesk Plus

Connect NetLock RMM to ManageEngine ServiceDesk Plus, Cloud or On-Premises: alerts become requests of the mapped site, the all-clear adds a hidden note and closes the request, sites can be imported as tenants.

ServiceDesk Plus

Requirements

ServiceDesk Plus Cloud

  • A self client in the Zoho API console with its client id and client secret.
  • A refresh token of that client for the scopes SDPOnDemand.requests.ALL,SDPOnDemand.setup.READ,SDPOnDemand.general.READ. Generate an authorization code in the console and exchange it once, as described in the self client guide.

ServiceDesk Plus On-Premises

  • The API key of a technician, generated under Admin → Technicians/Users.
  • A version with the v3 API.

Both need a technician who may add, edit and close requests and read sites. API access depends on your ServiceDesk Plus edition.

Setup

  1. In Settings → Integrations, open the ServiceDesk Plus tile and choose Connect.
  2. Enter the Instance address.
    • Cloud: the address of your data center with your portal, for example https://sdpondemand.manageengine.eu/app/itdesk. Only the addresses of the data centers are accepted, so a custom domain does not work here.
    • On-Premises: switch on On-Premises installation and enter your server, for example https://sdp.example.com:8080. Allow unencrypted http is for an internal network only: the key is then sent unencrypted.
  3. Enter the Client ID, Client secret and Refresh token for the cloud, or the API key (authtoken) for an installation.
  4. Under options, set the Status when closing and, if a closure rule of your instance requires one, a Closure code. Status when closing applies to the cloud only and is the exact name of a status that closes a request; if the request then does not count as closed, the history shows close_refused. Requester of tickets is optional, see below.
  5. Map each tenant to a site, or import sites as tenants. Tenants without a mapping are not included. Severities can be mapped to priorities.
  6. Activate the connection.

What goes to the vendor

For every alert that passes the filter of the connection: a title, the severity, tenant, location and device name, the source, first and last time seen, the alert text, and a link to the web console if the public console URL is set. Check that this matches your data processing agreements before you activate the connection.

What happens to a ticket

  • An alert becomes a request of the mapped site. The subject ends in [NetLock-Alert-<id>], which NetLock uses to find the request again.
  • Without a Requester of tickets, the account of the API is the requester, so no customer receives an e-mail about a request. With an address, your notification rules apply.
  • When the alert ends, the request gets a note hidden from the requester and is closed if no technician is assigned. The text of the note is also the closure comment.

The behaviour is set in the Settings tab, see A.14.4. NetLock never closes a ticket whose status somebody changed in the meantime, and it never deletes anything at the vendor.

Known limits

  • NetLock sends at most ten requests per minute and client to the cloud. Further alerts wait in the queue and arrive with a delay; other connections are not held up. If the cloud reports that the limit is reached, the jobs wait a minute and then continue.
  • Tenants map to sites. The test of the connection reads the list of sites and fails with a clear message if it gets no answer or the list is empty.
  • A closure rule of the instance can refuse the close. The note is added and the request stays open. The history shows close_refused.
  • If ServiceDesk Plus refuses the note, the request is left unchanged, because nobody could otherwise see why it ended. The history shows note_refused.
  • ServiceDesk Plus MSP is not covered by this connector.