Deploy with NinjaOne. Verify coverage in InventoryOS.

Use NinjaOne to roll out InventoryOS agents. Windows and macOS scripts are already documented. Then connect the NinjaOne integration so you can see which devices have verified NinjaOne coverage, and which do not, per client org.

InventoryOS sits beside NinjaOne. NinjaOne remains the RMM and remote-action layer. InventoryOS is the live inventory and coverage-verification layer that reconciles NinjaOne device presence against enrolled agents, so you can catch deploy gaps before audits, QBRs, or awkward client calls.

Why “RMM said installed” is not enough

Most MSPs already live in NinjaOne for remote management, scripting, and patch. The failure mode is uneven inventory proof across dozens of client orgs.

Gaps show up when:

• New devices outpace enrollment. A laptop shows up in NinjaOne faster than the InventoryOS agent lands, or the reverse.
• Enrollment-key drift. Org custom fields are missing, a location override blocks the key, or a single-device Preset parameter is needed when the org key is not visible.
• Partial reinstalls. Older script re-runs, file locks, or broken agents that looked like SUCCESS in automation history.
• Multi-tenant sprawl. New sites, mergers, or tribal “we deployed it” knowledge with no cross-org ledger.
• RMM inventory and the ITAM ledger do different jobs. NinjaOne owns remote actions and agent state. The multi-org coverage ledger across live inventory and stack connectors is a separate view.

NinjaOne remediates and deploys. InventoryOS sits beside it as the live inventory and coverage-verification layer.

Related: ITAM vs RMM · Huntress coverage verification · MSP multi-org.

Part A. Deploy InventoryOS agents from NinjaOne

This is the high-level path. The linked docs have the click-by-click screens.

Windows

1. Create or confirm the InventoryOS client org and copy its enrollment key.
2. In NinjaOne, set the organization custom field inventoryosenrollmentkey to that org’s enrollment key.
3. Add a NinjaOne Automation script (PowerShell, Run as System) using a fresh download of the InventoryOS NinjaOne Windows install script. Paste the current file from docs. A saved copy from an older download can leave agents broken on re-run.
4. Run it against the target devices. The current script resolves the enrollment key (parameter, then org custom fields, then CLI and environment fallbacks), installs missing .NET 8 and WebView2 when needed, and skips healthy agents on re-run.
5. Confirm devices appear under Agents in InventoryOS. Hostname and OS populate within minutes.

Docs: NinjaOne RMM deployment (Windows) · enrollment key on a single device · Windows repair script when a prior re-run left agents broken.

macOS

1. Use the same InventoryOS org and enrollment key model.
2. Put a fresh copy of the documented NinjaOne macOS install script (.sh) into Automation.
3. Confirm the arch-aware install (Intel and Apple Silicon) and that the agent checks in.

Docs: NinjaOne RMM deployment (macOS).

Part B. Verify NinjaOne coverage against live inventory

After agents are checking in, connect the product integration so coverage is proven.

1. Agents keep inventory live. Windows, macOS, and mobile check in so you have a current device list per org.
2. Connect NinjaOne. In NinjaOne, open Administration, then Apps, then API, then Client app IDs. Add a client app with platform API Services (machine-to-machine), grant type Client credentials, and Monitoring and Management scopes. In InventoryOS, open Software, then Integrations, then NinjaOne, and enter the instance URL, client ID, and client secret.
3. Map orgs. Map each NinjaOne organization to the matching InventoryOS client org. Suggestions can appear when names align.
4. Sync devices. InventoryOS pulls NinjaOne device data for mapped orgs. Mapped orgs sync on a recurring schedule.
5. Match devices. Matching uses service tag or serial and hostname. A device that cannot be matched keeps a status so you can see it.
6. See coverage gaps. Agents shows InventoryOS devices that lack verified NinjaOne coverage, and NinjaOne agents that are not represented in InventoryOS.
7. Close gaps in the right tool. Fix deploy and enrollment in NinjaOne automation, or with InventoryOS installers. InventoryOS stays the cross-org proof layer.
8. Re-check after changes for audits, QBRs, and insurance questionnaires.

The coverage view on Agents lists both sides of the gap: InventoryOS devices missing verified NinjaOne coverage, and NinjaOne devices that never landed in InventoryOS. Open it per client org, or across organizations, after a sync.

Workflow for techs

Onboard, deploy, verify, then re-check.

1. Onboard the client org in InventoryOS. See MSP multi-org.
2. Set the NinjaOne org custom field to that org’s InventoryOS enrollment key.
3. Deploy with NinjaOne Automation (Windows, macOS, or both).
4. Confirm agents online in InventoryOS Agents.
5. Connect NinjaOne if it is not connected yet, and map the NinjaOne org to the InventoryOS org.
6. Sync, then open the coverage and gap views for that org.
7. Triage missing InventoryOS agents, unmatched NinjaOne devices, and mapping or serial and hostname issues.
8. Re-verify after remediation.

A strong first week is an agent online plus at least one integration, or a compliance rule. NinjaOne is a natural first connector for MSPs already living in that RMM. Software rules are covered in compliance rules.

Same pattern for the rest of the stack

NinjaOne is the RMM deploy-and-verify story because the product includes both documented RMM scripts and a live coverage integration. The same coverage-verification pattern applies to EDR connectors MSPs already run, including Huntress, SentinelOne, Malwarebytes, and Webroot. How that sits beside remote management is in ITAM vs RMM.

Naming those products describes coverage verification in the product. Buyers already pay for RMM and security tools. InventoryOS shows where coverage is missing and keeps device inventory honest. It is a complementary seat.

For the wider device-management picture, see the MSP device management guide and spreadsheet vs inventory tool.

FAQ