Enterprise Client Deployment Guide
SCCM, Intune, Jamf, GPO, silent install, zero-touch registration, and multi-platform packaging.
Last updated: February 15, 2026
The Ambient platform supports enterprise deployment via multiple methods. The endpoint agent includes MSI, NSIS, PKG packaging, config file and environment variable pre-configuration, and auto-registration.
Supported Deployment Methods
Windows
| Method | Package | Install Command |
|---|---|---|
| SCCM | MSI or NSIS | msiexec /i AmbientAgent.msi /quiet or Setup.exe /S |
| Intune | Win32 (wrapped MSI/NSIS) | Same as above |
| Group Policy | MSI | Assign or Publish via GPO |
| PDQ Deploy | MSI or NSIS | Silent install |
| Chocolatey | .nupkg (from MSI) | choco install ambient-agent |
| Ansible | MSI/NSIS | win_package or win_chocolatey |
macOS
| Method | Package | Install Command |
|---|---|---|
| Jamf Pro | PKG or DMG | installer -pkg AmbientAgent.pkg -target / |
| Munki | PKG in repo | managedsoftwareupdate -i |
| Intune for Mac | PKG (wrapped) | MDM push |
| Ansible | PKG | installer or command |
Linux
| Method | Package | Install Command |
|---|---|---|
| Ansible | deb/AppImage | apt or copy + chmod |
| Puppet | deb | package resource |
| Manual | deb / AppImage | dpkg -i or run AppImage |
Packaging Outputs
| Platform | Format | Use Case |
|---|---|---|
| Windows | NSIS (.exe) | General, Intune Win32 |
| Windows | MSI | SCCM, GPO |
| macOS | DMG | Manual, Jamf |
| macOS | PKG | Jamf, Munki, MDM |
| Linux | deb | apt, Ansible |
| Linux | AppImage | Portable |
Silent Install Commands
Windows NSIS:
"Ambient Agent Setup 1.0.0.exe" /S
Windows MSI:
msiexec /i "Ambient Agent 1.0.0 x64.msi" /quiet /norestart
macOS:
sudo installer -pkg "Ambient Agent-1.0.0.pkg" -target /
Linux:
sudo dpkg -i ambient-agent_1.0.0_amd64.deb
Pre-Configuration for Zero-Touch
Config File Paths
- Windows:
C:\ProgramData\Ambient\agent-config.json - macOS:
/Library/Application Support/Ambient/agent-config.json - Linux:
/etc/ambient/agent-config.json
Config File Schema
{
"serverUrl": "https://api.ambient.company.com/api/v1",
"enrollmentCode": "XXXX-XXXX-XXXX",
"tenantId": "optional-tenant-guid",
"silentMode": false
}
Environment Variables
| Variable | Purpose |
|---|---|
AMBIENT_API_URL | API base URL |
AMBIENT_ENROLLMENT_CODE | Enrollment code for auto-registration |
AMBIENT_TENANT_ID | Tenant ID hint |
AMBIENT_SILENT_MODE | true or 1 for silent mode |
Environment variables override the config file. Set before first agent run.
Quick Runbooks
SCCM
- Import MSI as Application
- Detection: MSI Product Code
- Install:
msiexec /i "Ambient Agent 1.0.0 x64.msi" /quiet /norestart - Deploy
agent-config.jsonvia Baseline before or with agent
Intune
- Wrap MSI with IntuneWinAppUtil
- Create Win32 app, upload
.intunewin - Install command:
msiexec /i "Ambient Agent 1.0.0 x64.msi" /quiet - Deploy config via Configuration Profile or script
Jamf Pro
- Upload PKG to Packages
- Create policy with package, trigger (e.g. Enrollment Complete)
- Pre-config: Policy script to write
agent-config.jsonto/Library/Application Support/Ambient/
Group Policy
- GPO → Computer Config → Software installation → Assign MSI
- GPO Preferences → Files to create
C:\ProgramData\Ambient\agent-config.json
For full details, deployment scripts, and SSO integration, see the Admin Deployment Guide or contact enterprise@ziviso.africa.