Hey Hexnode Community,
I’ve got an enrolled device flagged as Non-Compliant, and I think the issue seems to be with one of the Required Apps policy I pushed out.
The app is definitely installed on the device, so I’m confused about why the compliance check is failing. Does anyone know why this might be happening and what I can do to clear this compliance status?
13 Views
@laura123 , this could be an issue with the success criteria mismatch. This basically means that the version of the app installed on the device no longer matches the specific version your policy expects your device to have.
When you set up a Required Apps policy, you define the “success criteria“ with the exact app identifier of the app that is to be installed. If the app identifier specified in the policy is different from the actual app identifier of the app, a success criteria “mismatch” occurs. Therefore, the device is flagged and displayed as non-compliant in the system.
Here is how you can fix this,
Check the installed version: Find the actual version of the app currently on the non-compliant device.
Navigate to Manage > Devices.
Select the non-compliant device.
Go to the Applications sub-tab and note the Installed Version of the problematic app.
Update the policy:
Next, you’ll update the Required Apps policy to reflect the new app identifier of the new version of the app.
Go to Policies and select the required app policy.
Click Manage > Modify.
Locate the app in the Required Apps and under Installation Settings, click on Configure.
Here, under App Identifier, enter the new app identifier. Then, click Save.
After saving the policy, go ahead and re-push it into the devices. The Non-Compliant status should clear!
@kylian_parker , thank you mate. That worked out.
Don't have an account? Sign up
