Hi Sabrina,

Thanks for posting on SOTI Pulse.

Thanks Rafael Schäfer, Raymond Chan and Zafer Cigdem for responding to the post, your expertise and willingness to help are greatly appreciated!

We understand you're facing issues deploying the System Update Policy profile to your Android devices. From the screenshots shared, it seems a large number of devices are showing installation failures.

The message “failed to install because all of its payloads cannot be installed” typically means that the payload (in this case, likely the System Update Policy) is not compatible with the device's Android version, OEM, or device configuration.

Here are a few steps to troubleshoot further:

1. Device Connectivity
   
   Ensure the devices are online and actively communicating with MobiControl. Profiles cannot be deployed to devices that are offline, which is a common cause of the “Installation Failed” status.
   
   
2. Confirm Android Version & Manufacturer Support
   
   System Update Policies rely on Android Enterprise APIs and are not supported across all manufacturers or older Android versions. Check that the device is:
• Enrolled as a Work Managed Device (Android Enterprise)
• Running a supported Android OS version (usually Android 8+)
• From an OEM that supports this restriction (e.g., Samsung Knox, Zebra, etc.)
  
  
3. Profile Compatibility
   
   Ensure the System Update Policy profile is supported by the Android version and OEM build running on your devices. Not all manufacturers support the full range of Android Enterprise controls — especially for system-level restrictions like OS updates.
   
   
4. Check Profile Type
   
   Please ensure that the System Update Policy is specifically configured and applied to Android Enterprise (Work Managed) devices only. If a policy designed for Android Enterprise is mistakenly pushed to devices enrolled under Android Plus (Classic), or to a mixed group of devices with different enrollment types, the profile installation may fail due to compatibility issues.
   
   
5. Test on a Known Compatible Device or Use Clone Profile for Testing:
   
   Before applying changes across all devices, create a clone of the profile and assign it to a few test devices. This helps isolate any configuration or compatibility issues without impacting your production fleet.
   
   
6. Profile Composition
   
   If there are multiple payloads in the profile (besides System Update Policy), consider breaking them into separate profiles to isolate the failure. Check if there is any Lockdown profile or Feature Control payload which is restricting the installation.
   
   
7. Retry Deployment
   
   For devices that show “Installation Pending” or “Installation Failed,” you can attempt to redeploy the profile after confirming the device is online and reachable.
   
   

We appreciate your effort in reporting this.

Warm regards,
KTMOD

You should reach out to support in such case to investigate if this is an (maybe device specific, if all the same) issue and how to fix that

Have you checked the device-agent log file for any entries related to the profile installation attempt?  There might be more information on why the installation failed.

Hi Sabrina,

it looks like only 3 devices installed the profile well, is this number still same?
is there any difference between these devices who installed the profile well, and others.

Zafer