crosrooms.blogg.se - Cannot connect to jamf pro server

CANNOT CONNECT TO JAMF PRO SERVER PRO
CANNOT CONNECT TO JAMF PRO SERVER PASSWORD
CANNOT CONNECT TO JAMF PRO SERVER MAC

How many devices are affected (all devices or just some)ĭevices are marked as unresponsive in Jamf ProĬause: The following are common causes of devices being marked as Unresponsive by Jamf Pro:.How many users are affected (all users or just some).

CANNOT CONNECT TO JAMF PRO SERVER PRO

When the problem started, and whether your Jamf Pro integration with Intune worked previously.

You must have a user account that has Global Admin permissions in Azure.Ĭollect the following information when investigating Jamf Pro integration with Intune:.

You must have a user account that has Microsoft Intune Integration permissions in the Jamf Pro console.

All users must have Microsoft Intune and Microsoft Azure Active Directory (Azure AD) Premium P1 licenses.

Use the Jamf Cloud Connector to integrate Jamf Pro with Intune.

Review the prerequisites from the following articles, depending on how you configure Jamf Pro integration with Intune:.

Consider the following before you start troubleshooting: For example, when you encounter a Jamf-Intune integration-related issue, always verify that prerequisites have been met. Prerequisitesīefore you start troubleshooting, collect some basic information to clarify the problem and reduce the time to find a resolution. For more information, see Transitioning Jamf macOS devices from Conditional Access to Device Compliance. If you have questions or need help, contact Jamf Customer Success. If you use Jamf Pro's Conditional Access integration for macOS devices, follow Jamf's documented guidelines to migrate your devices from macOS Conditional Access to macOS Device Compliance.

Starting from September 1, 2024, the platform that Jamf Pro's Conditional Access feature is built on will no longer be supported. Massive thanks to gabe2385 and junjishimazaki for their assistance.Jamf macOS device support for Conditional Access is being deprecated. If your company does not use logins verify that any login keys are removed). Verify Keychain Access keys are correct (publickey, privatekey, and login if used. Verify that the jss_url is correct in /Library/Preferences/ so it gave an unable to connect to MDM server error as a result. Further attempts to open Self Service were relying on those credentials and those were being denied by the server.

CANNOT CONNECT TO JAMF PRO SERVER PASSWORD

Removing the login password from Keychain Access resolved the issue.įrom what I can tell, it seems someone tried to log into Self Service, and saved credentials which don't actually work there. We don't use the user logins on Self Service (it has been enabled for techs, but not for standard users and isn't built out enough for regular use). It is Keychain Access, but it's not the private or public key the user had a password enrolled for automatic login to Self Service. This information allowed us to further troubleshoot and we were able to find the issue! If anyone has any idea what this could be I'm open to further troubleshooting. Self Service appears to be the only thing affected.

CANNOT CONNECT TO JAMF PRO SERVER MAC

The Mac still has access to jamf controls via terminal, still receiving profiles and policies, still reporting in all information to the server. Issue is present both on and off VPN (so that is irrelevant).Ĭurrently this is only affecting the one machine but as I don't have a fix there's trouble if it spreads. I did find the list of ports, but we aren't seeing any blocked ports (on machine, router, or via ISP). also tested:Ĭomputer restart, trying from an IT account (removes any variables from the users startup items), refreshing the MDM, clean uninstall and reinstall of the JAMF Framework. There's a similar error "connecting to jamf server" which can be resolved by simply uninstalling and allowing JAMF to reinstall Self Service. We've been using JAMF for a few years mostly without issue - this is the first time we're seeing this error.

The last post I can find relating to this is from 2017 There isn't a solution there and I've tried almost everything previously listed.