Why Some Setting Features and Payloads Are Supported for Specific OEMs and OS Versions in Workspace ONE UEM Console for Android Devices

C.

The Workspace ONE UEM Console is an enterprise mobility management (EMM) solution that allows organizations to manage their mobile devices, applications, and content. When configuring profiles for Android devices, some settings, features, and payloads may only be supported for specific original equipment manufacturers (OEMs) and/or operating system (OS) versions.

The reason for this is that profile configuration is dependent on operating system and firmware API availability. OEMs may implement Android differently, meaning some features may not be available on all devices. Additionally, Android releases new versions frequently, and with each new version, they may introduce new APIs or remove deprecated ones. This means that the features and payloads available for configuration may vary depending on the OS version.

It's important to note that profile configuration is not dependent on a device directly purchased from Google or an application built with the AirWatch SDK installed on the device. While these factors may affect the functionality of a device, they are not directly related to profile configuration.

Finally, it's worth mentioning that profile configuration is typically XML-based. However, the XML format and the supported payloads may vary depending on the OEM or OS. This means that some devices may not support certain XML-based payloads, and as a result, some settings may not be available for configuration.

In summary, the reason why some setting features and payloads may only be supported for specific OEMs and/or OS versions is that profile configuration is dependent on operating system and firmware API availability, and the XML format and supported payloads may vary depending on the OEM or OS.