I would suggest uploading the Jamf schema and turning on the required keys mentioned in the wiki. Also, is it not launching when you click on it or when you run your launch agent? Let me know if you need screenshots.

Hello bwoods,

The Launch agent do not turn on. It would be much appreciated if you can help me with modifed changed that has to be done in custom Schema with screenshot.

The jamf schema can be found here. You can upload it to your jamf pro server using "External Applications" in the "Application & Custom Settings" payload. (This is a configuration profile payload)

Select "Custom Schema" as the source.

The preference domain will be com.github.macadmins.Nudge

Click "Add schema" and copy/paste the code block from the URL above.

Click "Save" instead of "Upload". 

You'll now have a simple GUI to activate and deactivate features.

According to the wiki, Nudge will not open until the following keys have been configured. ( I suggest only enabling these three keys before doing any thing else.)

After configuring the keys above, you need to deploy the profile to a test machine and manually open nudge without a launch agent to see if it works. If it doesn't, something is wrong. If it does, move on to the launch agent. 

Below I have a script that creates and loads a custom launch agent for me. You can change the Start Interval to whatever you want. Below I have it set to 14400. ( 4 hours)

!/bin/bash

# Determine Current User
currentUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name && ! /loginwindow/ { print $3 }' )

# Determine Current User ID
currentUserUID=`id -u "$currentUser"`

# Generate Nudge launch agent
echo "<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.github.macadmins.Nudge</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StartInterval</key>
<integer>14400</integer>
</dict>
</plist>" > /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

# Load Launch Agent
/bin/launchctl asuser "$currentUserUID" launchctl load /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

exit 0 ## Success
exit 1 ## Failure

Hello Bwoods,

Now I'm manually able to open the Nudge. as the Configuration you mentioned.
But now the launch agent is not opening automatically as you mentioned "custom launch agent". I've changed the start interval to 1600. But no pop-ups.
Note:- I haven't install the Launch Agent pkg yet.

The jamf schema can be found here. You can upload it to your jamf pro server using "External Applications" in the "Application & Custom Settings" payload. (This is a configuration profile payload)

Select "Custom Schema" as the source.

The preference domain will be com.github.macadmins.Nudge

Click "Add schema" and copy/paste the code block from the URL above.

Click "Save" instead of "Upload". 

You'll now have a simple GUI to activate and deactivate features.

According to the wiki, Nudge will not open until the following keys have been configured. ( I suggest only enabling these three keys before doing any thing else.)

After configuring the keys above, you need to deploy the profile to a test machine and manually open nudge without a launch agent to see if it works. If it doesn't, something is wrong. If it does, move on to the launch agent. 

Below I have a script that creates and loads a custom launch agent for me. You can change the Start Interval to whatever you want. Below I have it set to 14400. ( 4 hours)

!/bin/bash

# Determine Current User
currentUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name && ! /loginwindow/ { print $3 }' )

# Determine Current User ID
currentUserUID=`id -u "$currentUser"`

# Generate Nudge launch agent
echo "<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.github.macadmins.Nudge</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StartInterval</key>
<integer>14400</integer>
</dict>
</plist>" > /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

# Load Launch Agent
/bin/launchctl asuser "$currentUserUID" launchctl load /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

exit 0 ## Success
exit 1 ## Failure

Quick edit. The shebang is missing in the launch agent script. My bad. 

#!/bin/bash

# Determine Current User
currentUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name && ! /loginwindow/ { print $3 }' )

# Determine Current User ID
currentUserUID=`id -u "$currentUser"`

# Generate Nudge launch agent
echo "<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.github.macadmins.Nudge</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StartInterval</key>
<integer>14400</integer>
</dict>
</plist>" > /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

# Load Launch Agent
/bin/launchctl asuser "$currentUserUID" launchctl load /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

exit 0 ## Success
exit 1 ## Failure

Hello @bwoods I did follow the steps ^ but nudge is still not opening. Anything I missed?

Are you able to open it manually without the launch agent?

@mforeman1 FYI, it won't open if you're already running the latest version of the OS. It's best to test with a VM or build a usb to go back to an older version.

@bwoods Got it. Looking good now. One last thing how can I redirect the user to the softwareupdate in Mac when they click "update device" in nudge?

That should be the default behavior if you configure the keys I mentioned above. 

hmm that's weird, coz I already did that but seems every time I click on the update device nothing happens

What OS version is the machine running and what did you set as the minimum requirement?

Hello All,

This post is old I know but curious if I could get a little help. I have the Nudge.pkg deploying via JAMF's Mac Apps, I deployed the LaunchAgent via a policy in JAMF. I have the custom schema uploaded into a configuration profile with deferrals set, install date, and minimum OS version. Nudge launches fine as is and it has no problems, it is set to default every 30 minutes without an edited LaunchAgent.

Here is where I am stuck and where the documentation gets a bit confusing to me. All I want is the Launch Agent to launch Nudge every 4 hours such as what @bwoods describes (14400). Can someone please break it down in the simplest terms what is needing to be done here to get the Launch Agent edited? Do I need to somehow edit the plist that is in the PKG and repackage the Launch Agent? Do I need to deploy a custom script that will edit the plist for the Launch Agent, if so, how do I go about deploying that, would it be its own separate policy or deployed with the Launch Agent pkg in JAMF with the script set to take effect after the PKG is installed.

Any help or guidance would be appreciated, I am so close getting this to working how we want I have just been hitting a brick wall with editing of the Launch Agent, whether that means somehow editing the plist or deploying a script I am all ears! If it is a script I could use the one @bwoods gratefully shared but unsure if that is deployed by itself or with the Launch Agent .pkg, if it is do I need to alter filepaths or any kind?

Thank You!

-Paul Fye

Hello All,

This post is old I know but curious if I could get a little help. I have the Nudge.pkg deploying via JAMF's Mac Apps, I deployed the LaunchAgent via a policy in JAMF. I have the custom schema uploaded into a configuration profile with deferrals set, install date, and minimum OS version. Nudge launches fine as is and it has no problems, it is set to default every 30 minutes without an edited LaunchAgent.

Here is where I am stuck and where the documentation gets a bit confusing to me. All I want is the Launch Agent to launch Nudge every 4 hours such as what @bwoods describes (14400). Can someone please break it down in the simplest terms what is needing to be done here to get the Launch Agent edited? Do I need to somehow edit the plist that is in the PKG and repackage the Launch Agent? Do I need to deploy a custom script that will edit the plist for the Launch Agent, if so, how do I go about deploying that, would it be its own separate policy or deployed with the Launch Agent pkg in JAMF with the script set to take effect after the PKG is installed.

Any help or guidance would be appreciated, I am so close getting this to working how we want I have just been hitting a brick wall with editing of the Launch Agent, whether that means somehow editing the plist or deploying a script I am all ears! If it is a script I could use the one @bwoods gratefully shared but unsure if that is deployed by itself or with the Launch Agent .pkg, if it is do I need to alter filepaths or any kind?

Thank You!

-Paul Fye

@OvativePaul , You can paste my script into Jamf Pro then add it to a policy. You just want it to run after the Nudge installation. 14400 seconds is equal to 4 hours. You can change when the pop-up appears by simply changing the seconds in the script above. (Use Google for a seconds to hours converter)

Basically, the only thing that you need to edit is the key below. Just edit the seconds whenever you want to change when Nudge launches. My replies below are my updated script. It has more logic built in.

@OvativePaul , You can paste my script into Jamf Pro then add it to a policy. You just want it to run after the Nudge installation. 14400 seconds is equal to 4 hours. You can change when the pop-up appears by simply changing the seconds in the script above. (Use Google for a seconds to hours converter)

Basically, the only thing that you need to edit is the key below. Just edit the seconds whenever you want to change when Nudge launches. My replies below are my updated script. It has more logic built in.

@OvativePaul , You can paste my script into Jamf Pro then add it to a policy. You just want it to run after the Nudge installation. 14400 seconds is equal to 4 hours. You can change when the pop-up appears by simply changing the seconds in the script above. (Use Google for a seconds to hours converter)

Basically, the only thing that you need to edit is the key below. Just edit the seconds whenever you want to change when Nudge launches. My replies below are my updated script. It has more logic built in.

Example of 4 hours

#!/bin/bash

# Determine Current User
currentUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name && ! /loginwindow/ { print $3 }' )

# Determine Current User ID
currentUserUID=`id -u "$currentUser"`

# Verifies Presence of Nudge Launch Agent
if [[ -f /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist ]]; then
echo "Nudge launch agent is present"
/bin/launchctl asuser "$currentUserUID" launchctl unload /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist
rm -Rf /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist
elif [[ ! -f /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist ]]; then
echo "Nudge launch agent is not present."
fi

# Generate Nudge launch agent
echo "<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Label</key>
<string>com.github.macadmins.Nudge</string>
<key>ProgramArguments</key>
<array>
<string>/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge</string>
</array>
<key>RunAtLoad</key>
<true/>
<key>StartInterval</key>
<integer>14400</integer>
</dict>
</plist>" > /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

# Load Launch Agent
/bin/launchctl asuser "$currentUserUID" launchctl load /Users/$currentUser/Library/LaunchAgents/com.github.macadmins.Nudge.plist

exit 0 ## Success
exit 1 ## Failure

Hi @bwoods ,
The result of your script shows me this error, any idea ?