BlackPoint SnapAgent Deployment
Purpose
The BlackPoint Deployment solution is designed to automate the deployment of the BlackPoint Agent on supported endpoints through ConnectWise RMM platform. It identifies machines that are configured for BlackPoint deployment but currently do not have the BlackPoint Agent installed and automatically deploys the agent based on the configured deployment settings.
The solution uses centralized configuration through ConnectWise RMM custom fields to control BlackPoint deployment behavior, including operating system selection, installer URL, macOS authentication details, customer ID, and deployment exclusions at the site and endpoint level.
Key Capabilities
-
Automated BlackPoint SNAP Agent Deployment
Automatically deploys the BlackPoint SNAP Agent on endpoints where deployment is enabled and the agent is not detected. -
Centralized Deployment Configuration
Uses ConnectWise RMM custom fields to centrally manage BlackPoint configuration settings, including:- Target Operating System
- Windows Installer URL
- macOS Authentication Token
- macOS Customer ID
- Deployment Enablement
-
Site and Endpoint-Level Exclusions
Provides the ability to exclude specific sites or individual endpoints from BlackPoint SNAP Agent deployment without changing the global deployment configuration. -
Automatic Installer Download
Downloads the configured BlackPoint installer during execution to ensure the appropriate agent installer is deployed. -
Silent Installation and Upgrade Support
Installs or upgrades the BlackPoint SNAP Agent silently without requiring user interaction. -
Installation Validation
Verifies successful installation by confirming that the BlackPoint SNAP Agent service is installed and available after deployment. -
Multi-Platform Deployment Support
Supports BlackPoint SNAP Agent deployment across supported Windows and Macintosh devices.
Associated Content
Custom Fields
| Name | Level | Type | Purpose |
|---|---|---|---|
| BP_Enable_Deployment | Company | DropDown | Custom field to select the target operating system for BlackPoint SnapAgent deployment. |
| BP_WIN_URL | Company | Text | The direct URL used to download the BlackPoint Windows agent installer. This URL is used by the Install SnapAgent to retrieve the latest installer package and install the BlackPoint agent on the target Windows machine. |
| BP_MAC_Authentication_Token | Company | Text | Unique BlackPoint Authentication token to be used during the installation of the BlackPoint SNAP agent on MacOS endpoints. |
| BP_Mac_Customer_ID | Company | Text | Unique BlackPoint Account UID used to identify and link endpoints to the correct BlackPoint account. This is for MAC agents. |
| Exclude_BP_Deployment_Site | Site | Flag | Custom Field to exclude Site from BlackPoint SnapAgent Deployment. |
| Exclude_BP_Deployment_Endpoint | Endpoint | Flag | Custom Field to exclude Endpoint from BlackPoint SnapAgent Deployment. |
Group
| Name | Purpose |
|---|---|
| Deploy BlackPoint SnapAgent | This group contains machines that are opted for BlackPoint SnapAgent deployment but currently do not have the BlackPoint SnapAgent installed. |
Task
| Name | Purpose |
|---|---|
| Install BlackPoint SnapAgent | Deploy and update the BlackPoint SnapAgent on Windows and macintosh machines by downloading the latest installer, running the installation silently, and validating that the agent has been successfully installed. |
Implementation
Step 1: Create the Following Custom Fields
Create all the custom fields listed below in ConnectWise RMM. These are required for the solution to function correctly.
- BP_Enable_Deployment
- BP_WIN_URL
- BP_MAC_Authentication_Token
- BP_Mac_Customer_ID
- Exclude_BP_Deployment_Site
- Exclude_BP_Deployment_Endpoint
Step 2: Create the Group
Create the dynamic group that will automatically target the enabled machines.
Step 3: Create the Task
Set up the script that will run on the targeted endpoints.
Step 4: Schedule the Task
Schedule the Install BlackPoint SnapAgent to run once per day against the Deploy BlackPoint SnapAgent , as described in the Schedule Task section of the task's document.
FAQ
Q: How does the BlackPoint SNAP Agent Deployment solution work?
The solution evaluates the BlackPoint deployment settings configured through ConnectWise RMM custom fields and identifies machines where BlackPoint SNAP Agent deployment is enabled but the BlackPoint SNAP Agent is not currently installed. The Install BlackPoint SnapAgent task then downloads the configured installer, installs the agent silently, and validates successful installation.
Q: Which devices are targeted for BlackPoint SNAP Agent deployment?
Devices are targeted based on the configured operating system, deployment settings, and exclusion rules. Machines must have BlackPoint deployment enabled and must not be excluded through the Exclude_BP_Deployment_Site or Exclude_BP_Deployment_Endpoint custom fields.
Q: What configuration is required for BlackPoint deployment?
BlackPoint deployment requires the appropriate deployment operating system selection and installer configuration. Windows deployment requires a valid Windows installer URL, while macOS deployment requires a valid BlackPoint authentication token and customer ID.
Q: What happens if the BlackPoint authentication token is missing?
A valid BlackPoint authentication token is required for macOS deployment. If the authentication token is not available through either the client-specific custom field or configured parameter, the macOS installation task will fail and the agent will not be deployed.
Q: What happens if the BlackPoint Customer ID is missing?
A valid BlackPoint Customer ID is required for macOS deployment to associate the endpoint with the correct BlackPoint account. If the Customer ID is not available through either the client-specific custom field or configured parameter, the macOS installation task will fail.
Q: How can I exclude a specific site from BlackPoint SNAP Agent deployment?
Use the Exclude_BP_Deployment_Site custom field to exclude an entire site from BlackPoint SNAP Agent deployment. Any endpoint within an excluded site will not be targeted for deployment.
Q: How can I exclude an individual endpoint from deployment?
Use the Exclude_BP_Deployment_Endpoint custom field on the specific endpoint to prevent BlackPoint SNAP Agent deployment on that machine.
Q: Will the deployment task install the BlackPoint SNAP Agent on both Windows and macOS?
Yes. The Install BlackPoint SnapAgent task supports both Windows and macOS endpoints. The configured operating system selection determines the appropriate deployment process and installation method.
Q: What happens if the BlackPoint SNAP Agent is already installed?
The deployment task checks for an existing BlackPoint SNAP Agent installation before starting the deployment. If the agent is already installed, the task will not start a new installation.
Q: Can the deployment task update an existing BlackPoint SNAP Agent installation?
The deployment task is designed to deploy the BlackPoint SNAP Agent when it is not detected. Existing installations are checked before deployment to prevent unnecessary installations.
Q: When will changes to BlackPoint custom fields take effect?
Changes made to the BlackPoint deployment custom fields will take effect when the Install BlackPoint SnapAgent task runs again against the targeted endpoint.
Q: What happens if the BlackPoint installation fails?
The installation task will return an error if the installer cannot be downloaded, required configuration values are missing or invalid, or the BlackPoint SNAP Agent cannot be verified after installation. Review the task output and installation logs for additional troubleshooting information.
Q: Does the solution require administrator privileges?
Yes. The Install BlackPoint SnapAgent task requires administrative privileges on the endpoint to download and install the BlackPoint SNAP Agent successfully.
Q: Can deployment settings be different for different clients?
Yes. BlackPoint deployment settings are managed through ConnectWise RMM custom fields, allowing each client, site, or endpoint to have its own deployment configuration and exclusions.
Changelog
2026-08-25
- Initial version of the document