This user manual has been developed to guide the NIMC super admin to set up their devices on the Enrolment Mobile Device Management System (EMDMS). The guide will be broken into 2 phasessections.

1. Onboarding devices on the EMDMS.

2. Enforcing compliance Managing devices on the EMDMS admin portal.

ONBOARDING DEVICES ON THE EMDMS

\uD83D\uDCD8 Instructions

To onboard devices on the EMDMS portal, follow these steps;

1. Login to the EMDMS admin portal on https://nimc-emdms.seamfix.com/smartmdm/ with these test credentials.

   Username - haguonye@seamfix

   .

   comPassword - Aa123456@

...

Fig1: Enter valid Login credentials to access the portal

...

1. The QR Code method

2. The apk file download method.

The QR Code Method

...

1. For a new new device,

   1. Turn on the device

   2. On the Get started page (the page where you’d be required to set up your language preference & email), don’t click on “start” rather tap on the page about 6 times consequitively to launch the QR scanner

2. For a device already in use,

   1. Factory reset the device

   2. On the Get started page (the page where you’d be required to set up your language preference & email), don’t click on “start” rather tap on the page about 6 times consecutively to launch the QR scanner

...

• On the apps menu on the app, the user will be able to view the apps on the device including those installed & those pending installation

...

MANAGING DEVICES ON THE EMDMS

The EMDMS Dashboard -

This module shows basic analytics of all the activities happening within the ecosystem. This is a dynamic module so the analytics displayed on this page is configurable. To access the dashboard, follow these steps;

...

The EMDMS Device Locator -

The EMDMS device locator shows the distribution of devices across the different locations on a map view. To access the module;

1. Login with valid credentials

2. Navigate to the EMDMS Device Locator

3. On the map view, look for the location where the device is being used, Click on the location icon to view more details about the device

...

...

The EMDMS user Fig. 21: Showing device location across their various locations on a map.

EMDMS Users -

The EMDMS user module enables the admin to create users on the EMDMS portal and assign them roles. There are basically two roles on the EMDMS portal. The Admin role & the agent role. Only the admin users can access the EMDMS portal and perform device management functions. The agent users on the other hand only have access to their assigned devices.

EMDMS Policies -

policies contain a set of restrictions that the IT admin can apply to devices to enforce compliance. To access policies,

1. Login with valid credentials

2. Select EMDMS policies

3. From the list of policies, select policies to apply to specific devices.

4. Select the devices tab

5. Check the devices to map to the policy

6. Select the “confirm” button to apply the selection.

...

Fig. 22: Showing the list of available policies on the portal

Geofencing -

Geofences are the locations listed as part of the

\uD83D\uDCCB Related articles

Filter by label (Content by label)showLabelsfalsemax5spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@12996sortmodifiedshowSpacefalsereversetruetypepagecqllabel = "kb-how-to-article" and type = "page" and space = "MDM"labelskb-how-to-articlefor a device(s) at the point of activation. These locations are not created on the EMDMS portal. Once a device is successfully onboarded on the EMDMS, the location assigned to that device will be displayed on the EMDMS “Geofences” policy. To access the listed geofences, follow these steps

1. Login to the EMDMS portal

2. Navigate to EMDMS policies

3. Select “Geofences” from the list of policies displayed (see Fig. 22 above). The admin will be able to view all the geofences available within the ecosystem.

...

Fig. 23: showing all geofeneces with their corresponding coordinates

It is not enough to retrieve the geofences. It needs to be enforced. Enforcing a geofence means that users within that location will not be able to perform any actions on their devices for the period of the geofence action.

The following policies must be applied to your devices before geofence can be enforced.

1. Enable Location Tracking

2. Enforce Location tracking

3. Enforce Geofence

Geofence Blacklist -

This feature enables the admin to be able to blacklist an entire geofence. To achieve this follow these steps;

1. Login to the portal,

2. Navigate to the EMDMS policies module (see Fig. 22)

3. Select “Geofences” from the list of policies

4. Select the location you intend to blacklist from the options displayed (see Fig. 23)

5. Click the “actions” icon by the location of your choice and select the option “blacklist (see Fig. 24 below)

...

Fig. 24a: Showing the “blacklist” geofence option

...

Fig. 24b: Device locked due to blacklisted geofence

Geofence Waiver

Geofence waiver can be used when an admin decides that despite the initial geofence assigned to a device, they want the user to be able to use the device in a new location which is not the user’s original geofence for a while. To apply the waiver policy, follow these steps;

1. Login to the portal

2. Navigate to Policies

3. Select the “Geofence Waiver” policy from the list of policies displayed (see fig. 22 above). If you have created waiver locations, the list of locations that you have created will be displayed on the geofence waiver page. Otherwise, you will be required to create a new location.

   1. Enter the correct Latitude & the Longitude coordinates location & click save geofence (see fig. 25)

   2. The new location will be displayed on the table as a list of geofence locations

4. To apply the location to a device,

   1. Navigate to actions,

   2. select the “apply to devices” option (see fig. 26)

   3. select how long you want this device to be usable in this new location (see fig. 27)

...

Fig. 25: Enter coordinates (lat & long)

...

Fig. 26: Geofence waiver locations

...

Fig. 27: Select the duration of the waiver

Applications Management

The applications management module enables the admin to be able to manage applications usage & transfer within the NIMC ecosystem. amongst other things, you’d be able to

• Blacklist an unauthorized app

• Uninstall an unauthorized app

• Add a new app version and push the upgrade via OTA (Over-the-air) app upgrade

• Monitor the app usage including - total data consumed, screentime spent on an app.

Add a new app

To add a new app, follow these steps;

1. Navigate to the Applications Management module

2. Click on the “Add new app” button

...

Fig. 28: Add a new app

3. Fill out the form with the correct details

...

Fig. 29. Add details of the new app

Add a new app version

This can be used to update an app version. To add a new version, follow the steps below;

1. Navigate to the applications management module

2. From the list of apps, select the app version to update

   1. Select action > add a new app version (see fig. 30) below

...

Fig. 30: Add a new app version

3. fill out the new app version page

...

Fig. 31: Fill out the form to add a new app version

Where an app has more than one version, it will be listed on the app versions page. see fig.32 below

...

Fig. 32: List of all available app versions

App rollout via OTA

To roll out a new app version to the field, follow these steps;

1. Select the app name on the Apps bank page (fig. 28)

2. Click on actions (fig.30) and select edit app details

3. From the available app versions, select the app version to roll out (see fig.33)

...

Fig. 33: Roll out the new version by selecting “map to devices”

4. select a list of devices or a device group to map the app to

...

Fig. 34: select the devices to map the app version to

Blacklist an unauthorized app

To backlist an unauthorized app follow these steps;

1. Select the app name on the Apps bank page (fig. 28)

2. Click on actions (fig.30) and select the “blacklist app” option

3. select the device(s) or the group of devices that the app should be blacklisted on see fig.35

...

Fig. 35: select the devices to blacklist the app on

Device Monitoring

The EMDMS portal provides the capability for the admin to manage the heartbeat details on the device. Find below the details of the hearbeat page.

...

Fig 36: device heartbeat page

...

Fig. 37: device heartbeat page

...

P.S:

1. By default, Android devices are set to use the same password for work & personal profiles

   1. Users have the opportunity to set a new password in the work profile. This will override the password set in the personal profile.

2. If the password set for the personal profile does not meet the minimum password requirement set by the admin for the work profile, the user will not be able to access the work profile

3. Users cannot use screen lock or pattern. They must use a password.

4. The EMDMS app needs to finish downloading before the user can navigate away from the page that shows apps mapped by the admin

5. The user will be notified that the work profile setup is in progress.