Samsung Knox app stuck pending on Android kiosk devices in Hexnode required appsSolved

Hello,
Thanks for reaching out to Hexnode Connect.
Samsung Knox itself is not a standalone application that needs to be deployed from Hexnode or the public Play Store. Knox is a hardware-backed security framework built into supported Samsung devices.

For managing Knox-related configurations through Hexnode, the required app is Knox Service Plugin. If Knox Service Plugin is already installed and marked as a required app, that is the component needed for Knox policy management.

To clear the pending/missing app compliance issue:

1. Open the app group or policy assigned to the tablets.
2. Remove the separate app entry named Samsung Knox from Required Apps.
3. Keep Knox Service Plugin in the required app list.
4. Save the policy and allow the devices to sync.

After the next successful sync, Hexnode should stop trying to install the non-installable Samsung Knox entry, and the missing app compliance warning should clear.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM

That makes sense. I removed the extra Samsung Knox entry and kept Knox Service Plugin.

One thing I noticed afterward: one of our enterprise APK apps shows as installed in the Hexnode console, but users say it is missing on the tablet. The device also is not entering kiosk mode. The enterprise app is uploaded to Hexnode and deployed through the same Required Apps policy.

Hello,
If the console shows the enterprise APK as installed but the app is not visible on the device, first refresh the actual app inventory reported by the device.

Use the following action on the affected device:

1. Go to Manage > Devices.
2. Open the affected tablet.
3. Select Actions > Scan for Apps.
4. Refresh the device page and check the Applications tab again.

If the app status changes from Installed to Missing, trigger the installation again using Actions > Install Application and select the enterprise APK from the app repository.

For Samsung devices using Knox-related policies, also make sure Knox Service Plugin is activated properly on the physical device and that required permissions are granted. In this case, once the missing permissions were corrected and Knox Service Plugin was activated, the enterprise APK installation completed successfully on the affected tablets.

Best regards,
George
Hexnode UEM

I ran the app scan and then manually triggered the enterprise app install again. The device was missing some permissions, and after activating the Knox Service Plugin properly, the APK installed on a couple of tablets.

A few devices are still showing non-compliant though. One has not checked in for several days, and another still shows an app compliance warning.

Hello,
For the device that has not checked in, no policy change is required. If the non-compliance reason is inactivity, the device should become compliant again after it powers on, connects to the network, and checks in with Hexnode.

For the device with an app compliance warning:

1. Open the device summary page.
2. Check the Compliance Info section.
3. Open Application Compliance to identify the exact required app that is missing.
4. If Install Missing Apps has already been triggered, wait for the device to process the install.
5. To speed up the sync, run Actions > Scan Device.

Once the required application is installed and the device checks in successfully, the application compliance status should return to compliant.

Best regards,
George,
Hexnode UEM