Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
en:mobile:setup:device_side:prep_device [2020/02/13 00:28] – [Preparing the device] lou_lomas | en:mobile:setup:device_side:prep_device [2020/12/23 20:31] – rowena | ||
---|---|---|---|
Line 3: | Line 3: | ||
**Preparing the device involves: | **Preparing the device involves: | ||
- | * **[[en: | + | * **[[en: |
- | * **[[en: | + | * **[[en: |
- | * **[[en: | + | |
- | * **[[en: | + | |
- | * **[[en: | + | |
==== Initial Android device power up ==== | ==== Initial Android device power up ==== | ||
Line 19: | Line 17: | ||
</ | </ | ||
- | - Power up the device | ||
- | - You should see a **Welcome!** screen where you will be asked for a language. | ||
- | - You should be prompted to connect to a **Wi-Fi** network. | ||
- | - You should be prompted to accept Terms and Conditions. | ||
- | - You should be prompted to accept a number of **Google services**: | ||
- | - **Use Google' | ||
- | - **Improve location accuracy**: | ||
- | - **Send system data**: | ||
- | - Because you have not connected to Wi-Fi, you should be prompted to set the **Date & time**: | ||
- | - You may be prompted to provide a **Name**, or sometimes **First** and **Last** name. Do <wrap em> | ||
- | Take care: Your device will likely try to autocorrect your spelling! | ||
- | </ | ||
- | - You should be prompted to select a **Lock type**. | ||
- | - You should be prompted to **Secure startup**. | ||
- | - You should be prompted to **Set PIN**. | ||
- | - You should be prompted to set **Notifications**. | ||
- | - You should be prompted to create a **Samsung account** (obviously will be different for other branded devices). | ||
- | - You may be prompted to confirm that you wish to **Skip Samsung account setup? | ||
- | - You may be prompted to configure **More useful features**. | ||
- | ==== Android tweaks | + | ==== Install Manage Engine-Mobile Device Management |
+ | Manage Engine-Mobile Device Management (ME-MDM) is used to remotely manage the Android devices running mSupply Mobile around the world. | ||
+ | * ME-MDM allows remote management of the device. Using ME-MDM we can install, update and uninstall software, track the location of lost devices and wipe the contents of the devices remotely. | ||
+ | * This means only the applications (mSupply, Telegram, Gmail, etc.) will be shown on the home screen and all other functions of the tablet are locked down. | ||
+ | Once ME-MDM is installed on the device, considerable control over the device is possible including remotely deploying, installing and executing apps. | ||
+ | There is [[https:// | ||
- | There are a number of tweaks that are worth applying before proceeding further: | + | <WRAP center round important 550px> |
- | === Screen timeout === | + | Requirements |
- | | + | |
+ | | ||
+ | </WRAP> | ||
- | === Turn off ' | ||
- | For ease of use of the touch-screen keyboard it' | + | === Terminology === |
- | * Samsung devices: | + | * **DEVICES** are enrolled to the MDM. |
+ | * Devices are assigned to **GROUPS**. You may need to configure additional groups if there will be more than one type of device installed in the system (that requires different profiles or apps). It is also recommended to have a Beta tester group of just one device which can then be used to verify that a software upgrade actually works properly. | ||
+ | * **USERS** are assigned | ||
+ | * **PROFILES** (security, Kiosk, etc.) are associated with Groups | ||
+ | * **APPS** are stored in the App Repository and distributed to Groups (profiles can also be associated with devices – however, this is not recommended) | ||
- | === Device updates === | ||
- | As soon as your device accesses the internet, it will likely try to update software. | ||
- | - All brand bloatware (Samsung / Lenovo / etc.) | ||
- | - All MS Office applications | ||
- | - All Google applications | ||
- | * **Settings > Software update > Download updates automatically** | ||
- | === Allow apps to be installed from local sources === | ||
- | * **Settings > Lock screen and security > Unknown sources**: | ||
- | === Enable Knox security (necessary for Sure MDM management - see below) === | ||
- | * **Settings > Device maintenance > Device security** Accept the prompted permissions request | ||
- | * **Knox active protection**: | ||
- | - You may be prompted for various services by the pre-installed apps. Ignore / defer / deny all of these.<WRAP center round important 60%> | + | <WRAP center round tip 550px> To record asset tags with sites, it is necessary to maintain a small database external to ME-MDM. |
- | At this point, the device will try and update its apps. | + | Note: that once the phone number is stored in ME-MDM, the external database only needs to record: |
+ | * Device serial number | ||
+ | * Device name | ||
</ | </ | ||
- | - Turn off the manufacturer' | ||
- | - **Apps > Samsung > Galaxy Store > Settings (top right menu) > Auto update apps > Never**. | ||
- | - Turn '' | ||
- | - Turn '' | ||
- | |||
- | - Enter the credentials for a local Wi-Fi network, then tap **NEXT**. | ||
- | |||
- | |||
- | === Security PIN code for SIM card === | ||
- | |||
- | To prevent the SIM card being removed to be used on another device, it is a good idea to [[https:// | ||
- | |||
- | ==== Install device remote management apps ==== | + | === Installation |
+ | - Charge and label the device. | ||
+ | - If the battery level is low, take this opportunity to put the device on charge. | ||
+ | - Make sure the device is labelled and serial number recorded. | ||
+ | - If the device has been used before, complete a **factory reset** for the device. | ||
+ | - If the device has a SIM, ensure that the SIM is functional, with sufficient data, etc. If the devices don’t have their own SIM, ensure that you have the best WiFi connection possible. Three modes are possible in order of preference: | ||
+ | - **Open WiFi**: | ||
+ | - **Pre-configure WiFi AP in the QR code**: | ||
+ | - **Manual configuration**: | ||
+ | - Enrol the device with ME-MDM. | ||
+ | - If the device is Android 9 or above: | ||
+ | - Obtain QR code (generated from ME-MDM: remember to select Android 9 code) for enrolling. | ||
+ | - Tap six times on the screen and, after allowing access to the camera, scan QR code. | ||
+ | - Ordered List ItemIf the device is Android 6 to 9: | ||
+ | - Obtain QR code for ME-MDM registration. | ||
+ | - On the google accounts page, enter the username '' | ||
+ | - Open (or download) a QR code scanner when prompted. | ||
+ | - Scan the QR code. | ||
+ | - If necessary, enter the WiFi credentials. | ||
+ | - Notify ME-MDM admin of the following and request they **Complete enrolment on the ME-MDM Admin Console**. | ||
+ | - device site name | ||
+ | - device serial number | ||
+ | - Once enrolment has been completed, profiles and apps (including mSupply mobile) will be pushed to the device through ME-MDM. | ||
- | As of 2019-10-15, the apps SureLock and SureMDM are used to remotely manage the Android devices running mSupply Mobile around the world. | ||
- | * **[[https:// | + | You can find the latest version of open source mSupply Mobile |
- | * [[https:// | + | |
- | == Management using SureMDM == | + | We recommend that you use TeamViewer and Telegram |
- | Once SureMDM is installed | + | |
- | This control is generally managed through SureMDM [[https:// | + | === Configure TeamViewer === |
+ | - Launch TV and accept permission requests. | ||
+ | - Once TeamViewer has been configured | ||
+ | - In the properties | ||
- | ==== Install mSupply Mobile ==== | ||
- | **[[https:// | ||
- | ==== Install other apps ==== | + | === Configure Telegram |
- | {{page> | + | Launch Telegram |
- | **The following apps (or equivalent) should be included: | + | |
- | * Calculator - use the device' | + | |
- | * Wi-Fi centre - use the device' | + | |
- | * For communication between sites and with support workers: | + | |
- | * Instant messaging - we recommend [[https:// | + | |
- | * Email - set up the device email app with an email address for the site/device (not the operator). | + | |
- | While apps can be installed remotely using a SureMDM job, it may be more convenient | + | The following section highlights the key steps for initialising mSupply Mobile once it has been pushed |
\\ | \\ | ||
\\ | \\ | ||
- | | //Return to: **[[en: | + | | //Return to: **[[en: |