Configuration profiles are XML files that contain pre-configured system settings. You install them on a device to configure the settings. Except for passwords, users generally can’t change settings that are defined in a configuration profile. On iOS devices, you can mark a profile as being locked to the device, so when installed it can only be removed by wiping the device of all data (or by entering a passcode).
What do they contain?
Configuration profiles contain payloads that load settings and authorization information onto OS X or iOS devices. Some payloads are for use only with OS X, some are only for iOS devices, and some apply to both.
Payloads contain settings like:
Client security policies and restrictions
Network and VPN settings
Mail and calendar account logins
Accounts configured by a profile can only be removed by deleting the profile.
How do I create them?
You create configuration profiles for:
users
devices (either iOS devices or Macs)
groups of users or devices
You use the Profile Manager service to create the profiles. Profiles that apply only to users aren’t available when you’re creating a device configuration profile.
Although you can create a single configuration profile that contains all payloads for your organization, consider creating separate profiles that are defined by settings that rarely change, and settings that may change often. You may also want to create separate profiles for specific devices or a group of users.
For more information, see Apply payloads effectively.
How do I install them?
You can distribute configuration profiles by:
Profile Manager’s built-in user portal and mobile device management server
A link on your own webpage
Sending it as a mail attachment
When the user downloads the profile from the portal, webpage, or mail message, he or she is prompted to install the profile. When you use Profile Manager as a mobile device management server, you can push out new and updated profiles to users after they enroll their device.