My fix to "Configurator Mode" enabled by default in v3.x

[amirghaliusa]

In my environment, the Root3 Support app is deployed via the Jamf Pro App Catalog, which automatically updates client installations when a new version is released. As with version 3, the application introduces a new configuration structure and enables Configurator Mode by default. Since I intend to maintain the existing custom schema currently in use within Jamf Pro, I decided not to migrate to the new configuration model at this time.

To preserve the current behavior and disable the default Configurator Mode, I determined that the required change was to insert the following code snippet into the existing schema within the Configuration Profile. This will simply allow you to add this new property called "Block Configurator Mode" and set it to "Blocked"

After updating the schema, the Configuration Profile was redeployed to all managed computers to enforce the modification. For the change to take effect, the Root3 Support application must be relaunched on each client device.

"DisableConfiguratorMode": {
      "title": "Block Configurator Mode",
      "description": "Block the user from enabling Configurator Mode",
      "type": "boolean",
      "options": {
        "enum_titles": [
          "Blocked",
          "Allowed"
        ],
        "infoText": "Key name: DisableConfiguratorMode"
      },
      "links": [
        {
          "rel": "Documentation",
          "href": "https://github.com/root3nl/SupportApp/wiki"
        }
      ]
    },