Addigy Agent Deployment
Executes Install Addigy Agent [Macintosh] script on the machines where Addigy Agent deployment is enabled and either of "MacManage" or "MacManageHelper" applications are not installed.
Documents covering Apple's macOS and its applications
View all tagsExecutes Install Addigy Agent [Macintosh] script on the machines where Addigy Agent deployment is enabled and either of "MacManage" or "MacManageHelper" applications are not installed.
This solution provides automated deployment of the Addigy agent to macOS devices using NinjaOne. It utilizes a compound condition to detect if the agent is missing (checking for `MacManage` or `MacManageHelper` applications) and deploys it only when explicitly enabled via a custom field. The solution supports dynamic configuration of Addigy Organization and Policy IDs at the organization level to ensuring devices report to the correct management bucket.
This content is designed to install Blackpoint on Windows and macOS devices, and also supports uninstallation when required.
This script is used to the install the BlackPoint AnapAgent on the MacOS machines. The script used run time variable or Ninja custom fields to retrieve the necessary authentication information.
This compound condition is used to deploy the Blackpoint on macos.
This script fully removes the BlackPoint SNAP agent from macOS systems, including all related services, binaries, and configuration components. It stops and unloads associated launch daemons, to prevent the service from running during removal.
This script is used to show the FileVault status on macOS devices by updating the NinjaRMM custom field `cPVAL FileVault Status` to indicate whether FileVault is enabled or not.
Controls Addigy agent auto-deployment for macOS devices. Choose Enable to deploy agents at the selected level; choose Disable to prevent deployment. Device > Location > Organization in precedence.
Store the Addigy Organization ID here for automatic application to all devices. If not set, provide Org ID as a runtime variable when running the script.
Stores the Addigy Policy ID for this organization. Ensures all macOS devices report to the correct policy bucket in Addigy for proper management and compliance.
Choose the operating system to activate the auto deployment of the BlackPoint Agent. Auto deployment can be enabled for Windows machines only or for both Windows and Macintosh computers.
Holds the Blackpoint macOS authorization token for agent deployment.
This custom field stores the FileVault status on macOS devices fetched by the automation "Check FileVault Status" to indicate whether it is enabled or not.
Enables Threatlocker auto-deployment for Windows or both Windows and Macintosh machines at the organization level.
Enable this custom field to exclude the location or device from Threatlocker Deployment.
Stores the Threatlocker group key for agent deployment on Macintosh machines
This document contains the custom fields that are used in the CW RMM to Ninja migration
This solution is built to perform the CW RMM to Ninja migration.
This agent procedure checks the update channel for Microsoft Office on macOS endpoints and updates the corresponding custom field. It outlines the necessary steps to implement the procedure, including dependencies, export/import instructions, and expected output for successful execution.
This document provides a comprehensive guide for deploying and managing the Huntress Agent on both Windows and macOS machines, including installation, uninstallation, and repair processes, along with associated content for effective monitoring and management.
Downloads and installs the Addigy Agent using dynamic NinjaRMM parameters (Org ID and Policy ID).
This document outlines an internal monitor that detects all computers whose associated client has the Enable Webroot Deployment EDF checked, while ensuring there are no associated location or computer exclusions. It includes dependencies and target operating systems.
This group contains the endpoint where the Ninja deployment failed.
This group contains the endpoint where the Ninja Deployment succeeded.
This group contains the endpoints where the Ninja RMM deployment is enabled, the software "NinjaRMMAgent" is missing, and the custom field "Ninja Deployment Result" is blank.
This script deploys the NinjaRMMAgent to MAC OS, based on the article provided below: https://ninjarmm.zendesk.com/hc/en-us/articles/27524794230669-NinjaOne-Agent-Installation-Agent-Tokenization. It depends on the Authorization token, which will be kept in the company or site custom fields.
This document outlines the procedure for setting the update channel for Microsoft Office on macOS endpoints, including the available channels and implementation steps for exporting and importing the agent procedure in VSA RMM.
Triggers the auto-deployment script for Threatlocker on Macintosh machines where deployment is enabled
This script deploys threatlocker agent on Mac machines
This document outlines the procedures for managing Webroot Software within ConnectWise Automate, including installation, configuration, and auditing processes. It covers system requirements, plugin installation, and automatic deployment strategies for both Windows and macOS systems.
This document outlines the creation of a custom field that indicates whether an endpoint is compatible or provides reasons for incompatibility, including various conditions such as outdated operating systems or PowerShell versions.