DEPNotify App Not Found in /Applications/Utilities

bootrec
Contributor

Hello... I was just made aware of DEPNotify this week and have spent the last couple of days trying to implement it. I read and followed information from https://hcsonline.com/images/Signed_DEPNotify.pdf, and https://gitlab.com/Mactroll/DEPNotify and I'm using the script from https://github.com/jamf/DEPNotify-Starter.

I have my policy set to install depnotify-with-installers.pkg and run script depNotify.sh after enrolment. It doesn't load up after enrolment. I can see the DEPNotify.pkg in /usr/local/depnotify-with-installers/DEPNotify.pkg, but there is nothing in /Application/Utilities.

I'm obviously missing a crucial step, could anyone point me in the right direction please?

3 REPLIES 3

bootrec
Contributor

Executing Policy _01 - DEPNotify - Start
Downloading depnotify-with-installers.pkg...
Downloading https://use1-jcds.services.jamfcloud.com//download/2d03ef776bda4ef1be69aa0194118b3e/depnotify-with-installers.pkg?token=ce96e70d9aba4f2ea3f7223712e7f9638bszay33zsv1k4aebdxrqhko6esjjsyj...
Verifying package integrity...
Installing depnotify-with-installers.pkg...
Installation failed. The installer reported: installer: Package name is depnotify-with-installers
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “depnotify-with-installers.pkg”.)
Running script depNotify.sh...
Script exit code: 0
Script result: /Library/Application Support/JAMF/tmp/depNotify.sh: line 565: kill: `': not a pid or valid job spec
FSPathMakeRef(/Applications/Utilities/DEPNotify.app) failed with error -43.

alexjdale
Valued Contributor III

It looks like the pkg installation is simply failing, but I can't say why. Can you install the pkg manually?

bootrec
Contributor

Thanks @alexjdale I ended up re-downloading the depnotify.pkg from github, uploading again to Jamf and changing my policy to use this new one instead of the depnotify-with-installers.pkg I had created and it works now.