What

The intended result of the creation of a configuration profile is always to make some change to configuration of endpoints.  What those changes are, and how they are made differs profile by profile.

When/Why

Profiles tend to fall into two categories:

  • Stuff we've done before
  • New stuff we haven't touched before

The first is no trouble, because we know what we are doing.  For instance, after we have already created a wi-fi config profile for 41 of our 42 locations, the 42nd one isn't going to be too much trouble.

But, what if we have something new to do that we haven't done before?  There are two answers to this:

  1.  Experiment and test (no better teacher than experience with a device in hand)
  2.  Read the documentation (yes, seriously): 
    1. https://support.apple.com/guide/mdm/welcome/web#/mdmf0ec4d860

    2. FileWave (nor any other MDM provider) defines what the elements in profiles are or what they mean.  The above reference explains them all
    3. For third-party settings, reference the Vendor's documentation 

How

Defining MDM elements is out of scope for our Knowledge Base, but we can give best-practice guidance on building and testing profiles:

  • Build profiles (especially restrictions) as small as possible...do not intermix settings if at all possible
    • This prevents having to split profiles later when you have the inevitable exceptions to deal with
  • Test, test, and then test again against a device in your hands
  • Never create and deploy a profile to production without testing
  • Be especially careful with edits to already assigned profiles (especially wi-fi or anything else where a mistake could cause catastrophic consequences)

Here is a simple example of setting a Wallpaper and preventing it from being changed (notice two payloads, but related):


Related Content

Unable to render {children}. Page not found: beta:Add Profile/.