Hi everyone,
I'm working on upgrading our Mac fleet from Jamf Connect 2.39 to 3.7.1 and running into some cleanup issues I'd love some guidance on.
Environment:
- Jamf Pro 11.26.1
- macOS 15 Sequoia
- Apple Silicon and Intel endpoints
- Devices enrolled via Apple Business Manager (ABM) using Automated Device Enrollment (ADE)
- Identity Provider: Azure AD / Entra ID
Current situation: All of our managed Macs have Jamf Connect 2.39 installed. I have already built and validated a Jamf Connect 3.7.1 configuration profile in Jamf Pro and scoped it to a handful of test machines successfully.
The problem: When pushing JamfConnectLogin.pkg (3.7.1) via policy, it does not remove or replace the existing 2.39 installation. After the policy runs I can confirm:
Jamf Connect.app(2.39) remains in/Applications- The 2.39 menu bar app is still present and running
JamfConnectLogin.bundledoes get updated to 3.7.1 via the pkg
I also want to note that sudo is restricted on our endpoints via BeyondTrust Privilege Management, so any removal solution needs to run in the context of a Jamf policy (which runs as root) rather than interactively.
What I have tried:
- Pushing
JamfConnectLogin.pkgvia policy — updates the login plugin but does not cleanly remove anything.
What I am looking for:
- A reliable method or script to cleanly remove Jamf Connect 2.39 (app bundle, LaunchDaemons, LaunchAgents, login plugin) before installing 3.7.1
- Confirmation of whether anyone has successfully done an in-place upgrade from 2.x to 3.x or whether a full removal first is the recommended approach
- Any gotchas moving from 2.x to 3.x beyond the config profile key changes
Thanks in advance!