One native integration that can be setup within Hudu is N-Central RMM.
Before setting up your N-Central RMM integration, please read over our Understanding Integrations article to learn basic concepts and useful tips.
In order to set up an integration with N-Central RMM, you will need:
- Access to retrieve JWT Token from N-Central RMM.
- N-Central version 2024.3.
- Admin or Super-Admin user role within Hudu.
At any time, you can come back to your Hudu admin area >> Integrations >> N-Central RMM to make changes to the integration.
Integration Features
Hudu's integration with N-Central RMM allows you to sync over:
-
Customers.
- Create client spaces within Hudu directly from N-Central customers, or seamlessly merge them into existing (already created) client spaces.
-
Sites.
- Pull in Sites from customers in N-Central.
-
Devices.
- Pull device information from N-Central, sorted into asset layouts based on set sort rules.
What Hudu needs from N-Central RMM
- N-Central Domain.
- JWT Token.
Guides
Enabling Integrations
Integrations can be enabled at any point during your Hudu environment testing and/or during production. Integrations can be merged into your existing documentation based on set rules; providing the ability to start with integration setup, or easily connect them at a later date. To enable the N-Central RMM integration:
- Navigate to Hudu admin area >> Integrations.
- Select N-Able N-Central RMM from the list.
Obtaining the N-Central RMM Information
- Navigate to profile in the top right.
- Select API Access.
- Generate JSON Web Token.
As best practice, it is recommended to create a new user account specifically for the Hudu integration with N-Central. Additionally, "MFA Required" must be disabled for the N-Central user in order to use the API.
In Hudu:
- Enter your N-Central RMM Fully Qualified Domain Name (without the https).
- Enter your JWT Token.
- Save the Settings.
Make sure to test the integration for a successful connection before continuing; do not continue on until you see a connection successful message display.
Matching Companies
Before your companies (and their corresponding data) from N-Central RMM can be brought into Hudu, they must first be matched to companies that either already exist within your Hudu environment; OR to companies that you create now.
Hudu recommends matching one company first, for testing purposes, to ensure that your information comes over correctly.
- The first time your integration connection runs successfully, it will attempt to bring in customers from N-Central RMM; these are then added to the Matched Companies List of that integration.
- Navigate to Hudu Admin area >> Integrations >> and find N-Able N-Central RMM from the list. Click into it.
- It should now have a button that says Match Companies.
- Go through the list of companies and either bulk create/match all OR decide to:
- Match the company to an existing (already created) company in Hudu.
- Create a matched customer within Hudu from N-Central customer.
- Leave unmatched, customer (and corresponding data) will not be created/brought into Hudu.
- Once you have matched your companies, you must re-run the integration import to fill in all the data for the newly matched/created companies.
Select Sync Locations
The N-Central RMM integration requires you to Select a Sync Location for Locations as well as a Primary Sync Location for Configurations that serves as your "junk drawer" asset layout; storing the information that is being pulled in, but not otherwise told where to be placed.
- Navigate back to your Hudu admin area >> Integrations >> N-Central RMM ((Edit Settings)).
- Choose asset layouts (must be active asset layouts) from the list to designate as the primary sync locations.
If you don't see or have not created any asset layouts yet, you'll need to create these. Visit Asset Layouts for additional information!
Other Options
Choose which items, if any, you'd like to skip from being brought into Hudu.
- You have the option to skip importing:
- Devices. You can choose to skip.
- Locations. You can choose to skip.
Additional Options
Choose whether you would like the following additional options to be automatically applied:
- Auto-update names of Assets. If name is changed in N-Central RMM, the name will automatically be updated in Hudu.
- Auto-archive deleted devices. If a device is deleted in N-Central RMM, the device will automatically be moved to the Museum in Hudu.
- Do not update basic company details. This will prevent the company details from being changed in Hudu if they are changed in N-Central RMM.
- Sync detailed device information. This will bring over more device details such as, OS Features, Memory Information, OS Details, Media Access Devices, Folders, Motherboard Details, Network Adapters, Physical Drives, Processor Information, Patches, Applications, Ports, Services, Computer System Details, and Logical Devices.
Sort Rules
- Save your settings and stop/start your integration sync again to reflect your changes.
FAQ
Answer: Native integrations will automatically re-sync (update) every 3 hours.
You can also use either the global or the card-specific re-sync features to refresh native integration syncs at any point.
Answer: If the N-Central RMM sync has been loading for a significant amount of time (it can take up to 10 minutes), follow the steps below:
- Test the connection to ensure Hudu and N-Central RMM are communicating correctly.
- Verify your N-Central credentials.
- Refresh the page (while a sync is actively running).
- Stop the sync and restart the sync.
Answer: It should appear on subsequent re-syncs. If it is still not appearing, ensure that it has not been archived and still exists in your sort rules.
Notes: Active integrations sync automatically every 3 hours; manual re-syncs can be performed either within an integration’s settings page or by clicking the top right re-sync button.
Answer: Select the 'Sync detailed device information' check box on the N-Central Edit Settings page in Hudu to bring over OS Details, Memory Information, Physical Drives and more!
Answer: N-Central version 2024.3 is required for the integration to work.