NinjaOne Quick Deployment Guide

Topic

This guide covers the essential steps for deploying the NinjaOne agent in your environment, including creating an organization template, configuring installer settings, and choosing a deployment method for your endpoints.

Environment

NinjaOne Endpoint Management

Description

This deployment guide walks through creating a template organization, importing organizations, generating a NinjaOne agent installer, and deploying the agent to endpoints.

Select a category to continue:

Create an Organization Template
Import Organizations
Enable Installer Management
Obtain the Installation Details
Install the NinjaOne Agent
Additional Resources

Procedure

Follow these steps to deploy the NinjaOne agent to your endpoints.

This workflow is not currently available for FedRAMP customers. For FedRAMP deployment instructions, refer to NinjaOne Agent: How To Deploy a Generic Installer (FedRAMP) (login required).

Create an Organization Template

In NinjaOne, organizations control critical functionality such as:

Which remote access solution is on an endpoint
How policies are mapped to device roles
How devices are added to the platform

If you plan to have multiple organizations in your environment, creating the first organization as a template with the correct configurations will save you time and enable you to mass-create additional organizations via import.

Create an organization. Refer to NinjaOne Endpoint Management: Creating and Editing Organizations for instructions.
Configure your organization. You can make dozens of configuration choices when setting up an organization. The following table describes the most important configurations:

Configuration	Description
Policy Mapping	Policies define how NinjaOne manages devices. A single policy manages every device. Organizations define how each device, based on its role, is mapped to a policy when added to NinjaOne. Having the correct policy mapping can save a lot of time during the deployment process. Use default policies: If you have not created any new policies, you can leave the default policy mapping. Custom policies: If you have created custom device roles and custom policies, you must map each device role to a policy type. Custom device roles let you map custom roles to custom policies that provide specific management instructions for those roles. Refer to NinjaOne Endpoint Management: Device Roles to learn more.
Systray icon	The systray icon gives end users the ability to interact with your team and the NinjaOne agent in predefined ways. For example, you can add: The help form. Your support phone number. A contact email. You can set up the systray icon once for all your organizations to streamline configuration.
Device approval	This security setting defines whether a newly onboarded device: Goes directly into the NinjaOne dashboard (automatic). Needs an administrator to approve it (manual). Is rejected by default. We recommend setting device approval to Automatic during initial onboarding to avoid duplicating work.
Remote access	If your subscription includes remote access, activate the remote access solution of your choice when setting up your organization template. Key configurations to consider include remote access solution, end-user confirmation, and device roles.

Import Organizations

If you only plan to have a single organization in your NinjaOne instance, you can skip this step. This step allows you to import organizations via comma-separated values (CSV) so that each organization is configured the same as the template organization you created above. This can save you significant time. Refer to

Figure 1: Administration → General → Settings → Agent Installer (click to enlarge)

In the Agent installer settings window, activate Installer Management. If you are bulk-installing the agent onto multiple machines, activate Automatic token creation as well. NinjaOne will automatically create an installation token for each machine. When finished, click Update.

Figure 2: Agent installer settings (click to enlarge)

Obtain the Installation Details

From the NinjaOne system dashboard, click the Devices tab and select Agent Installers from the drop-down menu.

Figure 3: The Devices tab (click to enlarge)

In the Installers list, find the agent installer you wish to use and click anywhere within its row.

Figure 4: The installer list (click to enlarge)

The Installer details window opens, displaying the installer link and the install command, complete with the authentication token for this installer. You can use the command itself to install an agent on any device, but the token is device-specific. The link will vary based on the organization's region.

NinjaOne structures the install command differently depending on the device operating system (OS).

Example Installer Commands by Operating System

Microsoft Windows

  Invoke-WebRequest -Uri "https://app.ninjarmm.com/ws/api/v2/generic-installer/NinjaOneAgent-x86.msi"
  -OutFile ".NinjaOneAgent-x86.msi" msiexec.exe -i NinjaOneAgent-x86.msi TOKENID="the token value"

Apple macOS (PKG)

curl https://app.ninjarmm.com/ws/api/v2/generic-installer/NinjaOneAgent.pkg -L --output NinjaOneAgent.pkg
sudo echo ""the token value""  /tmp/.~; sudo installer -pkg NinjaOneAgent.pkg -target /

Debian Linux

curl https://app.ninjarmm.com/ws/api/v2/generic-installer/NinjaOneAgent-x86_64.deb -L --output NinjaOneAgent-x86_64.deb
sudo TOKENID="the token value" dpkg -i NinjaOneAgent-x86_64.deb

The token will appear in the Token field in the Installer details window and contains the approval for an installer to access NinjaOne resources.

Figure 5: Installer details (click to enlarge)

Installing the NinjaOne Agent

Now that you have set up all your organizations and created all your installers, you can deploy the NinjaOne agent to your endpoints. There are several deployment methods:

Manually install the agent on a machine: For a small number of devices, you can either physically visit the machine with a USB containing the NinjaOne agent or use an existing remote access tool to install the agent on endpoints manually, one by one. We only recommend this method for small organizations or in cases where no other option is feasible.
Send MSI links to end-users: If end-users have permissions to install applications on their endpoints, you can send them the direct Microsoft Installer (MSI) link to the installation file. This link is within Download Installer in the Installer details window, shown in Figure 5 above. We only recommend this method for small organizations or in cases where no other option is feasible.
Leverage Group Policy for Windows Devices: If you are using Microsoft Active Directory (AD), you can deploy the NinjaOne agent at scale via Group Policy. Refer to Custom Script: NinjaOne Agent Deployment by AD Immediate Scheduled Task GPO to learn more.
Deploy via Intune: If you are using Microsoft Intune, you can add NinjaOne and assign the application to end-user devices. Refer to NinjaOne Agent Installation: Deployment via Microsoft Intune. If you are using a Windows endpoint, refer to NinjaOne Integrations: Getting Started with the Microsoft Intune Integration.
Use NinjaOne's native Active Directory Discovery and Deployment: NinjaOne includes a native Active Directory Discovery and Deployment feature, which lets you see all your Active Directory organizational units (OUs) and deploy the NinjaOne agent ad hoc or on a schedule. You must first install the agent on your Active Directory server, then follow the instructions in our NinjaOne Endpoint Management: Active Directory Discovery and Deployment Dojo article.
Deploy via your existing RMM or Endpoint Management solution:
- Leverage your tool's native application deployment feature: Most endpoint management tools have a software deployment feature that enables you to install an application silently via MSI or executable (EXE) through your Remote Monitoring and Management (RMM) solution. Upload the NinjaOne installer to your existing tool and deploy the application using this functionality for the fastest deployment.
- Deploy NinjaOne through a PowerShell script: Most endpoint management tools can deploy a PowerShell script remotely. Use NinjaOne Academy's Migration from other RMM solutions (MAIN) scripts (login required) or the appropriate tools from our NinjaOne Endpoint Management: Mass-Deploying the NinjaOne Agent article to deploy the NinjaOne agent via PowerShell with your existing tool.

Our MSI installer is silent by default, so there are no command-line switches required to deploy it silently.

Additional Resources

The following resources will help you get the most out of NinjaOne:

NinjaOne Agent Installation: Quick Deployment Guide