Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:mobile:setup:device_side:prep_device [2020/12/23 20:29] – rowena | en:mobile:setup:device_side:prep_device [2021/04/28 00:33] (current) – Mark Glover | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== Preparing the device ===== | ====== Preparing the device ===== | ||
- | **Preparing the device | + | Preparing the device for mSupply is very dependant |
- | * **[[en: | + | * The make of the device |
- | * **[[en: | + | * The version of Android |
- | + | * The details | |
- | + | ||
- | ==== Initial Android device power up ==== | + | |
- | + | ||
- | <WRAP center round info> | + | |
- | * It is virtually impossible to prevent a modern Android device which is connected to the internet from doing at least some software updates. | + | |
- | * If possible, it is worth preventing these updates from occurring over slow and expensive cellular data connections. | + | |
- | * Therefore, it is recommended to connect the device to a (lower cost and faster) internet connected Wi-Fi network at the time of initial device power up and allowing OS updates and mSupply installation. | + | |
- | * Once this process is complete, the device can then use its cellular data connection | + | |
- | * Each new version of Android and the branded OS introduce changes to the menu structure. | + | |
- | </ | + | |
- | + | ||
- | + | ||
- | ==== Install Manage Engine-Mobile Device Management ==== | + | |
- | Manage Engine-Mobile Device Management (ME-MDM) | + | |
- | * 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 | + | |
- | There is [[https:// | + | |
- | + | ||
- | <WRAP center round important 550px> | + | |
- | Requirements | + | |
- | * Mobile device is Android 6.0+ | + | |
- | * Mobile device is using the EMM token (QR code) enrolment method | + | |
- | </ | + | |
- | + | ||
- | + | ||
- | === Terminology === | + | |
- | * **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 | + | |
- | * **USERS** are assigned to devices. All devices will be assigned to the same ‘system’ user for this ME-MDM ‘Customer’ account. | + | |
- | * **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) | + | |
- | + | ||
- | + | ||
- | <WRAP center round tip 550px> To record asset tags with sites, it is necessary to maintain a small database external to ME-MDM. | + | |
- | Note: that once the phone number is stored in ME-MDM, the external database only needs to record: | + | |
- | * Device serial number | + | |
- | * Device name | + | |
- | </ | + | |
- | + | ||
- | === Installation === | + | |
- | - Charge and label the device. | + | |
- | - If the battery level is low, take this opportunity to put the device | + | |
- | - 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 | + | |
- | + | ||
- | + | ||
- | === Install mSupply Mobile === | + | |
- | **[[https:// | + | |
- | + | ||
- | + | ||
- | We recommend that you use TeamViewer | + | |
- | + | ||
- | === Configure TeamViewer === | + | |
- | - Launch TV and accept permission requests. | + | |
- | - Once TeamViewer has been configured on the device, find the device based on the serial number. | + | |
- | - In the properties of the entry, change the ‘Alias’ to the Device site name. | + | |
- | + | ||
- | + | ||
- | === Configure Telegram === | + | |
- | Launch Telegram and configure as desired. | + | |
- | + | ||
- | The following section highlights the key steps for initialising mSupply Mobile once it has been pushed to the device through ME-MDM. | + | |
+ | Please consult with Sustainable Solutions ( < | ||
\\ | \\ | ||
\\ | \\ | ||
| //Return to: **[[en: | | //Return to: **[[en: |