officecom/oc-sentinel
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 21 Wiki Activity

Add NinjaOne bootstrap deployment script
Some checks failed
OfficeCom Sentinel Client / validate-client (push) Successful in 24s
Details
OfficeCom Sentinel Client / build-client-windows (push) Has been cancelled
Details

Browse Source
This commit is contained in:
OfficeCom Codex
2026-07-25 01:34:52 +02:00
parent ea90ddd1f6
commit f9f4d862bf
2 changed files with 105 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/ocsentinel-deployment.md
View File

@@ -32,7 +32,16 @@ powershell -ExecutionPolicy Bypass -File .\build\build-release-manifest.ps1 `
## NinjaOne Tasks
Initial install/update:
Create a PowerShell script in NinjaOne named `OCSentinel - Installieren oder aktualisieren`.
Run it as `SYSTEM` in 64-bit PowerShell and copy the content of
`scripts/bootstrap-ocsentinel-ninja.ps1` into the NinjaOne script editor.
It is idempotent: new devices install the current package, while installed devices
only update when a newer manifest version is published.
Use it for the one-time rollout and, later, as the monthly update task. For an
initial validation scan, add `-RunInitialStatusScan` to the script parameters.
Installed-client update only:
```powershell
& "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" `