Getting Started with Patch Management
Patch Management Agent Installation
GETTING STARTED WITH PATCH MANAGEMENT
To get started with this service, an agent needs to be installed on all relevant hosts that need Patch Management. For us to put together the installation materials for you to install this agent, we need to gather some information about the devices in your environment.
Step 1: Please fill out the Patch Management Questionnaire
Step 2: After we receive this form, we will put together the installation materials and send them to y ou within 48 HOURS.
Now you are ready to install the agents. We have a list of instructional materials on how to install the agents on your hosts, whether you want to do it manually on each host or through another Alternate Installation Method.
INSTALLING THE PATCH MANAGEMENT AGENT MANUALLY
Option 1: Manual Install: Windows
Step 1: Download the installation materials onto the host.
Step 2: You will need to make sure your user has administrative rights to install the agent on the Windows host.
Step 3: Double click on the MSI package that we sent you.
Step 4: Click Yes to allow it to make changes.
Step 5: After a few minutes the process will finish and the window will close on its own, meaning the agent is installed on the host.
Option 2: Manual Install: Linux
For Linux machines, the installer must be run via command line. Please see the following instructions. These instructions work for RPM or Debian/Ubuntu.
RPM Types: Red Hat Enterprise Linux (RHEL), Fedora, CentOS
Method 1:
Step 1: Open a terminal
Step 2: Type “wget <rpm package link>”
Step 3: Replace <rpm package link> with a link to the RPM package, which we will have sent you
Step 4: Type “sudo rpm -i <rpm package name>”
Step 5: Type “ls /opt/NinjaRMMAgent/programfiles”
Step 6: Users should see NinjaRMM program files such as ninjarmm-linagent
Step 7: Type “sudo systemctl status ninjarmm-agent.service”
Step 8: Users should see an output of 'Active'.
Method 2:
Step 1: Open a terminal.
Step 2: Navigate to where the RPM package is stored. (For example, cd ~/Downloads if you downloaded the RPM installer from the Ninja web interface directly onto the machine, or if you just put it there after downloading ).
Step 3: Type “sudo rpm -i <rpm package name>”
Step 4: Type “ls /opt/NinjaRMMAgent/programfiles”
Step 5: Users should see NinjaRMM program files such as ninjarmm-linagent.
Step 6: Type “sudo systemctl status ninjarmm-agent.service”
Step 7: Users should see an output of 'Active'.
Types: Debian and Ubuntu
Method 1:
Step 1: Open a terminal
Step 2: wget <deb package link>
Step 3: Replace <deb package link> with a link to the Debian package, which XeneX will have sent you
Step 4: Type “sudo dpkg -i <deb package name>”
Step 5: Type “ls /opt/NinjaRMMAgent/programfiles”
Step 6: Users should see NinjaRMM program files such as ninjarmm-linagent.
Step 7: sudo systemctl status ninjarmm-agent.service
Step 8: Users should see an output of 'Active'.
Method 2:
Step 1: Open a terminal.
Step 2: Navigate to where the DEB package is stored. (For example, cd ~/Downloads if you downloaded the Debian installer from the Ninja web interface directly onto the machine or donwloaded it and put it there.)
Step 3: Type “sudo dpkg -i <deb package name>”
Step 4: Type “ls /opt/NinjaRMMAgent/programfiles”
Step 5: Users should see NinjaRMM program files such as ninjarmm-linagent.
Step 6:Type “sudo systemctl status ninjarmm-agent.service”
Step 7: Users should see an output of 'Active'.
Option 3: Manual Install: MAC
Step 1: Download the material sent to you to the host and place them in a folder together.
Step 2: You must have admin rights to execute installation.
Note: The installation package is preset with the information to connect to the appropriate cloud, so you only need to execute MSI package to install it.
Step 3: Click on the MSI package.
Step 4: If it asks you to allow app to make changes to your device, click “Yes”
Step 5: After a few minutes the process will finish and the window will close on its own, meaning the agent is installed on the host.
If there are many hosts that need services, then it may not be practical to use manual installation. See the Alternate Installation Methods page for mass installation methods.