I need to un-enroll about 50 Macs from one of my Jamf Pro servers. I could scope a policy to run on every system I want to un-enroll, but then I have no feedback that the policy actually ran since the components that are being removed are the ones that would report back to the Jamf Pro server that the policy completed. I'm curious how other Jamf admins have done this. I can't lay my hands on any of these systems, so I can't manually un-enroll them, and I don't like giving end users the command to remove the Jamf components from their systems.
Once you run the script to remove the jamf client and all the associated binaries/frameworks, then it's no longer managed and reporting back to Jamf. So, what exactly is the problem or concern? You can read a discussion about it here https://www.jamf.com/jamf-nation/discussions/36661/jamf-pro-how-to-unenroll-device-remotely-via-script
and look at Chris_Hafner's response.