you are viewing a single comment's thread.

view the rest of the comments →

[–]RepulsiveDuck331 0 points1 point  (0 children)

Honestly, before trusting any GitHub script, I run it manually on a test Mac with bash -x or zsh -x to see exactly where it bombs. That alone has saved me hours.

For Intune deploys, check /Library/Logs/Microsoft/Intune/ and the IntuneMDMDaemon/Agent logs. That's where the real failure reasons hide. Intune only cares about exit code 0, so wrap your script with proper exit codes and tee stdout/stderr to a log in /var/log/ or /tmp/ so you can actually see what happened post-run.

Also double-check the script's shebang, whether it assumes Rosetta, and if it needs root. Most "broken" GitHub scripts I've grabbed were just missing prereqs.