I have an odd issue with Connect. I have a computer that upon initial login created the user profile, but did not open the Notify screen to run the script. However upon further examination of logs, it looks like the notify script started running in the background after the profile was created and the desktop displayed. When the devices are prepped, the last package in DEP has the command to enable Notify. However, this computer did not show the actual Notify screen. It simply created the profile, dumped to the desktop, and ran the script in the background.
To tack onto this issue I'm seeing in the logs of the polices that devices are somehow running them, even though the policies are only set to run via custom trigger. At no time did anyone explicitly run sudo jamf policy -event.
I'm having the same issue with macOS Ventura testing. Everything runs as expected in the background but the actual Notify screen doesn't seem to appear. If anyone else has figured out why I'd love to know.
