78 docs tagged with "macOS"

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.

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.

Validation script for the NinjaRMM self-healing solution on macOS. Checks if the background monitoring daemon and script are intact and triggers remediation if missing.

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.

Counts consecutive detection cycles where a prompt was missed. Resets to 0 on success or reboot.

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.

Sets the urgent message displayed when all deferrals are exhausted. Supports message substitution variables.

Specifies the grace period (in minutes) after the user acknowledges the final prompt before the system actually restarts.

Sets how long (in seconds) the final reboot prompt stays visible before forcing the reboot automatically.

Records the exact date/time the machine first missed a reboot prompt due to a locked screen or no logged-in user.

Stores the timestamp of the last reboot prompt sent to the device. Updated automatically by the automation script.

This field stores a comma-separated list of local administrator accounts on this macOS device. It automatically excludes the default root account and hidden system accounts to only show actual user or service accounts.

Max consecutive missed prompts (due to locked screen or no user) allowed before forcing a reboot. Set to 0 to disable.

Manual override checkbox to force a reboot prompt cycle on a specific device, regardless of Windows pending reboot status.

Allows unattended or forced reboots to proceed even during configured suppress windows or weekends.

When enabled, allows the system to reboot immediately without showing a prompt if no user is currently logged in.

Specifies the size of each button in WIDTHxHEIGHT format.

Specifies the font size (in pixels) for the button text.

Specifies the font family for the button text.

Specifies how many times a user will be prompted (allowed to defer) before the reboot becomes mandatory.

Defines the wait time (in hours) between consecutive reboot prompts to prevent spamming the end-user.

CLIENT-level master switch for the macOS reboot prompt solution. Enable opts in client-wide; Disable opts out; if unset, defers to the per-device cPVAL Pending Reboot.

Specifies the local file path or public URL for the header image displayed at the top of the reboot prompt.

Specifies the local file path or public URL for the small icon displayed next to the prompt title.

Specifies the size of the header image/logo box in WIDTHxHEIGHT format.

Sets the custom message displayed to users. Supports message substitution variables (e.g., PromptsLeft, PromptIntervalHours).

Specifies the overall size of the reboot prompt window in WIDTHxHEIGHT format.

When enabled, prevents the reboot prompt from appearing on Saturdays and Sundays.

Specify a 24-hour time range (HHmm-HHmm) to suppress prompts (e.g., 1800-0900 blocks prompts from 6:00 PM to 9:00 AM).

Specifies the size of the message text box area in WIDTHxHEIGHT format.

Specifies the font size (in pixels) for the main message text.

Specifies the font family for the main message text (e.g., Arial, Calibri).

Selects the visual theme (Dark or Light) for the reboot prompt window to match organizational branding.

Sets how long (in seconds) the regular reboot prompt stays visible before automatically closing and counting as a deferral.

Sets the title displayed at the top of the reboot prompt window.

Specifies the size of the title bar area in WIDTHxHEIGHT format.

Specifies the font size (in pixels) for the title bar text.

Specifies the font family for the title bar text.

Defines the number of uptime days that must pass before prompting for a reboot. Setting to 0 disables this trigger.

Controls whether a prompt appears on Windows machines when Windows reports a reboot pending status via Registry keys.

Enables ThreatLocker auto-deployment for Windows or both Windows and Macintosh machines at the organization level.

Stores the ThreatLocker group key for agent deployment on Macintosh machines

Tracks the number of reboot prompts sent to the device. Updated automatically by the automation script.

This script uses to create or update a local administrator account using runtime-provided credentials and ensures the account is a member of the local Administrators group.

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.

The script is designed to ensure the NinjaRMM Agent remains operational and automatically recovers from service failures on macOS.

Condition script for the NinjaRMM Agent Self-Heal solution on macOS. Validates the background monitoring setup and triggers remediation if missing.

Fetches local admin users (excluding root/system) and writes them to a custom field (cPVAL Mac Admins).

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).

Installs Claude Desktop and its Cowork feature on macOS.

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 solution provides an automated, device-resident mechanism to ensure the NinjaRMM Agent and related services remain operational and automatically recover from failures on Windows and macOS.

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.

OmniPrompt is a cross-platform, Go-based reimplementation of the original .NET Prompter tool, built to run natively on both Windows and macOS from a single codebase.

A comprehensive, cross-platform solution for NinjaOne that provides an automated, user-friendly mechanism to handle pending reboots on Windows and macOS devices.

Action script for the "Reboot Pending Prompt" solution on macOS. Downloads the OmniPrompt GUI utility to prompt the logged-in user and initiates a reboot based on their response or policy enforcement.

Detection script for the "Reboot Pending Prompt" solution on macOS. Determines if a Mac requires a reboot and if the current conditions permit a user prompt.

Compound condition that triggers the user reboot prompt sequence on macOS when the detection script identifies a pending reboot state.

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.