Category filter

Custom configuration profile reference for iOS devices

Configuration profiles are XML files that enable IT admins to customize configurations of managed devices, enforcing specific policies, settings or restrictions. This document serves as a repository of custom configuration profile references that can be deployed to iOS devices for various use cases. With Hexnode UEM’s Deploy Custom Configuration policy, IT admins can deploy these configuration profiles to iOS devices remotely.

How to create and deploy configuration profiles?

  1. Determine configuration requirement – Identify the specific restrictions, policies or settings you want to enforce on the iOS devices.
  2. Select a method of creation – Configuration profiles can be created using profile creator tools such as Profile Creator, Apple Configurator, iMazing Profile Editor etc. You can also create them using text editors.
  3. Configure the profile settings – Use the above-mentioned tools to create the required configurations. You may also refer to these payloads.
  4. Test the configuration profile – Test the profile manually on iOS devices.
  5. Deploy the configuration profile – Once the profile is tested and validated, follow these steps to execute it in bulk using Hexnode UEM:
    1. Login to the Hexnode UEM portal.
    2. Navigate to Policies > iOS > Deploy Custom Configuration and click Configure.
    3. Click Choose File and upload the configuration profile.
    4. Click OK and associate the policy with the required devices/device groups.

    Non encrypted files of the following extensions – .mobileconfig, .xml, and .plist can be deployed via Hexnode UEM.

Custom configuration profiles

Serial No Configuration profile
1 Set passcode requirements
2 Configure Global HTTP Proxy
3 Configuration profile for the allowlist AirPlay on iOS devices
4 Single app lockdown
5 Configure Email
6 Web content filter
7 Single app mode

  • While defining a profile, ensure it contains all the mandatory payload keys, including PayloadUUID, PayloadType, PayloadVersion and PayloadIdentifier, etc.
  • Binary .plist files cannot be used to deploy custom configuration profiles. You can convert the binary .plist files to normal .plist files using the terminal command: plutil -convert binary1 <name of the .plist file>.
  • Generic .plist files alone can’t be used to deploy custom configuration profiles. It is recommended to choose an appropriate payload, add profile-specific payload keys to the configuration profile, and verify them before uploading it.
  • While distributing the configuration profiles to the devices, make sure that no conflicting configurations are pushed.
  • You can use wildcards while deploying custom configuration profiles.

  • Configuration Profile Repository