Skip to main content

BlackPoint SnapAgent Deployment

Purpose

This content is designed to manage the deployment of Blackpoint across both Windows and MacOS devices. It automates the installation process to ensure consistent security coverage across supported endpoints. The uninstallation process must be performed manually by running script on target device and is not automated.

Associated Content

Compound Conditions

ContentTypeFunction
BlackPoint SnapAgent Installer - MacOSCompound ConditionUsed to target eligible macOS devices for automated Blackpoint installation.
BlackPoint SnapAgent Installer - Windows ServerCompound ConditionUsed to target supported Windows Server devices for automated Blackpoint installation.
BlackPoint SnapAgent Installer - Windows WorkstationsCompound ConditionUsed to target supported Windows Workstation devices for automated Blackpoint installation.

Automation

ContentTypeFunction
BlackPoint SnapAgent Installer - WindowsScriptInstalls the Blackpoint SNAP agent on Windows devices.
BlackPoint SnapAgent Installer - MacOSScriptInstalls the Blackpoint SNAP agent on macOS devices.
Blackpoint SnapAgent - Uninstall - (MacOS)ScriptUsed to manually uninstall Blackpoint SNAP-Defense from macOS devices when required.
Blackpoint SnapAgent - Uninstall - (Windows)ScriptUsed to manually uninstall Blackpoint SNAP-Defense from Windows devices when required.

Custom Field

ContentTypeFunction
cPVAL Blackpoint DeploymentCustom FieldControls deployment logic during automation and compound condition evaluation.
cPVAL BP AccountUIDCustom FieldStores the Blackpoint AccountUID used during authorization and deployment.
cPVAL BP Mac Auth TokenCustom FieldStores the Blackpoint macOS authentication token used by the macOS installer.
cPVAL BP Win CompanyEXECustom FieldStores the Windows-specific Company EXE installer reference for Blackpoint deployment.

Implementation

Step 1: Create the following Custom Field

Step 2: Import Automation Scripts

Import the following automation scripts:

Step 3: Configure the following Compound Conditions

Create three compound conditions targeting the appropriate device policies:

FAQ

Q: Does this automation include an automatic uninstall process?

A: No. Uninstallation is not automated and will need to be executed manually using the provided removal script when appropriate.

Q: What happens if Blackpoint is already installed on the device?

A: The detection script validates the installation and prevents unnecessary redeployment.

Q: Can I deploy only to selected operating systems?

A: Yes. The custom field supports selective deployment using values Windows, macOS, or Both.

Q: How often does the system check installation status?

A: The compound condition continuously monitors agent presence and triggers remediation only when required.

Q: Where do install parameters such as organization key or token come from?

A: These values are typically stored in protected custom fields and injected into the installer by the remediation script.

Q: Does the deployment process interrupt users or require reboot?

A: Installation runs silently without interrupting the user and does not require a reboot under normal circumstances.

Q: Can this be manually triggered for a single device?

A: Yes. Both installation and uninstallation tasks can be run on-demand via Automation.