Non-Compliant Devices
When the machines have been started this morning, compliance issues were found and the Company Resources were unavailable. In the Company Portal application which is also connected to the Jamf Pro, there were two different devices with the same serial number: one was marked as compliant and the other as non-compliant.
Upon refreshing and the status, the same device had still two entries: one entry showed as compliant and the other one as non-compliant.
As a solution for Compliance issues, we have the dedicated procedure as seen below:
Restoring Compliance
In the event of non-compliance, users can follow these straightforward steps to restore their MacBook's compliance. Click on the respective button on the right to open the respective guideline in your support app.
1. Install System Updates:
Make sure that all relevant system updates are installed on the MacBook.
This ensures that the device is up to date. Install Updates
2. Executing Policy Updates:
Implementing the latest policy updates ensures the MacBook
adheres to current security standards Update Policies
3. Updating Inventory Information:
Refreshing the MacBook's inventory information in the system
guarantees the accuracy of its compliance status. Update Inventory
4. Restarting the MacBook:
A simple restart can often resolve minor issues and help in
regaining compliance.
Furthermore, when comparing the devices in Intune and Jamf Pro, in Jamf Pro the device appears as managed and compliant, however, in Intune it has no MDM, Security nor Compliance information.
The above steps were tried for three times, with three different reboots and the device still had compliance issues. However, after the forth reboot, the device was suddenly compliant.
At the moment, we have several devices which are experiencing the same compliance issues and we would like to know if there is a fixed solution for the detailed error.
We are currently in talks with our service providers to analyse the issue.
It is also probable that the issue was solved by restarting the device, but at the time being, we should be looking for a root case analysis as well.