DEPNotify-Starter
DEPNotify-Starter copied to clipboard
DepNotify GUI not running
Describe the bug The DepNotify GUI doesn't start running on enrollment. It will just stay at the "Waiting for DEPNotify to start the process ID" message until I manulaly open that DEPNotify app in the utilities folder
depnotify.log depnotifyDebug.log jamf.log
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Logs Please attach the following logs:
- /var/tmp/depnotify.log
- /var/tmp/depNotifyDebug.log
- /var/log/jamf.log
Software Versions (please complete the following information):
- macOS Version currently running on 10.15 but the same thing happens on 10.14
- Jamf Version 10.14.1
- DEP Notify Version 1.1.5
This same DEPNotify and script has been working about 2 weeks ago and it just stopped. Not sure if someone changed something on the JAMF server or what happened.
After a horrible amount of testing on 10.14 and 10.15
The issue appears to be with lines
Line 695
sudo -u "$CURRENT_USER" open -a "$DEP_NOTIFY_APP" --args -path "$DEP_NOTIFY_LOG" -fullScreen
and
Line 697
sudo -u "$CURRENT_USER" open -a "$DEP_NOTIFY_APP" --args -path "$DEP_NOTIFY_LOG"
It appears to be a combo of open -a
and $DEP_NOTIFY_APP
. If one removes -a
from the open command and add to the end the location of the binary eg $DEP_NOTIFY_APP
/Contents/MacOS/DEPNotify
DEP notify launches correctly.
The modified commands should look like this
Line 695
sudo -u "$CURRENT_USER" open "$DEP_NOTIFY_APP"/Contents/MacOS/DEPNotify --args -path "$DEP_NOTIFY_LOG" -fullScreen
and
Line 697
sudo -u "$CURRENT_USER" open "$DEP_NOTIFY_APP"/Contents/MacOS/DEPNotify --args -path "$DEP_NOTIFY_LOG"
This suggests that something isn't being passed correctly.
Unfortunatly, the open command without the -a
causes terminal to open to run DEPNotify. Not ideal but at least is a work around.
Thanks blake. I don't know when I will be back into our offices to try it again but, I have made the changes to our script in Jamf. I don't think I can do this from home.
Thanks Blake for the information.
@blakeusblade I've added the code you listed but it seems to ignore my fullscreen flag now. I have it set for Fullscreen True but it runs it in windowed mode.
I'm seeing the same issue.
Hardware: iMac Intel (Retina 5K, 27-Inch, 2019) OS: 10.15.7 DEPNotify: 1.1.5 jamf: 10.26.0
Trying to manually run the sudo command that launches DEPNotify yields:
+ sudo -u "$CURRENT_USER" open -a "$DEP_NOTIFY_APP" --args -path "$DEP_NOTIFY_LOG"
LSOpenURLsWithRole() failed for the application /Applications/Utilities/DEPNotify.app with error -54.
Changing to the following works manually:
CURRENT_UID=$(id -u $CURRENT_USER)
sudo launchctl asuser "$CURRENT_UID" open -a "$DEP_NOTIFY_APP" --args -path "$DEP_NOTIFY_LOG"
I still need to test if it works via jamf policy, though.
I still have this issue.
@kylejericson
Its been a while since I worked on it... but I do remember the code might have a flaw in it with the below lines and the last parameter causing the script to reset the parameters...
eg Line 48 FULLSCREEN=true
Line 452 Fullscreen Mode if [ "$5" != "" ]; then FULLSCREEN="$5"; fi
In the example above... Line 48 is hardcoded to true however line 452 is possibly resetting the value... You could try #/commenting out line 452's if statement (adding # in front of the if) and try again...
Regards Blake
I also just have this exact issue this week. But it seems like it sometimes works, but sometimes the GUI doesn't fire up? the debug log just says "Waiting for DEPNotify to start the process ID" over and over.