We do not collect any personal information, such as the contents or names of personal files (documents, emails, pictures, browsing history, etc). We have customized Jamf to only collect the data that is required to support macOS devices. Software patches, antivirus protection, and firewall policies will be well maintained.Ĭompliance: Your device will always be in compliance with UCLA security standards.įlexibility: You have the ability to install new software or get support through the use of Self Service. Security: DTAs will manage the security of your machine.
Your personal data will never be scanned, indexed, or transmitted off the device. Reliability: Software updates and patches with little to no user interaction.Ĭonfidentiality: Your data and files will remain confidential. If you’d like to learn more about Jamf Pro, please visit What benefits do I receive from Jamf Pro? This allows us to maintain a current inventory, deploy machines, update software & settings, and respond to security incidents much sooner. Jamf enables our IT staff to support macOS devices with greater flexibility and efficiency. If this is an urgent issue, please open a TAC case to investigate further.Jamf Pro is an enterprise management software for Apple devices that simplifies IT management for Mac, iPad, iPhone, and Apple TV. If you're using the non-randomised Wireless connection and have confirmed that JAMF has registered the same MAC address that ISE sees from the authentication, you will probably need to setup the debug logs as per this document and review the ise-psc.log to see what response ISE is getting from the MDM server. There is an enhancement in ISE 3.1 to mitigate both of these issues, but it also requires the MDM vendor to support the new MDM APIv3 (which I don't know if JAMF has implemented yet).
If the MacBooks are using a dongle for Wired connections and/or the Wifi connection is using a randomised MAC address, it will break the MDM checks. You should confirm that the MAC address that ISE sees from the endpoint is what is captured by JAMF as part of enrolment. The MDM API used prior to ISE version 3.1 (APIv2) uses the MAC address of the endpoint as the only identifier to check against the MDM server.
0 kommentar(er)
