Profiles are created to impose one or more policies and restrictions to the managed devices/groups. You need to create separate profiles for iOS, Android and Windows devices respectively.Follow the steps mentioned below to create a profile.
Click Create
Profile and choose the platform as iOS,
Android or Windows, for which you wanted to create the profile.
Provide the below mentioned basic information:
Name of the Profile: Unique name to identify the profile
Description: A brief description about the profile
Customize Profile for (This is applicable only for Android) : In case of KNOX devices, apart from creating profile for Device, profiles can be created for KNOX containers by choosing the option KNOX Container. For all other Android devices, choose the option Device to create profile for devices.
Click Continue
Under Define Profile from the left pane, select the configuration profile ( iOS / Android / Windows ) and define the policies and restrictions of the profile. You will have to save the individual configurations before you move on to the next configuration within the same profile.
After specifying the required configurations, click Publish.
A published profile is not applied to any of the devices until they are associated to the devices or groups. |
Let us assume you are associating two profiles to the same device:
Profile 1: Restricts camera and sets minimum passcode length as 4
Profile 2: Allows camera and sets minimum passcode length as 6
Let us see how the profiles get applied on the devices:
PLATFORM | DESCRIPTION | CAMERA | MINIMUM PASSCODE LENGTH |
iOS | Most secure combination of settings get applied |
Restricted | 6 |
Windows | Most secure combination of settings get applied |
Restricted | 6 |
Android | Most recent profile settings get applied |
Allowed | 6 |
To modify a profile,
On the web console, navigate to Profiles
Under Profiles tab, you can view the list of all the profiles that have been created already.
Click on the ellipsis icon under the Actions column, of the profile that you want to modify and select Modify Profile from the dropdown. You can add or remove configurations from the profile.
After making the required changes, click Save to save the changes.
Click Publish to save the changes made to the Profile.
When a profile is modified and published, it is not applied to the devices to which they were applied before. A new version of the profile is listed, you can upgrade the latest version to the group, so that the current members of the group will have the latest version of the profile applied to them. The previous version of profile will be overwritten by the latest version. |
Copy Profile lets you duplicate profiles which were previously created using Mobile Device Manager Plus (MDM). Instead of creating profiles and configuring policies from scratch every single time, you can duplicate an existing profile and subsequently add/remove/modify the configured policies according to your organizational needs. This way, existing profiles can be used as a base instead of creating new ones. MDM differentiates the duplicate profiles from the original ones with the profile name followed by _Copy. The profile name can be modified as well.
Benefits:
To duplicate a profile on MDM,
|
When you want to delete a profile associated with devices/groups, you can simply move the profile to Trash. Moving profiles to Trash ensures the profiles are automatically disassociated from the devices/groups. These profiles are automatically deleted after 90 days. The profiles can also be deleted or restored manually from Trash by the user. However, the restored profiles don't automatically get associated with the previously associated groups/devices. These restored profiles can be associated to the devices/groups.
The following steps explain the moving of profiles to Trash:
On the web console, navigate to Profiles
Under Profiles tab, you can view the list of all the profiles that have been created already.
The profiles can be viewed by clicking . The profiles can be deleted or restored from here.
Policies which require constant changes such as Restrictions should not be grouped with e-mail account related policies such as Exchange, Wi-Fi etc., as every time a modified version of the profile containing all these policies is re-distributed, the passcode for the account-based services such as Exchange and configurations such as Wi-Fi preferences, previously synced mails etc., specified in the account-related policies is reset and has to be manually entered by the user again. Consider the case of Exchange - as MDM uses third-party mail clients such as Gmail, Samsung mail to configure Exchange, even reassociating the same policy (with/without modification) removes the existing configuration and then configures Exchange based on the newly associated policy. This may require some user input.
SCEP and the associated account policies which are to utilize the certificate provisioned by SCEP must be configured in the same profile. This ensures the same SCEP certificate is used for all the account-related policies configured in the profile.
See Also: | Configure Mobile Device Manager Plus, Device Enrollment, Location Tracking,App Management, Profile Management, Asset Management, Security Management , Reports |