Home > Declarative Device Management, Jamf Pro, Jamf Pro API, Mobile Device Management > Forcing a DDM sync on a Jamf Pro-managed device via the Jamf Pro API
As part of Jamf Pro 10.48.0, Jamf changed the behavior of the Send Blank Push MDM command to send a DeclarativeManagementRequest MDM command (aka DeclarativeManagement) in place of the previous blank push MDM command, which was a blank push notification via APNS to the device to prompt the device to check in the Apple Push Notification Service (APNS). Changing the behavior to now send a DeclarativeManagement MDM command allows a DDM status report to be sent to the MDM server along with the APNS check-in.
However, I’ve observed that sending a blank push command does not always cause a DeclarativeManagement command to be queued up for Jamf Pro-managed devices if a previous DeclarativeManagement command was recently sent. If you want to make sure a DeclarativeManagement MDM command is being sent to your Jamf Pro-managed device, the declarative-device-management endpoint for the Jamf Pro API can be used to force a DDM status report to be sent to your Jamf Pro server. For more details, please see below the jump.
The declarative-device-management endpoint uses what’s referred to as the client management ID to identify the managed device in question. The client management ID is included as part of the computer inventory record. If you have the Jamf Pro ID of the Mac in question, you can get the client management ID using the following API command:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
That should produce output which looks similar to this, where the output is the client management ID:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Once you have the client management ID, you should be able to use it to force a DDM sync and cause a DeclarativeManagement MDM command to be sent to your managed device:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Once sent, the DeclarativeManagement MDM command should appear in the device’s inventory record as part of the management history.
Once the device has sent in an updated DDM status report, you can also use the Jamf Pro API to query the status report’s information. For more information about doing that, please see the link shown below for a previous post on this topic: