Deploying Printix Client with NinjaOne
This post will show you how to deploy the Printix client using NinjaOne Documentation fields and a PowerShell script.
This post will show you how to deploy the Printix client using NinjaOne Documentation fields and a PowerShell script.
This script uses an undocumented Microsoft 365 API to check the latest version of Microsoft Office / 365 Apps and compares it to the installed version. It then sets a custom field in NinjaOne to indicate whether the latest security release (if there is one) is installed. It also sets fields to indicate the channel, installed version, update status and a card containing more detailed information.
This article uses an undocumented API to check the latest version of Microsoft Office / 365 Apps. This API is subject to change without notice and may stop working at any time. Use at your own risk.
PowerShell 5.1 as shipped with Windows 10 and 11 includes versions 1.0.0.1
of PackageManagement
and PowerShellGet
this old version cannot install most modern modules, nor can it self update properly.
In most cases fixing this runs into numerous issues with conflicting versions or files in use. This script is an adaptation of a script by Chris Taylor which takes a different approach to downloading the modules, has a bit more error checking and further installs the new PSResourceGet
module which is the replacement for PowerShellGet
.
This post will hold detection scripts for any serious CVE vulnerability that we write detection scripts for in the future. It will be updated and added to as new vulnerability detection scripts are written.
We're adding three role custom fields for devices with the Windows Laptop role:
Field Name | Field Type | Description |
---|---|---|
Driver Update: Reboot Required | Checkbox | Whether the latest driver update run requires a reboot to finalise. |
Driver Update: Last Run | Date/Time | The date and time the driver update script last ran successfully. |
Driver Update: Number Installed on Last Run | Integer | The number of driver updates installed on last script run. |
This post draws on multiple posts, click the link below to check out CyberDrain.com and support Kelvin's fantastic work for the MSP community.
You will find more excellent uses for NinjaOne custom fields on the Dojo, on Stephen Murphy's blog and on Luke Whitelock's blog.
Custom fields are a great way to store arbitrary data from your devices in NinjaOne. In this post I will explore a few examples, some using code from CyberDrain, which store data in NinjaOne custom fields.
This post was updated on 2022/12/22 to add a new script to run a speedtest on a device and store the results in NinjaOne.
Ninja doesn't currently support native AV monitoring via Windows Security Center, integrated AV packages are monitored but what if you need more?
We're going to create one role custom field for devices with the Windows Desktop or Windows Laptop role:
Field Name | Field Type | Description |
---|---|---|
Detailed AV Status | Multi-Line | Output for each configured AV on the system including name and status information. |
I'm the author of the NinjaOne PowerShell module so when I was looking for a quick way to identify duplicate devices I turned to that module and the NinjaOne API to find a solution.
This script is a quick way to identify duplicate devices in your NinjaOne instance. It can return a full listing of all devices grouped by serial number, it can also just return the ID, last contact date and serial number for the device with the oldest last contact date.
The NinjaOne agent gives you the ability to customise your system tray and add things like about text, email links, a help request form, a URL and other things. Unfortunately HaloPSA doesn't currently support hooking into NinjaOne's help request form (don't worry, we're talking to NinjaOne and Halo Service Solutions about this!) so we're left with a bit of a workaround as a solution.
Click the link below to check out the original post on CyberDrain.com and support Kelvin's fantastic work for the MSP community.
So firstly, if you haven't already, hit the giant orange button above to read the original blog post on CyberDrain.com to understand what this script is doing!