The free version of Miradore Online offers a multitude of . One of these is the configuration profile for controlling the use of the screen lock passcode in mobile devices, including the passcode complexity requirements.
In this blogpost we’ll walk you through the steps of specifying a passcode policy, applying the passcode policy to any number of devices, and how to follow through on policy compliance with reports.
Before you start
To enable a screen lock passcode policy with Miradore Online:
- Go to your Miradore Online instance (if you are not yet registered, you can register here).
- Make sure you have administrator access to Miradore Online.
- Some devices will already need to be enrolled in Miradore Online (if not, here are instructions for doing so).
Defining the policy
In Miradore Online, the Configuration profiles view is where configuration profiles are managed — let’s have a closer look.
Open the view and hit Create configuration profile from the Actions menu on the right-hand side. After that, a wizard opens (see screenshot below) allowing you to choose the device platform for which the configuration profile will be created. Choose your desired platform and hit Next.
Then, you’re asked to choose what you’d like to configure with the configuration profile. In this case, choose Passcode and hit Next.
In the next step, you will have the chance to configure the actual passcode settings and requirements. Notice the additional tabs where you can find additional settings, such as the passcode expiration age, the maximum number of failed attempts before a device gets wiped, the history of restriction for preventing the reuse of old passcodes, and the maximum time until the screen is automatically locked. Moreover, in the Default passcode tab, you can even define a new passcode.
Lastly, you are asked to give a name and description for the configuration profile — and then it’s ready to go.
If you want to create a similar passcode configuration profile for other device platforms, simply repeat the above steps, but choose another device platform when starting to create the profile.
Deploying the policy
The easiest way to apply a passcode policy to devices is to do it through the Devices view (see screenshot below).
First, filter and sort the view according to your preferences and then use the check boxes in the leftmost column to choose the devices that should be affected. Then choose Deploy configuration profile from the Actions menu on the right.
A wizard opens again asking you to choose what configuration profile you want to assign to the selected devices. Choose the passcode policy that you created, and hit Next.
As a precaution, you will be asked to confirm the deployment once more before anything happens. Click Deploy to start the distribution.
Following through on compliance
You can track the progress of the policy deployment on the Deployments tab of each Configuration profile page ( see screenshot below). From there, you can quickly spot if the policy deployment has failed for any of the devices.
For general reporting purposes, you can utilize the Dashboard view that shows you a variety of charts and widgets that visualize the status of your managed mobile devices. Here you can get an overall picture whether your devices on ALL platforms have any passcode set. If you click on the red section of the doughnut, you will see a list of the devices that still do not have a passcode set.
Miradore Online Enterprise lets you create business policies
In addition to the capabilities discussed in this blogpost, our Enterprise Plan offers the opportunity to create advanced business policies. With the upgraded plan, your selected configuration policies, files, and applications can be automatically deployed to all devices that are within the scope of your organization’s mobile device management guidelines.
This is an efficient way to make sure that all devices are and remain compliant with the company’s policies and regulations. In addition, it removes an administrative burden since required configuration profiles and applications are automatically deployed to enrolled devices.
With more oversight and less labor, you can spend time working on other mission-critical or time-sensitive IT issues for your organization.
Latest posts by Esa Hietikko (see all)
- Best Practices for Ensuring Patch Compliance - 03.01.2018
- Best Practices for Optimizing Patch Management Performance - 03.01.2018
- UnifiedPOS simplifies POS systems management - 13.11.2017