

- OEM APPLICATION PROFILE AMD HOW TO
- OEM APPLICATION PROFILE AMD UPDATE
- OEM APPLICATION PROFILE AMD FOR ANDROID
Intune doesn't maintain older versions of the schema or the app.

Intune always syncs the latest version of the OEMConfig app from Google Play.
OEM APPLICATION PROFILE AMD UPDATE
We recommend contacting the OEM for more information on managing their devices with OEMConfig.Īt any time, OEMs can update their supported features and schemas, and upload a new app to Google Play. For example, Intune doesn't have any control over strings, language, the actions allowed, and so on. Intune doesn't influence or control the content of the app schema. If you find a problem that originates in the schema, contact the OEM for guidance. So if the schema is incorrect, or has inaccurate data, then this data is still sent to devices. Intune doesn't validate or change the schema provided by the app. Intune exposes the OEMConfig app's schema so you can configure it. When using OEMConfig, be aware of the following information: You can only use OEMConfig with devices that support this feature and have a corresponding OEMConfig app. As an administrator, you get these new features and updates (including fixes) without waiting for EMMs to include these updates. When the OEM adds and improves management features, the OEM also updates the app in Google Play. Device settings are executed by the OEMConfig app, instead of an MDM agent built by the EMM. When the OEMConfig app installs on a device, it uses the settings configured in the EMM administrator console to manage the device. The console allows Intune administrators to configure the settings in the schema. The EMM reads the schema from the app, and exposes the schema in the EMM administrator console. The OEM embeds the schema into an app, and then puts this app on Google Play. With OEMConfig, an OEM creates a schema that defines OEM-specific management features. This approach leads to duplicated efforts and slow adoption. Historically, EMMs, such as Intune, manually build support for OEM-specific features after they're introduced by the OEM. Learn more about OEMConfig (opens Google's web site). This standard allows OEMs and EMMs (enterprise mobility management) to build and support OEM-specific features in a standardized way. OEMConfig is a standard defined by Google that uses app configuration in Android to send device settings to apps written by OEMs (original equipment manufacturers). OEMConfig policies are a special type of device configuration policy similar to app configuration policy.
OEM APPLICATION PROFILE AMD HOW TO
This article describes OEMConfig, lists the prerequisites, shows how to create a configuration profile, and lists the supported OEMConfig apps in Intune. To manage Zebra Technologies devices using Android device administrator, use Zebra Mobile Extensions (MX). The available settings depend on what the OEM includes in their OEMConfig app. Different original equipment manufacturers (OEM) include different settings. OEMConfig is typically used to configure settings that aren't built in to Intune.
OEM APPLICATION PROFILE AMD FOR ANDROID
In Microsoft Intune, you can use OEMConfig to add, create, and customize OEM-specific settings for Android Enterprise devices.
