Admin Deployment Guide

This guide covers mass-deployment of the Ambient endpoint agent for IT administrators using enterprise management tools.

Overview

The Ambient agent can be deployed silently across Windows, macOS, and Linux using:

• Windows: SCCM, Intune, Group Policy, PDQ Deploy, Chocolatey
• macOS: Jamf Pro, Munki, Kandji, Mosyle, Intune for Mac
• Linux: Ansible, Puppet, Chef, Salt, Landscape

Prerequisites

1. Enrollment code – Generate in your Ambient workspace → Endpoints → Enrollment
2. API URL – Your Ambient API base URL (e.g. https://api.ambient.company.com/api/v1)
3. Agent installers – Download from the Download page

Pre-Configuration

Before deploying the agent, create agent-config.json:

{
  "serverUrl": "https://api.ambient.company.com/api/v1",
  "enrollmentCode": "YOUR-ENROLLMENT-CODE",
  "silentMode": true
}

Deploy this file to the config path before or with the agent install:

OS	Path
Windows	C:\ProgramData\Ambient\agent-config.json
macOS	/Library/Application Support/Ambient/agent-config.json
Linux	/etc/ambient/agent-config.json

Alternatively, set environment variables before first run:

• AMBIENT_API_URL
• AMBIENT_ENROLLMENT_CODE
• AMBIENT_SILENT_MODE (optional, true for headless)

Windows Deployment

SCCM (Configuration Manager)

1. Create Application → Manual
2. Deployment type: MSI
3. Install: msiexec /i "Ambient Agent 1.0.0 x64.msi" /quiet /norestart
4. Detection: MSI Product Code
5. Deploy config file via Configuration Baseline or separate Application

Intune (Endpoint Manager)

1. Use IntuneWinAppUtil to wrap the MSI or NSIS exe
2. Create Win32 app, upload .intunewin
3. Install: msiexec /i "Ambient Agent 1.0.0 x64.msi" /quiet (or Setup.exe /S for NSIS)
4. Detection: MSI Product Code or PowerShell script
5. Deploy config via Configuration Profile (custom OMA-URI) or remediation script

Group Policy

1. GPO → Computer Configuration → Software installation → New → Package
2. Assign the MSI
3. Group Policy Preferences → Files → Create C:\ProgramData\Ambient\agent-config.json

PDQ Deploy

1. New Package → Add MSI or exe
2. Install step: msiexec /i "Ambient Agent 1.0.0 x64.msi" /quiet
3. Add step to copy agent-config.json to C:\ProgramData\Ambient\
4. Deploy to target computers

macOS Deployment

Jamf Pro

1. Computers → Packages → New → Upload Ambient Agent-1.0.0.pkg
2. Create Policy → Add package → Trigger (e.g. Enrollment Complete)
3. Pre-install or post-install script to write agent-config.json to /Library/Application Support/Ambient/
4. Scope to computer groups

Munki

1. Add PKG to Munki repo: manifestutil --add-pkg Ambient Agent-1.0.0.pkg
2. Add to managed_installs in manifest
3. Use postinstall script in pkginfo to deploy config

Linux Deployment

Ansible

- name: Deploy Ambient Agent config
  copy:
    src: agent-config.json
    dest: /etc/ambient/agent-config.json

- name: Install Ambient Agent (deb)
  apt:
    deb: "{{ agent_deb_path }}"
    state: present

Verification

After deployment:

1. Check agent appears in your workspace → Endpoints
2. Verify device shows as “Online” and enrolled
3. Test wallpaper/signature sync

Troubleshooting

• Agent not enrolling: Ensure enrollmentCode and serverUrl are correct in config
• Config not found: Verify config path and permissions (agent needs read access)
• Silent install fails: Check MSI/NSIS logs; ensure admin rights

---

For full enterprise deployment details, see the Enterprise Client Deployment Guide. For support: enterprise@ziviso.africa