Jamf Connect Updates and the Version of Preference Domain

[healthcareaa]

Hello,

Most users currently running Jamf Connect app 2.19. I myself have been running the 2.22 app version for a month or so now (just updated to 2.23 today. 

Our Jamf Connect Login and Jamf Connect Menu Bar configuration profiles are set for the 2.19 version of preference domain. I am wondering if I should change the preference domain version AFTER I deploy the latest version, or BEFORE I deploy the latest version. Does the timing matter? My computer has been running fine using the 2.19 preference domain while being on the 2.22 and 2.23 Jamf Connect app versions. 

We do not have Auto Updates setup for Jamf Connect as I would like to manage update manually and controllably. 

[mikevandelinder]

@healthcareaa there's no need to update your preferences versioning unless there are specific keys that have been added or changed in that schema you need to take advantage of. Existing deployed configurations for previous versions of Connect continue to work as the apps update. If you do want to make changes to those managed settings, know that Connect reads in those settings on launch - which typically occurs as part of the install process. In that case, I would push the new configurations before applying the updates.

[Tribruin]

One trick. If the new keys don't conflict with your existing keys you can create a whole new profile with the new keys and just push that as a companion to the existing profile. 

However, and this bit me, A lot of the preference keys are part of a larger dictionary. For example, Jamf recently added the PasswordSyncBlockList key to not prompt specific users to log in to Jamf Connect. However, it is part of the PasswordPolicies dictionary and I already had other keys in that same dictionary in my original config profile. You can not have the same top level preference key in two different profiles. macOS will only recognize one of the settings for that key.