Yeah, latest macOS 14.
After the Command the Login-Screen changed to Jamf Connect, but the Microsoft Azure Login is being black.
Im getting following error: Error: JamfConnectLogin.JCAuthProviderFactory.FactoryError-Error 0.
Do i need to reconfigure some Config-Files?
We're using Jamf Connect and have run into this issue as well. We have several users who upgraded to 14 (our policy to block the installer no longer does anything) and they can't get to the login screen as it's completely black.
Anyone know the fix?
I'm running Jamf Connect v2.28 in production on machines with either Monterey or Ventura. I am testing macOS upgrades to Sonoma via Self Service.
As we are all seeing, once the upgrade has completed, the Sonoma login screen takes over from the Jamf Connect login screen. Jamf Connect seems to need a "nudge" to get back to the login screen. I found two ways...
1. By accident and after reading the first part of this thread, I pushed Jamf Connect up to v2.28. Pushing the latest version of the app was enough of a nudge for Jamf Connect retake the login screen. However, this is not practical in production as a method to reset the login screen.
2. Thanks to @dvasquez for including the bit of script for resetting the login screen back to Jamf Connect. I am incorporating that at the end of my upgrade to Sonoma. I'll trigger it for computers on OS version 14.0 and later. That way, each computer that upgrades to 14 and checks in will get its login screen reset.
For those just finding this thread or still working through this issue, I have now experimented with the process of resetting the login screen back to Jamf Connect after an upgrade to Sonoma. Here is what I have found and what I have set up that is working in my production environment.
A. It is true that upgrading from an earlier version of Jamf Connect to a higher version (2.27 or 2.28) will "nudge" Jamf Connect to reset the login screen, but this only works if ALL machines in your production environment are already on Sonoma. A machine that is already running Jamf Connect v2.28 that then upgrades to Sonoma will not get a "reset" from a Jamf Connect upgrade, because it can't upgrade past the highest version of Jamf Connect. Thus, the piece of script that has been mentioned a few times above must be used:
/usr/local/bin/authchanger -reset -jamfconnect
B. The script must be kicked off AFTER Sonoma upgrades. Two ways that MIGHT done:
Production Setup (start to finish):
1. Policy that fetches the Install macOS Sonoma.app package. Scoped to computers not yet on Sonoma that are compatible with the new OS.
2. Policy that runs the Install macOS Sonoma.app package (the typical script that kicks off the Sonoma Installer (/Applications/Install\ macOS\ Sonoma.app/Contents/Resources/startosinstall --nointeraction --agreetolicense --forcequitapps). Scoped to computers that have the Install macOS Sonoma.app package in their Applications folder. Triggered by the user from Self Service.
3. Smart Group into which Jamf Connect + Sonoma computers fall -- as soon as they reboot from the upgrade and check in.
4. Policy with a Script payload to reset the login screen back to Jamf Connect -- scoped to the new Smart Group -- triggers at Startup, Login, and Recurring Check-in (lots of trigger options so the policy runs ASAP) -- runs once per computer. We have found this is actually triggering at Login. Thus, the end user gets the Sonoma login screen once, logs in from that Sonoma login screen, and sees the Jamf Connect login screen after they log out.
I hope helps those who are trying to solve this issue on their own.