08-13-2024 08:44 AM - edited 08-13-2024 08:54 AM
We have been using Nudge as a means to prod users to update for a few years and it has been flawless until recently. In test machines Nudge is no longer running despite having the launch agent installed being included in our managed login item profile. Manually installing the Nudge suite causes the service to run, but it doesn't pick up its settings in our Nudge config profile (minimum OS and whatnot).
Granted we created our Nudge config profile back with version 1.x. Comparing the json for 1.x to 2.x looks identical, so I don't think that is our issue.
Has anyone experienced something like this?
Solved! Go to Solution.
Posted on 08-13-2024 11:39 AM
Did you install the Nudge suite? If so, that includes the logging function, so you can take a look at the logs at /var/log/Nudge.log. That will confirm whether Nudge is launching or not.
You can also run this command to confirm the configuration Nudge is using:
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -print-profile-config
That will output the current configuration. Make sure it reflects what you are expecting.
Posted on 08-13-2024 11:39 AM
Did you install the Nudge suite? If so, that includes the logging function, so you can take a look at the logs at /var/log/Nudge.log. That will confirm whether Nudge is launching or not.
You can also run this command to confirm the configuration Nudge is using:
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -print-profile-config
That will output the current configuration. Make sure it reflects what you are expecting.
Posted on 08-16-2024 09:22 AM
For some reason it was using an outdated config. Thank you!