Hi everyone,
I’m running into an issue trying to upgrade Jamf Connect across our environment and hoping someone from Jamf or the community has seen this before.
Until recently, I was able to update Jamf Connect using the dropdown under
Settings → Jamf Apps → Jamf Connect → Deployment and Update Settings.
That list used to automatically show each new version as Jamf released it (for example, 2.44 → 2.45).
Now the dropdown has stopped updating — it’s capped at 2.45.1, even though 3.4.0 has been released publicly for several weeks.
I’ve tried to manually handle the upgrade:
• Downloaded JamfConnectLogin.pkg (3.4.0) from account.jamf.com.
• Uploaded it into Jamf Pro (Cloud Distribution Point).
• Created a policy to deploy it to test devices and tied it to our existing PreStage.
• Policy runs successfully, reports “completed,” but the actual version on the Mac remains 2.45.1 — both in Get Info and when checking the bundle version via Terminal.
• I’ve confirmed the correct PKG is being used, deleted the old 2.45.1 from the repo, flushed logs, etc.
We’re on Jamf Cloud 11.20.1, and all Jamf Connect auto-deploy settings have been set to “No” to avoid conflict with the outdated catalog version.
At this point, I’m wondering:
1. Has anyone else seen this behavior where Jamf Connect 3.x fails to install/upgrade and reverts to 2.45.1?
2. Is Jamf aware that the Jamf Apps catalog hasn’t been updated beyond 2.45.1 for some tenants?
3. Is there a documented process change for deploying Jamf Connect 3.x manually?
Everything used to work beautifully through the Jamf Apps auto-deploy flow, so this new process feels like a step backward.
Any insight, confirmation, or official Jamf comment would be hugely appreciated.
Thanks in advance,
Cesar D.
Jamf Cloud Tenant v11.20.1
Jamf Connect 3.4.0 not deploying or upgrading — still installs 2.45.1 despite new PKG upload
+3
+12Hey mate,
Looks like auto-update of jamf connect login via Jamf Pro app settings is only supported up to version 2.45.
For versions after that its suggested to use manual policy deployment, or app installers.
hope this helps you
+3Jamf Connect beyond 2.45.1 is tied to Self Service+, as in it is part of the functionality of that. The jamf app catalog only goes to 2.45.1 intentionally because you should not be using jamf connect 3+ if you aren’t using Self Service+ yet. If you are using the login window functionality that is a separate app in jamf app installers, jamf connect login, and is current (3.5 in mine now). I am not official jamf, but that is my understanding.
+26Jamf Connect login and Jamf connect menu bar are two different applications.
The Menu Bar has been replaced by Self Service+ and if you are on Self Service + the menu bar can just be removed.
Updating Jamf Connect 3+ just updates the Login Window app as that is all it is for. There is an App Catalog item for this, but it’s separate from the one that was for Jamf Connect 2 due to lacking the Menu Bar component.
Will updating the Jamf Connect Login to 3.5 remove or break the Connect Menu Bar for 2.45.1 or will that functionality remain?
Will updating the Jamf Connect Login to 3.5 remove or break the Connect Menu Bar for 2.45.1 or will that functionality remain?
Found this thread after running into the same issue as the OP. After installing 3.5.0 via PKG, the 2.43.0 menu bar app seems to be working fine still. Obviously still test for yourself in your environment, but seems like it’ll probably be fine.
I’m having a similar issue…
I have no problem updating existing Macs from 2.45.x to 3.4.0. It works fine by just installing the new Jamf Connect Login and Self Service+ packages together in a policy. However, when I cloned our production prestage enrollment profile (which still installs 2.45.0) and just removed the old Jamf Connect and Launch Agent packages and replaced them with the new Jamf Connect Login, Launch Agent, and Self Service+ packages, these 3 apps do not install during enrollment. What am I doing wrong?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.