Profile Editor
- Former user (Deleted)
- lsh (Unlicensed)
- Mikkel Knop
Introduction
In the Profile Editor, one or more Payloads can be configured, and saved in a Profile with a specified name and description. When the profile is assigned to a device, it and its payloads will be installed on that device. This could be WiFi settings or a web clip etc.
For specific configuration guidelines for individual payloads see: Profiles
Create a profile
In order to open the editor and create a new profile follow the steps below
Similar to packages and power schemes, profiles can only be created and edited in root CMPs, and from there be promoted to child CMPs.
If any mandatory fields have been skipped, or the input is invalid, they will be marked by an exclamation mark!
- Expand a root Configuration Management Point
- Right-click on Profiles
- Select Create Profile
- Specify a name for the profile and a description
- Select and configure a profile from the available payloads in the right toolbar
- If the status is set to inactive, the profile can be configured and assigned to devices, without being installed on any of them. It will not be removed from devices that already have the profile installed. However the priority determines the order in which profiles are installed, and if a removal password is specified it prevents users from manually removing the profile from their device without knowing this password.
- It is recommended to add several payloads to one profile if they are logically connected. Examples of payloads which can be logically combined into one profile can be something like a profile called "Wifi Denmark", containing payloads with all the WiFi access points in this region. Another example of a profile that could contain more payloads would be a "Common restriction profile", in this there could be both an iOS restriction payload and an Android restriction payload. CapaInstaller will ensure that only the device compatible payloads will be deployed to each device.
User and Device Variables
It is possible to enter user variables and device variables in profiles instead of hardcoded values.
$Email$ will use the email of the primary user of a device, retrieved from active directory. The full list of supported variables will be shown if ‘$’ is entered in any of the payload input controls and will be inserted at the cursor's location by selecting one in the list. |
|
Edit or View Profile
In order to open the Profile editor and edit/view an existing Profile
Right-click on the Profile in the root Configuration Management Point (CMP), and select Edit
Right-clicking a profile in a child point, you can select 'View' in order to open it in the Profile editor. All the settings can be seen but in a view-only mode.