Chapter 2 Creating and Deploying Configuration Profiles 21
This is where you provide the name and identifier of this profile.
A configuration name is required. The name you specify appears in the profiles list and
is displayed on the device after the configuration profile is installed. Although the
name doesn’t have to be unique, you should use a descriptive name that identifies the
profile.
The configuration identifier must uniquely identify this profile and must use the format
com.companyname.identifier, where identifier describes the profile. For example:
com.mycompany.homeoffice.
The identifier is important because, when a profile is installed, the Configuration
Identifier value is compared with profiles that are already on the device. If the
Configuration Identifier value is unique, information in the profile is added to the
device. If the identifier matches a profile already installed, information in the profile
replaces the settings already on the device.
Profiles can be verified by signing them, but signed profiles aren’t required. If you don’t
sign a profile, its status is shown as Unsigned when viewed on the device.
If you choose to sign a profile, and the signature can be verified by a certificate on the
device, its status is Verified. If the certificate necessary to verify the signature isn’t on
the device, or if the chain of trust cannot be linked to a root CA that is on the device,
then the profile’s status is Not Verified. Signed profiles are indicated with a checkmark: