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