Apple iPod and iPod Touch Preparing Configuration Profiles for Deployment

26 Chapter 2 Creating and Deploying Configuration Profiles

The Configuration Identifier field in the General pane is used by the device to

determine whether a profile is new, or an update to an existing profile. If you want the

updated profile to replace one that users have already installed, don’t change the

Configuration Identifier.

Preparing Configuration Profiles for Deployment

After you’ve created a profile, decide whether you want to distribute it to users by

email, or by posting it to a website. When users use their device to open an email

message or download the profile from the web, they are prompted to start the

installation process. See “Installing Configuration Profiles” on page 27 for information.

Some of the information contained in a profile is obfuscated to prevent casual

snooping, but the profile isn’t encrypted. Make sure the file is accessible only by

authorized users.

To send a profile by email, click the email button. If you’re using the Mac OS X version

of iPhone Configuration Utility, a new Mail message opens with the profile added as an

uncompressed attachment. If you’re using the web-based version, the profile is emailed

to the address you specify.

To post a profile for downloading using Safari on iPhone or iPod touch, click the Export

button. This creates a .mobileconfig file in the location you specify, ready for posting to

your site.

Don’t compress the .mobileconfig file, or the device won’t recognize the profile.

Additionally, you must configure your web server so that .mobileconfig files are

transmitted as application/x-apple-aspen-config files.

Mac OS X Server

If your web server is Mac OS X Server v10.5.3 Leopard or later, it is already configured

for correctly transmitting .mobileconfig files.

For Mac OS X Server versions prior to v10.5.3, add the following MIME type to the MIME

Types settings using Server Admin:

application/x-apple-aspen-config mobileconfig

This ensures that all .mobileconfig files, regardless of where they are stored on your

web server, are correctly sent to clients.

Alternatively, add the MIME type to httpd.conf or one of its subconfiguration files,

provided that your Apache configuration allows directory overrides:

AddType application/x-apple-aspen-config mobileconfig