You can also use a curl command with POST to redeploy the Jamf management framework. (This will honor re-enrollment settings as defined by the Jamf Pro re-enrollment settings on the server.) You can see it in the URL of the computer record or in the attribute Jamf Pro Computer ID on a computer record in Jamf Pro.Īs long as the computer is online you should see the command run and the computer will go through re-enrollment once the QuickAdd installs. Find the Jamf Pro Computer ID of the computer in this state.If so you can use the new jamf-management-framework API endpoint to reinstall the Jamf management framework (QuickAdd package) automatically and re-establish management with the Jamf Pro server.Ī quick look at how you can use this new feature in Jamf Pro 10.36: You can usually tell this is the case if you check the Management History on a computer record and see commands running successfully. Jamf Pro accomplishes this by using the InstallEnterpriseApplication command, which means a computer in this state would still need to be receiving and processing MDM commands from your Jamf Pro server. Have you ever had an instance where a computer has lost device trust and when you attempt to run any policies or a recon you get at Device Signature Error? Or someone sends in a ticket that Self Service isn't working and can't connect to the MDM server (due to Device Signature Error)? On 10.36 you now have a way to redeploy the Jamf management framework without having to unenroll and re-enroll a computer. These steps include better security, faster performance, support for paging, sorting and a much more consistent way of interacting with each endpoint.Hot off the presses is Jamf Pro version 10.36, which includes the first iteration of a feature that a lot of admins have been waiting to see for a long time. When directly compared to the Classic API, the Jamf Pro API is a step forward in many ways.
Jamf pro api software#
It is worthwhile to note that the Jamf Pro API goes through the same quality assurance and testing processes as non-beta software and is used when rendering pages in Jamf Pro’s web interface. Once those have been finalized and desired feature parity achieved, the Jamf Pro API will introduce versioning - providing dependability and consistency for each version. This is being done because the internal standards and style guide are still being worked on. This makes checking the release notes and change log that much more important to maintain custom workflows and integrations. The Jamf Pro API is in beta, which means there may be breaking changes each release. These will be documented in the release notes available on Jamf Nation and change log which is available on the Developer Portal. Jamf is working hard to introduce new endpoints with every release. Many Jamf Pro features aren’t yet available in the Jamf Pro API. As stated above, this won’t be an overnight change. This rebrand represents a large effort in both how Jamf develops software and how they want customers and partners to interact with Jamf Pro. Once we have reached an acceptable level of parity between both APIs, a sunset period will be communicated to ensure customers and partners can effectively transition to the new Jamf Pro API.
This will take some time and Jamf will continue to fully support the Classic API during this time period. The goal is to build out the Jamf Pro API to provide parity with the Classic API. Jamf has no immediate plans to deprecate the Classic API.
The Classic API is currently more utilized by Jamf customers. The Classic API (formerly known as the Customer API) and the Jamf Pro API (formerly known as the Universal API). With this initiative, Jamf is renaming two existing APIs. Allowing all customers and partners with the ability to leverage the information and capabilities of Jamf Pro to enhance their custom workflows or bring new innovations to their integrations. This means functionality is added and made available simultaneously. The APIs that Jamf uses to build Jamf Pro are the same ones that are available to its customers and developer partners. Primarily, this enables faster and more efficient webpages inside of Jamf Pro. This means that when developing its software, Jamf will be adding to its API to expose the new functionality. For example, is an endpoint that allows the user to see a list of macOS computers in their Jamf Pro environment. Those endpoints are a reference to a URL that accepts web requests formatted in a certain way. Resources in a REST API refer to an object or objects that are exposed at an HTTP endpoint.
API stands for Application Programming Interface, which is a standardized way a system can provide programmatic access of its capabilities to other systems.
0 kommentar(er)
