Skip to main content
Question

Blackscreen since Jamf Connect

  • April 9, 2026
  • 4 replies
  • 124 views

BenSystems

We are currently in the process of implementing Jamf Pro in our company environment. So far, we have successfully integrated several scripts, SMB shares, and other configurations, and everything was running smoothly.

As the next step, we attempted to set up Jamf Connect in order to integrate a SAML authentication flow via our Entra environment. The goal was to allow users to log in with their Entra credentials during a fresh macOS installation.

However, after configuring Jamf Connect, we started encountering a critical issue. The Microsoft 365 login window appears as expected, but after a few seconds, the entire Mac screen goes black and becomes completely unresponsive. The only way to recover from this state is by manually restarting the device.

Additionally, since this issue started occurring, our previously working scripts and configurations are no longer functioning as expected.

Has anyone experienced a similar issue or has any suggestions on how to troubleshoot or resolve this problem? Any help would be greatly appreciated.

4 replies

MaChristosh
Forum|alt.badge.img+3
  • New Contributor
  • April 9, 2026

Maybe try Jamf Connect 3.5. We have found that to be more stable.


Forum|alt.badge.img
  • New Contributor
  • April 24, 2026

We are currently in the process of implementing Jamf Pro in our company environment. So far, we have successfully integrated several scripts, SMB shares, and other configurations, and everything was running smoothly.

As the next step, we attempted to set up Jamf Connect in order to integrate a SAML authentication flow via our Entra environment. The goal was to allow users to log in with their Entra credentials during a fresh macOS installation.

However, after configuring Jamf Connect, we started encountering a critical issue. The Microsoft 365 login window appears as expected, but after a few seconds, the entire Mac screen goes black and becomes completely unresponsive. The only way to recover from this state is by manually restarting the device.

Additionally, since this issue started occurring, our previously working scripts and configurations are no longer functioning as expected.

Has anyone experienced a similar issue or has any suggestions on how to troubleshoot or resolve this problem? Any help would be greatly appreciated.

Such like issue we face 2.29 Jamf connect

 


Forum|alt.badge.img+5
  • New Contributor
  • April 26, 2026

What version of Jamf Connect are you deploying? 
 


Forum|alt.badge.img+8
  • Valued Contributor
  • April 28, 2026

I have the same happening with Okta. You can dump logs by running the following. You can dump to a log file or run it through Jamf and view the data there.

 

log show --style compact --predicate 'subsystem == "com.jamf.connect.login"' --debug