03. Configuration Methods
Carefully review Nudge Preferences and determine if deploying either a Configuration Profile (Option No. 2) or local JSON (Option No. 3, the remainder of this article) will best meet your needs.
| Option | Nudge.app | LaunchAgent | Preference |
|---|---|---|---|
| 1 |
 Nudge-1.1.9.x.pkg |
  Local Testing |
|
| 2 |
Nudge_Suite-1.1.9.x.pkg |
Included inNudge_Suite-1.1.9.x.pkg |
  Jamf Pro JSON Schema |
| 3 |
Nudge-1.1.9.x.pkg |
 Nudge Post-install script |
 Nudge Post-install script |
Option No. 1 is when you are first testing Nudge; see: Local JSON, Proof-of-concept.
When you're satisfied with your Nudge configuration on your local test Mac, it's time to deploy to your testing group.
Every release of Nudge includes a LaunchAgent package, which we see in Option No. 2. This LaunchAgent will open Nudge every 30 minutes — on the hour and half-past the hour. You will still need to deploy the Nudge app itself, and with this option, a Jamf Pro JSON Schema to deploy a Configuration Profile for Nudge's settings.
- If you deploy a standard Configuration Profile, it must be signed or it will be modified by Jamf Pro. (See: Creating a Signing Certificate Using Jamf Pro's Built-in CA to Use for Signing Configuration Profiles and Packages.)
Option No. 3 leverages the Nudge Post-install script deployed via the Jamf Pro Script Payload to create:
- LaunchAgent: Opens Nudge
- LaunchDaemon: Redirect Logs
- Local JSON: Configures Nudge
- Hides Nudge: Finder & Launchpad
- Reset function: Policy Script Parameter
Note: All support for this workflow should be asked in the MacAdmin's Slack #nudge-post-install channel or by opening an issue.
The remainder of this wiki focuses on Option No. 3.