MDM failure. Inability to Lock or Wipe machine.

To add to my post, or maybe ‘jamf manage’?

You could try the Redeploy Framework API call: /v1/jamf-management-framework/redeploy/{id}

Basically does programmatically what you did manually.

Are they still polling in JAMF?  What’s the status of the devices?  A MDM lock should not cause any binary issues….but without knowing the state of devices, it’s hard to say what should be done.

Were the devices locked or were they unmanaged?  Can you post the management history logs of a device so we can get a better story of what happened?

You have two possible scenario’s of something going wrong:

1. The Jamf binary still communicates (check-in and inventory update work) but the device does not respond to MDM commands. A profiles renew -type enrollment (given the devices are in ABM) would resolve that. You could put this in Self Service.
2. The device responds to MDM commands but the Jamf binary no longer communicates (no check-in / inventory update). A redeploy framework would work (either through API or via this tool). 

As ​@Chubs said, a little more info would help. :) 

I have never witness this in our environment.  the lock and wipe command always works unless there is an issue with communication.