Jamf Connect Deployment and Update integration

[PPAict]

Good morning, simple question about Jamf Connect Deploy & Updates integration in Jamf Pro.

Currently my configuration is: deploying Jamf Connect not in the prestage via .pkg (only launch agent) but via the integrated functionality of Jamf Connect combined with the Jamf Connect Login Configuration Profile, as shown in the screenshot. It works.

Two questions.

1) In your experience is it a stable configuration? Up to now it has never given me problems, but I would like to update to 2.44 (I'm stuck on 2.39) and since the profile is in scope on All Managed Clients I'm wondering if it's stable and the best option.

2) If I remove this integration in the configuration profile, nothing would happen to existing clients, right?
That way I could simply deploy the update via policy and reinsert the Connect .pkg in the Prestage, just to have more control.

What do you suggest?

If the integration works well in your experience i could simply choose the new version and keep this configuration :)
Thanks.

[Matthew_T]

2.44 is stable. When first set up I was pushing from a config profile but ended up switching to just using the Mac app option. It keeps it updated automatically and have not had any issues at all. 

[PPAict]

Thank you for the reply Metthew.
Can I ask you why you preferred Mac Apps to deploy Connect instead of via Configuration Profile?
Any issue with the conf profile deploy system?
I want to know if it's ok to use this feature (that i actually run, but never change the manual version) to update Jamf Connect and also if it's safe to disable this function to switch to Mac Apps / Installomator Policy.
That's because if it's ok i can stick with this configuration, otherwise i just want to be sure that i can simply turn off the option.

[Matthew_T]

That would be up to you and your needs. If 2.39 does everything you need it to do then you don't ever have to update from that. If a new version releases with features you need you can update the profile to that version with no issues as well.

As far as the Mac App option, no real reason we do it that way besides not having to worry about updating. Just checked and we've been doing it this way since 2.39, again with no issue thus far. 

[PPAict]

Yes i was just try to understand if the conf profile feature is stable for updating, because i tried it when i got only 5-8 devices, now they are more then 200 and don't want to mess up because i have no control with that feature :) Also want to be sure that i can simply turn off the conf profile feature to switch to another one without any consequences.

I was ok with 2.39 but 2.44 get a fix that we issued to Jamf (passwords with special character issues with with google as IDP) so now it's time to update :)

[Matthew_T · Accepted solution]

No you don't have to do all that. You just go to Settings > Jamf Applications > Jamf Connect, hit Edit next to the configuration profile and update that profile to 2.44. Will update the scoped Macs without issue. 

[Matthew_T]

Here, check this out- Updating Connect https://learn.jamf.com/en-US/bundle/jamf-connect-documentation-current/page/Jamf_Connect_Updates.htm...

[PPAict]

I know how to do it, my concern was different.

Probably i can't explain properly.

Don't worry, thank you m8!