Topic
This article answers frequently-asked questions about Linux patch management in NinjaOne.
Environment
NinjaOne Patching
Description
The following index represents common questions about working with patch management that our customers have asked and that our product management team has answered. Select a topic to continue.
- How Much Space Does the Endpoint Require to Perform Patching?
- Can I Run a Report That Returns a List of Servers That Did Not Install Approved Patches?
- Where Does the Patch Job Get Its Information?
- How Does NinjaOne's Linux Patching Determine Which Patches Apply to My Endpoint?
- How Does Linux Patching Handle Application Dependencies When Updates Require Older, Dependent Software?
- Does the Linux Patching Feature Copy New Applications from the Repository It Uses?
- What Is the Difference Between 'Reboot Immediately' and 'Reboot Automatically' in Linux Patching Options?
- Does NinjaOne Linux Patching Do Full Operating System (OS) Upgrades?
How Much Space Does the Endpoint Require to Perform Patching?
To scan for and apply patches, the target endpoint requires a minimum of 100 MB of available disk space in each of the following directory paths:
- /
- /opt
- /var
- /home
If the device does not have the required space, NinjaOne will notify you that it cannot proceed with the scan and apply processes.
Can I Run a Report That Returns a List of Servers That Did Not Install Approved Patches?
You can export a list of failed or pending patches from the System, Organization, or Device dashboard. Click the Patching tab, then navigate to OS patches and select any status.
Where Does the Patch Job Get Its Information?
NinjaOne finds patches based on the target device's configuration. If you configured the device to search for patches from a repository, NinjaOne feeds the data into its patch management interface.
How Does NinjaOne's Linux Patching Determine Which Patches Apply to My Endpoint?
The NinjaOne agent runs the appropriate command for the device to determine which patches are available. Depending on the Linux brand, the command could be APT, DNF, YUM, or Zypper.
How Does Linux Patching Handle Application Dependencies When Updates Require Older, Dependent Software?
NinjaOne relies on the package manager to resolve dependencies. For example, if one package requires an update for another package to work, NinjaOne will install both package updates.
Does the Linux Patching Feature Copy New Applications from the Repository It Uses?
Yes, NinjaOne uses the device's configured repository (or repositories).
What Is the Difference Between 'Reboot Immediately' and 'Reboot Automatically' in Linux Patching Options?
Both settings perform the same function.
Does NinjaOne Linux Patching Do Full Operating System (OS) Upgrades?
Due to the potential for system-breaking changes, NinjaOne does not currently support major version upgrades for Linux distributions. You can still perform these upgrades by leveraging NinjaOne's scripting features. Test thoroughly before deploying operating system upgrades at scale, as they can affect system stability, services, and configuration files.