Skip to main content

SentinelOne Management Server Url Validation

Purpose​

This solution validates whether the SentinelOne Management Server URL detected on endpoints matches the value configured for the client in NinjaRMM. It automatically flags discrepancies and generates remediation tickets through ConnectWise Manage when mismatches are detected.

Associated Content​

Custom Fields​

ContentDefinition ScopeRequiredTypeApplicable OSFunction
cPVAL SentinelOne KeyOrganizationConditionalTextAllStores the SentinelOne Site Key for endpoint organization (only required if not using existing field)
cPVAL SentinelOne Mgmt Server DiscrepancyDeviceTrueCheckBoxWindowsFlags when endpoint's management URL differs from configured value
cPVAL SentinelOne Mgmt Server UrlDeviceTrueTextWindowsStores actual management URL detected on endpoint

Automation​

ContentFunction
SentinelOne Management Console ValidationCompares endpoint's S1 management URL with configured value and flags discrepancies

Condition​

ContentFunction
SentinelOne Management Console ValidationTriggers daily validation and ticket creation for discrepancies

CW Manage Ticket Template​

ContentFunction
SentinelOne Management ConsoleConfigures how tickets are generated in ConnectWise Manage

Implementation​

Step 1: Create Custom Fields​

  1. cPVAL SentinelOne Mgmt Server Discrepancy
  2. cPVAL SentinelOne Mgmt Server Url
  3. Optional: cPVAL SentinelOne Key
    Only create this if you don't already have a custom field storing SentinelOne installation tokens

Step 2: Import Automation​

Import the SentinelOne Management Console Validation automation

Step 3: Create Validation Condition​

Create the SentinelOne Management Console Validation condition

Step 4: Configure CW Manage Template​

  1. Ensure ConnectWise Manage app is enabled
  2. Configure SentinelOne Management Console ticket template
    Verify field mappings with your consultant as environments vary

FAQ​

1. Do I need to create the 'cPVAL SentinelOne Key' custom field?​

Only create this field if you don't already have a custom field storing SentinelOne installation tokens. If you have an existing field, use its name in the automation's S1 Key Custom Field Name parameter instead.

2. How often does the validation run?​

The condition runs the automation once per day. Discrepancies are flagged immediately upon detection.

3. Where are discrepancies shown?​

Discrepancies appear in:

  • Device's cPVAL SentinelOne Mgmt Server Discrepancy checkbox
  • Generated ConnectWise Manage tickets
  • Automation activity details

4. Why are my CW Manage tickets not generating correctly?​

Verify:

  1. ConnectWise Manage app is properly connected
  2. Ticket template field mappings match your environment
  3. Required custom fields exist and have values
  4. Technician permissions allow ticket creation

5. Can I use existing custom fields instead of creating new ones?​

Yes, for the Site Key/Token field. Specify your existing field name in the S1 Key Custom Field Name parameter. The discrepancy and URL fields are required as they're updated by the automation.

6. Can I run the validation manually?​

Yes, execute the automation manually on any endpoint to validate its configuration immediately.

7 How to use the script's runtime parameter?​

Set runtime parameters:

  • S1 Key Custom Field Name:
    • Leave blank if using cPVAL SentinelOne Key
    • Enter name of existing custom field if storing token elsewhere