Jamf Connect 3.0.0 Now Available

[PCalomeni]

Today we released Jamf Connect 3.0.0. This release includes the following changes and improvements:

• Upcoming Changes to Jamf Connect
  Jamf Connect 3.0.0 continues to include the following login window capabilities and direct support for Jamf Connect Configuration:
  -Desktop multifactor authentication
  -macOS account provisioning
  
  
• Deprecation of Jamf Connect Menu Bar App Capabilities
  The Jamf Connect menu bar app is now deprecated and will no longer receive updates. All menu bar app capabilities from Jamf Connect 2.45 and earlier will be unaffected by this deprecation. Future updates to the Jamf Connect menu bar app will be limited to macOS compatibility and security updates.
  
  Note: For customers deploying Jamf Connect with Jamf School, Jamf recommends to continue using version 2.45.1 instead of updating to version 3.0.0. This will preserve the existing menu bar capabilities for Jamf Connect and not affect existing deployments.
  
  No immediate action or migration efforts are necessary; however, Jamf recommends migrating to Self Service+ 2.0.0 or later which includes the same account management capabilities and a comparable user experience to the Jamf Connect menu bar app:
  -Password syncing
  -Privilege elevation
  -Compatibility with existing Jamf Connect configuration profiles and payload settings written to the com.jamf.connect domain.
  
  Jamf recommends reviewing all existing deployment update settings for Jamf Connect in Jamf Pro to prevent unnecessary or unwanted updates moving forward. For example, you can disable Jamf Connect automatic updates if you do not plan to use any login window capabilities. Automatic update settings for Self Service+ will become available with a future release of Jamf Pro. Additionally, license profiles remain compatible and required with both account management capabilities in Jamf Connect and Self Service+.
  
  All future updates and bug fixes for macOS account management capabilities will only be available through Self Service+. For additional information about macOS account management capabilities with Self Service+ and current known issues, see the Self Service+ for macOS Release Notes.
  
  Note: The product subscription for the Jamf Connect login window, menu bar app, and configuration features all remain unaffected by this change.
  
  
• Adjusting the Jamf Connect Login Window Size
  The Login Window Size (LoginWindowSize) setting allows administrators to modify the resolution of the webview that appears in the Jamf Connect login window. The default webview is set to Wide with a resolution of 620x720px.

To access new versions of Jamf Connect, log in to Jamf Account with your Jamf ID. The latest version is located in the Solutions section under Jamf Connect.

Product Documentation

For additional information on what's included in this release, review the release notes via the Jamf Learning Hub.

[S885]

Replacing existing functionality with an unpolished new version is not a good look.
One of the first things mentioned in the Self Service+ link in this article is that "Self Service+ is still early in development." Should it really be pushed so heavily at this stage?

There are no automatic updates, no way to replace the old Self Service, and no documented options for customization. (Also, why aren’t categories showing in the left-hand menu?)

[Bretterson]

I agree with @S885. It's strange to move functionality to an app that's basically in beta; it can't even replace "Classic" Self Service and will likely just confuse users. I understand it isn't being removed from Connect yet, but you're saying it's dead and trying to push people to software that really isn't ready for production environments and doesn't have a clear roadmap on when SS+ might begin replacing SS (at least not one visible to the public).

[PCalomeni]

@S885 Thanks for your post. For clarity, we have updated the statement to "Self Service+ is in continuous development."

[Jordy-Thery]

I agree with @S885. This shouldn't have been pushed this way, especially not since Self Service hasn't been replaced by Self Service+ yet. 

We have many customers whom utilize Jamf Connect and have it set to auto-update. We have had numerous calls about this change. 🥲 Asking them to use an old version OR start using Self Service+ with the caveats that come with it is not a good look.

[mikevandelinder]

@Jordy-Thery with both Self Service+ 2.0 and Connect login 3.0 being major version changes, there aren't any methods in Jamf Pro that would have auto-deployed this change. This is all staged to give customers the opportunity to update on their own timeline.

[Jordy-Thery]

Not so difficult @mikevandelinder, Jamf App Installers or Installomator for example. :-)

[Bretterson]

@PCalomeni Can you clarify how that clarifies things? All software is in continuous development until it's no longer being updated at all.

[PCalomeni]

@Bretterson Self Service+ is no longer in "early development"; that's what we attempted to clarify with the update to "continuous". Thanks

[kfalato]

It does seem very odd to make this change when Self Service+ isn't native to Jamf Pro yet and most likely hasn't been deployed by many yet due to this. Even if it is deployed, not being able to remove Self Service makes it extra confusion when you have to explain to users that there are two versions whent they go looking for it.

[kfalato]

Also it seems that if you already have Self Service+ installed, Jamf Connect automatically updated to 3.0.  The only devices in our enviroment with 3.0 are those with SS+ installed.  The Patch Policy for Connect is for 24.5.1. Also, the Patch Policy for Connect shows the latest version is 3.2.0 and shows Unknown versions for anything on 3.0.  I'll be opening a support case for this now, but just a heads up.

[mleach]

OK...I am sorry for the strange questions, but in prior releases of Jamf Connect, you had three pkg files included

• JamfConnect
• JamfConnectLaunchAgent
• JamfConnectUninstaller

In this latest release, it looks like JamfConnect has been replaced with JamfConnectLogin.  Is that statement correct?