This isn’t just about pushing updates, it’s about driving operational excellence and reducing risk through smart automation. Whether you’re scaling your MSP or fine-tuning your internal standards, this is the foundation of a mature patching strategy.
Step by Step:
- Log in as an administrator and confirm you have access to Agent Policies. Also make sure the NinjaOne WinGet third-party app is installed and enabled. If it’s not there, add it from the Apps area in the upper right.
- Once WinGet is enabled, you can use package management directly inside NinjaOne policies.
- Navigate to Agent Policies and open your standard Windows workstation policy.
- Scroll down inside the policy to the Software section.
- Review the general software settings, including enabling or disabling the software feature, reboot behavior when users are logged in or not, scan frequency for updates, update schedules, and any overrides or rejected patches.
- Review the software packages already listed in the policy and note the available sources, such as NinjaOne and WinGet, along with how patches are approved and whether software installs if it isn’t already present.
- Click the Add Software button on the right side of the Software section.
- Search for the application you want to deploy, such as Mozilla Firefox.
- Select the NinjaOne source when available, then add the package to the policy.
- Use the ellipsis menu next to the software and select Edit to change its behavior.
- Configure the package to automatically approve critical patches, automatically approve recommended patches, and install the software if it is not already present.
- Click Save in the upper right corner to apply the policy and make it live.
- Repeat this process for any additional software packages available through the NinjaOne or WinGet sources, which include thousands of supported applications.
- Once complete, the software deployment and patching settings will be enforced across the endpoints covered by the policy.