Jamf Connect changes

Updates to Jamf Connect

With the release of the Jamf Self Service plus, some of the functionality of Jamf Connect has moved. The main application used in the past was called “Jamf Connect” and could be found installed on machines like any other application. That package consisted of two parts. The Jamf Connect menu bar app, and the Jamf Connect Login window plugin. Self Service plus has taken over all the functionality of the main “Connect” app. The “login” plugin is still needed for a seamless deployment.

In the past we have been updating Jamf Connect using the built in App installers within Jamf Pro. Since the Connect application was a true app that we could query in a traditional smart group, we used that as the target for patching.

Going forward we will be utilizing a new Extension attribute labeled “Jamf Connect Login version”. This EA will be found in the “operating system” tab within a device inventory record.

The “Jamf Connect” application will still be installed on machines that already have it. It will not be updated beyond version 2.45.1. There will be an effort to remove this application at a later time.

Additional notes:

There was an issue causing Jamf Connect Login, and Self Service plus to conflict and prompt for keychain access. This issue has been addressed in macOS version 26.4, and Connect login version 3.6

If you are deploying Jamf Connect to users directly (no IT intervention prior to deployment) you may need to add the Self Service plus package into your pre-stage. If the Jamf Connect Login triggers before Self Service plus is present on the device the prompt for keychain access may still occur. For units who’s IT staff interact with the device before deployment, there will be enough time for both to install.