Introduction

Use this article as a guide to create and maintain an RMM integration with N-able N-central (formerly SolarWinds N-central) which gives you information about CPU, memory, last reboot, etc.

To integrate with N-able's cloud-based RMM software, please refer to Integrating with N-able RMM (formerly SolarWinds MSP RMM) (previously branded as SolarWinds MSP RMM, and MAXfocus prior to that).

It should only take about an hour to get up and running with your RMM. This is a rough estimate based on our experience with several partners who integrated with their RMM.

For more information about the device mappings, see RMM Field Mappings.

Prerequisites

• An SSL connection with a valid certificate (not self-signed) from a trusted authority is required.
• Manager or Administrator level access to IT Glue.
• If you're integrating with a PSA and an RMM, you will want to first sync your RMM to your PSA and your PSA to IT Glue to make sure that the required data is available for matching.
• A Manager role will only be able to see RMM matched/unmatched data for organizations that they have explicit access to. To grant access to RMM data for all organizations, refer to Step 7 of our Adding and removing users KB article.

Instructions

Configure RMM

1. You need to create a dedicated N-central integrator login which is a user account created at the Service Organization (SO) level that has read-only access permissions to all clients.
1. The initial password is a temporary password. You must login to N-central and change the password to complete the registration process for the created account. Otherwise, IT Glue will be unable to access the API.
2. In addition to the SO user's credentials, you need the Fully Qualified Domain Name (FQDN) of the N-central server.

If you are using N-central 11 (or newer), follow the instructions in our Creating an integrator login in N-central KB article to create the integrator login.

Enter your RMM credentials

1. Log in to IT Glue and navigate to Account > Integrations. Then, click on the green + New button and then on the N-central icon.

   
   

2. Enter your N-central FQDN (ncentral.example.com) and login credentials. Then, click on the Connect button.
   Note: To add a custom port for API traffic, you can add the port to the FQDN. For example, to add port 3000, your FQDN would look something like this: ncentral.example.com:3000.
   
3. After your enter your RMM credentials in IT Glue, you will need to match your IT Glue Organizations to either Customers or Sites.
   
   

   Option	Description
   Customers	Matching on customers will allow you to map to top-level organizations in IT Glue.
   Sites	Matching on sites allows you to map to organizations and sub-organizations in IT Glue.

   You can change this preference at any point. If you change your preference later, existing matches will be reset. For more information about sub-organizations, see Working with sub organizations.

Sync Data

1. From the Account Integrations screen, click Actions > Start Manual Sync.

   
   

2. When the sync is complete, the Status column changes from Syncing... to OK.

Organization matching

IT Glue discovers organizations and configurations and tries to match them to data in your account. The matching logic can be found in the Introduction section of this article. Anything that isn't automatically matched will need to be manually actioned.

1. From the Account Integrations screen, find your RMM in the list and click on Actions > Matching.
2. In the Unmatched tab, review the unmatched organizations.
   1. If you're happy with a suggested match, click Accept Suggestion to accept it.

      
      

   2. If there is no suggested match, or it is incorrect, you can search for and choose a different organization using the Match To field.
   3. If no organization exists in IT Glue, you can choose to create an organization. You can also choose to ignore groups, which means they won't count as unmatched items in subsequent syncs.
      
      Warning. Before creating an organization from the matching screen, ensure that no corresponding organization already exists, otherwise a duplicate will be created.
3. If any matches are incorrect, click on Actions > Change Match and select a different organization to match to.

Configuration matching

Once all organizations have been matched, the same process should be followed for any unmatched configurations.

1. From the Matched tab, choose any organization that has unmatched configurations, click the Actions button, and select Match Devices.

   
   

2. For any unmatched configurations, you can either accept the suggested match, search for an IT Glue configuration by entering the name in the Match To column, or create a new configuration by clicking Actions > Create Configuration.
3. Before you create configurations, first match any of the devices based on MAC addresses or serial number, for example, virtual servers. When you're done matching, you can create (in bulk or individually) any of the remaining devices coming in from your RMM.
   Important. We don't recommend that you create configurations from your RMM if you'd like to then have them populate from IT Glue to your PSA. New items created from such data will not sync with your PSA unless you choose to do so manually by editing and saving each and every item. This is absolutely manual and is not recommended.
4. Repeat for each organization until all configurations are actioned.

Once everything is matched, the RMM setup is complete. At any time, you can come back to these instructions to discover and match new organizations and configurations from your RMM.

RMM logic

Before an organization, site, location, or company in an RMM tool can sync with IT Glue to create an IT Glue organization, you must add at least one configuration to it. If there are none and the organization does not already exist in IT Glue from any other source, then it will not appear in IT Glue. In this case, you will need to create it manually.

Only RMM companies that have at least one RMM record will sync into IT Glue.

Related articles

• Overview of client onboarding steps