Custom profiles for iOS 10

Custom profiles for iOS 10

iOS 10 offers a variety of advanced MDM functionality that can be configured through Profiles in the AirWatch Admin Console. 

New iOS 10 features are available as part of AirWatch 8.4.5. Administrators on an earlier AirWatch version can run the iOS 10 seed script to allow support of iOS 10 devices, and use the following custom profiles to achieve the same functionality.

The XML code for these custom profiles is listed below and can be implemented using the following procedure.

Using Custom Profiles 

The Custom Settings payload allows admins to enter their own XML into a profile and apply the profile to devices. Follow the steps below using the iOS 10 code found at the end of this document.

1. Configure the General payload and deployment options as desired.

2. If you would like to include any iOS 10 features that are not available in the UI for your version, you can add the associated XML below to the Custom Settings payload for your profile. 

  • This XML should contain the complete block of code as listed below, from <dict> to </dict>. 
  • Administrators should configure each setting from <true /> to <false /> as desired. 
  • If certificates are required, then configure a Certificate payload within the profile and reference the PayloadUUID in the Custom Settings payload. See further information within the examples below.

Custom_Profiles.jpg 

iOS 10 Custom Profile XML Code

Use the following link to download custom XML Code. View all custom XML code examples here.

 

Disable Bluetooth modification

Disables the ability to make modifications to Bluetooth settings. This will be available under the existing Restrictions payload

 

<key>allowBluetoothModification</key>

<false />

 

QoS Marking Policy

Apple and Cisco have partnered to deliver better app and voice experience for iPhones and iPads on corporate networks. Essentially customers using the new Cisco Routers and Access points can prioritize traffic such as Webex or Facetime so the bandwidth is allocated more to what is required for business.

Please read the following article for more information: 

http://www.apple.com/ipad/business/work-with-apple/cisco/ 

With MDM, customers with the Cisco infrastructure can : 

  1. Enable or Disable use of Cisco QoS fast lane network
  2. Whitelist Applications to benefit from L2 and L3 marking
  3. Enable Audio and Video traffic for built-in services such as FaceTime and Wi-Fi calling for L2 and L3 marking for traffic sent to Wi-Fi network

This will be available under the existing Wi-Fi Payload. 

An example of the custom XML is provided below. The QoS-specific keys are highlighted in bold. These keys need to be added in addition to a Wi-Fi payload with the respective settings.

 

<dict>

    <key>PayloadDescription</key>

    <string>Configures wireless connectivity settings.</string>

    <key>PayloadDisplayName</key>

    <string>WiFi (1)</string>

    <key>PayloadIdentifier</key>

    <string>e87021a8-6578-444a-ac66-e5ddfa4b6f17.Wi-Fi</string>

    <key>PayloadOrganization</key>

    <string></string>

    <key>PayloadType</key>

    <string>com.apple.wifi.managed</string>

    <key>PayloadUUID</key>

    <string>7c5abc0d-da0c-41cc-b9fd-5a062cb30fbd</string>

    <key>PayloadVersion</key>

    <integer>1</integer>

    <key>ProxyType</key>

    <string>None</string>

    <key>SSID_STR</key>

    <string>Corporate_Wifi</string>

    <key>HIDDEN_NETWORK</key>

    <false />

    <key>EncryptionType</key>

    <string>Any</string>

    <key>AutoJoin</key>

    <true />

    <key>IsHotspot</key>

    <false />

    <key>QoSMarkingPolicy</key>

    <dict>

        <key>QoSMarkingEnabled</key>

        <true />

        <key>QoSMarkingAppleAudioVideoCalls</key>

        <true />

        <key>QoSMarkingWhitelistedAppIdentifiers</key>

        <array>

            <string>{App BundleID}</string>

        </array>

    </dict>

</dict>

 

Default Calling App for Exchange

This feature configures the exchange account to default calls that are made from clicking phone numbers from messages to the app configured in the profile. 

Applications used as the default calling app need to use the CallKit framework.  Contact the application developer for more questions on support for CallKit by the application.

This configuration will be part of the existing EAS payload

An example of the custom XML is provided below. The Calling App-specific keys are highlighted in bold. These keys need to be added in addition to an EAS payload with the respective settings.

 

<dict>

    <key>EmailAddress</key>

    <string>{EmailAddress}</string>

    <key>Host</key>

    <string>com.test.com</string>

    <key>MailNumberOfPastDaysToSync</key>

    <integer>3</integer>

    <key>SSL</key>

    <true />

    <key>UserName</key>

    <string>{EmailDomain}\{EmailUserName}</string>

    <key>PayloadDisplayName</key>

    <string>Exchange ActiveSync</string>

    <key>PreventMove</key>

    <false />

    <key>PreventAppSheet</key>

    <false />

    <key>SMIMEEnabled</key>

    <false />

    <key>disableMailRecentsSyncing</key>

    <false />

    <key>allowMailDrop</key>

    <false />

    <key>CommunicationServiceRules</key>

    <dict>

        <key>DefaultServiceHandlers</key>

        <dict>

            <key>AudioCall</key>

            <string>{App BundleID}</string>

        </dict>

    </dict>

    <key>PayloadDescription</key>

    <string>ExchangeActiveSyncSettings</string>

    <key>PayloadIdentifier</key>

    <string>5bbf91dc-11e4-48d5-a344-54e6e3a0c8fe.Exchange ActiveSync</string>

    <key>PayloadOrganization</key>

    <string></string>

    <key>PayloadType</key>

    <string>com.apple.eas.account</string>

    <key>PayloadUUID</key>

    <string>5de53c17-d179-4bb8-8d3d-5f2792be2a89</string>

    <key>PayloadVersion</key>

    <integer>1</integer>

</dict>

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.