Release Notes
Abstract
Device custom attributes support for iOS policy
Content
From 10.67 release, MaaS360 supports usage of device custom attributes as placeholder values in iPCU settings and in any input fields for an iOS policy. Using this functionality, device custom attributes can be applied to iOS devices through iOS policy settings. To ensure device custom attributes published through iOS policy is applied on an iOS device, values for these attributes must be defined for an iOS device in Devices > Custom Attributes tab.
How to set device custom attributes for an iOS device using policy settings?
The workflow includes step 1 and step 2 actions to be performed.
Step1: Manage device custom attributes for iOS device.
- You can manage device custom attributes from Devices > Device Attributes, click Manage Custom Attributes. You can add new custom attributes or edit existing attributes.
Viewing an example of Device Custom Attributes
- From Device Inventory, select iOS device and choose Custom Attributes from Device Summary page.
All managed custom attributes are listed here. - Edit Custom Attributes values as needed and save the settings.
Note: Customers can use the device attributes that are created in Apple Configurator by using %attribute% placeholder, then create a profile, and import the iPCU xml file containing these attributes in the iOS policy. The placeholder values for the attributes are replaced with the actual settings that are defined on the device. This enhances the ability to include custom attributes in to the device.
Step 2: Update iPCU settings for iOS policy.
- From Security > Policies, select an iOS policy and navigate to iPCU Import under Advanced Settings.
- Import settings that are created in iPCU by uploading new iPCU setting file and save or select an existing settings file from the list. Note: The file upload fails if the document contains DOCTYPE declaration.
Viewing an example of iPCU settings file with placeholder values for device attributes
- Save and Publish the iOS policy and click Confirm Publish to continue publishing the policy to the applicable devices.
-
Workflow result: Placeholders for device custom attributes are replaced with custom attribute values that are defined for an iOS device in Step 1 and the policy is applied to the device. Hence, device custom attributes are supported for iOS policy.
Note: Installation of custom iPCU payload to the device fails if the device does not have custom attributes defined but OS policy containing iPCU xml is applied on the device.
Was this topic helpful?
Document Information
Modified date:
09 January 2019
UID
ibm10794549