Hello @Tonydig11 

I have been using DEPNotify with 12.3.1 and 12.4 (Beta) with no issues. Are you using the DEPNotify Starter Script for your deployments? https://github.com/jamf/DEPNotify-Starter 

I was at this link a few this morning. Noticed that I was on version 2.0.5 of the script. So I updated my script to the new 2.0.7 script and modified it for my deployment and it is still not launching during the build.

Hello @Tonydig11 

Is DEPNotify installed already on the machine before the script is run? We are deploying the DEPNotify package through prestage enrollment packages and having the script run after enrollment. We had to notarize the DEPNotify pkg in order for it to work correctly.  Also check the Jamf logs and see if the script is actually running during your deployment ( /var/log/Jamf.log) 

Yes. I deploy DEPNotify in prestage enrollment. Just tested and it still works with 12.2.1. Not working with 12.3.1

the log shows that the DEPNotify policy that holds the script has started.

With help from a Slack channel I have my DEPNotify back up and running. I had my DEPNotify package in pre stage enrollment. I was asked to try to create a policy then add the DEPNotify package in there and have it run on "enrollment complete". I did this and removed the package from pre stage. I also added a custom trigger to point to the policy that has the script.

It is definitely the case that you need to lift the script to version 2.0.7 - triggered by the fact that in the previous versions Python code was still used, which now no longer works because with 12.3.1 Python was removed.

Find the script in v2.0.7 and adapt it to your script - I think there are only 20-30 lines of code that have been changed.

Everything else can be left as it is, it's definitely the script!

@Tonydig11 what other installers do you have in the DepNotifywithinstallers.pkg file?