Description
With the release of Jamf Connect 3.x, the Jamf Connect installer is for the login window only and the menu bar functionality (password syncing, privilege elevation, kerberos, etc.) is now integrated with Self Service+.
⚠️ Installing Self Service+ 2.x will automatically uninstall Jamf Connect menu bar.
When Self Service+ is deployed with Jamf School, it will only include:
the Account management dashboard items (Jamf Connect menu bar)
Security dashboard items (if Jamf Protect is installed on computers)
The app deployment self service features are not supported with Jamf School deployment. Jamf School Student continues to be the end user app of choice for on demand app installation.
This article is for organizations currently using Jamf Connect 2.45.1 or earlier with Jamf School, which was not integrated with Self Service+.
More Resources: The process for deploying Jamf Connect and Self Service+ to devices at time of provisioning is cover in the article 🔗 Deploying Jamf Connect & Self Service+ with Jamf School.
Requirements for this Workflow
Download the Jamf Connect DMG from Jamf Account and mount the DMG to extract the Jamf Connect Login (3.x) file.
Download the Self Service+ package file from Jamf Account.
Testing Prior to Deployment with Jamf School
It's important to test that the new version of Jamf Connect Login and Self Service+ work as expected with your current Jamf Connect configurations. Do the following as preliminary testing:
Select a device with the current Jamf Connect configurations and application installed or setup a new device with your organization's existing Jamf Connect setup for the explicit purpose of testing.
Login to the device as an admin and install the package for Self Service+ locally on the machine.
For upgrades it is important that Self Service+ is installed before the the Jamf Connect Login package is executed.
Once Self Service+ has finished installing, install the Jamf Connect login package locally on the computer.
Restart the device and spend some time validating that any of your custom configurations continue to work as expected.
Deploying the Upgrade with Jamf School
Once you've confirmed that Jamf Connect is functioning as expected based on your configuration, use these steps to deploy the upgrade to your existing devices.
Upload the Jamf Connect and Self Service+ packages to Jamf School. For assistance, see Adding In-House Apps and Packages.
Do not replace your existing Jamf Connect package with the new Jamf Connect Login package. It should be uploaded as a distinct application.
To ensure devices only install the new login package after Self Service+ installs, create a new Smart Device Group for deploying the new Jamf Connect Login.
The steps for creating a Smart Device Group can be found in the Jamf School Documentation. Use the
Managed App (Installed)smart group criteria and select the Self Service+ app.NOTE: Do not add this group to the scope of Jamf Connect Login yet.
Scope the newly added Self Service+ app to your devices running Jamf Connect.
It is recommended that you scope Self Service+ to devices using the same group that you use to scope your Jamf Connect configuration profiles. This ensures only devices that are configured for Jamf Connect are going to receive the applications related to Jamf Connect.
Scope the newly created Jamf Connect Login app to the Smart Group that was built in Step 2.
Un-scope the old Jamf Connect application from devices.
How It Works
Next time a device with Jamf Connect checks in with Jamf School it will see that it needs to install Self Service+ and it will perform that install.
Once that install is complete and reported back to Jamf School the device will automatically fall into scope of the new Smart Group that deploys Jamf Connect Login and it will perform that install.
Since order matters with this upgrade, this process ensures that no device can install the updated version of Jamf Connect Login without first have the dependency of Self Service+ installed and ready.