Transition Profiles from MDM (Mobile Device Management) to DDM (Declarative Device Management) not applied on 17 beta devices

Question

MDM iOS Dev OP

Created Sep ’23

Replies 0

Boosts 0

Participants 1

Hi Apple Community,

Problem Description:

Regarding the transition from MDM (Mobile Device Management) profiles to DDM (Declarative Device Management) profiles, as announced during WWDC 2023, this marks a significant step forward in simplifying our device management process.

When we attempted to test this transition with the 17 developer beta OS version devices, we encountered a notable challenge. Specifically, when trying to apply a DDM Webclip legacy profile configuration to a device that already had the same profile applied through MDM. We received the following status response from DDM: "The profile “<profile_identifier>” cannot replace an existing profile." As a result, the configuration was not applied.

However, after removing the existing applied MDM profile and then reapplying the same profile as a legacy profile via DDM, the configuration was successfully applied.

My DDM Configuration:

{
  "Type": "com.apple.configuration.legacy",
  "Identifier": "DEFAULT_APP_CATALOG_CLIP_CONFIG",
  "ServerToken": "3",
  "Payload": {
    "ProfileURL": "https://mdmtest:8080/certificates/appConfig.mobileconfig"
  }
}

My DDM Status Response :

{
  "StatusItems" : {
    "management" : {
      "declarations" : {
        "activations" : [
          {
            "active" : true,
            "identifier" : "DEFAULT_ACT_0",
            "valid" : "valid",
            "server-token" : "1"
          },
          {
            "active" : false,
            "identifier" : "DEFAULT_APP_CATALOG_CLIP_ACT",
            "valid" : "valid",
            "server-token" : "3"
          }
        ],
        "configurations" : [
          {
            "reasons" : [
              {
                "details" : {
                  "Error" : "The profile “<profile_identifier>” cannot replace an existing profile."
                },
                "description" : "Configuration cannot be applied",
                "code" : "Error.ConfigurationCannotBeApplied"
              },
              {
                "details" : {
                  "Identifier" : "DEFAULT_APP_CATALOG_CLIP_ACT",
                  "ServerToken" : "3"
                },
                "description" : "Activation “DEFAULT_APP_CATALOG_CLIP_ACT:3” has errors.",
                "code" : "Error.ActivationFailed"
              }
            ],
            "active" : false,
            "identifier" : "DEFAULT_APP_CATALOG_CLIP_CONFIG",
            "valid" : "invalid",
            "server-token" : "3"
          },
          {
            "active" : true,
            "identifier" : "DEFAULT_STATUS_CONFIG_0",
            "valid" : "valid",
            "server-token" : "2"
          }
        ],
        "assets" : [

        ],
        "management" : [

        ]
      }
    }
  },
  "Errors" : [

  ]
}

Kindly help us with this issue.

Note : We have posted a feedback in Feedback Assistant portal FB13132059 - along with device sysdiagnose.

Boost