OLE DB or ODBC error: Exception from HRESULT: 0x80040E4E. Error returned: 'OLE DB or ODBC error: Web.Contents failed to get contents from ' ' (502): Bad Gateway. Hello followed those links but I'm getting these error messages:Ĭomputer Device Groups Failed to save modifications to the server. Hopefully you find the cause on your side soon! Keep us posted. Perhaps you're experiencing a similar blockage on your end, but it seems ours was specific to our environment. I know I'm missing some details that I wasn't given, but the bottom line is that it's working again and it seems to coincide with the error message with LDAP and restart of this other server. The Jamf server wasn't down and could be accessed and worked with directly, but data connections were blocked. The cause of that was that the a server was stuck in a hung state and needed to be rebooted, but it was prohibiting network connectivity to complete the data request. Then our admin explained that they had seen the bad gateway error on the LDAP connector to the Jamf server. I explained to our admin and the engineer that we would normally see a bad gateway error message. In our meeting, I ran a test on the connector again and today it worked. □ Developer docs for jamf-management-frameworkĭon't hesitate to submit new FRs or contact your support team if you have additional questions or feedback around this new feature.Hi had our meeting with the Jamf engineer this morning. □ Here's a link to Jamf Pro 10.36 release notes. □ Here's a link to the original Jamf Nation feature request. A computer must be MDM managed and receiving/processing MDM commands issued from the Jamf Pro server you expect it to be enrolled in and managed by.Jamf Pro server on version 10.36 or later.Log show -info -debug -predicate 'subsystem = "" AND category = "ManagedApps"' -last 1hĪnd just to clarify, there are requirements for this functionality to work for you: To check for the installation of the QuickAdd locally on a device, you can filter log events like so: If you're not confident you can pass that information securely when running this command, just use the API endpoint outlined in the steps above and avoid running the command locally on a device. Be careful where and how you invoke commands like the above. Passing tokens or user:password auth in plaintext is dangerous business. It would look something like this (where 3 is the computer ID in this scenario):Ĭurl -X POST "" -H "accept: application/json" -H "Authorization: Bearer bigLOngTOkEnTHiNghEre" ⚠️ 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |