Differences

This shows you the differences between two versions of the page.

--- en:mobile:setup:device_side:prep_device [2020/12/23 20:27] – Updated from ME-MDM rowena
+++ en:mobile:setup:device_side:prep_device [2021/04/28 00:27] – [Preparing the device] Mark Glover
@@ Line 2: / Line 2: @@
 ====== Preparing the device =====
-**Preparing the device involves:**
+Preparing the device for mSupply is very dependant on factors including:
-  * **[[en:mobile:setup:device_side:prep_device#initial_android_device_power_up|Initial Android device power up]]**
+  * The make of the device
-  * **[[en:mobile:setup:device_side:prep_device#Install_Manage_Engine-Mobile_Device_Management|Install Manage Engine-Mobile Device Management]]**
+  * The version of Android running on it
-  * **[[en:mobile:setup:device_side:prep_device#install_device_remote_management_apps|Install device remote management]]**
+  * The details of how the organisation plans to manage devices and communicate with users
-  * **[[en:mobile:setup:device_side:prep_device#install_msupply_mobile|Install mSupply Mobile]]**
-  * **[[en:mobile:setup:device_side:prep_device#install_other_apps|Install other apps]]**
+Please consult with Sustainable Solutions on this.
 ==== Initial Android device power up ====
@@ Line 38: / Line 39: @@
   * 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.  ME-MDM has a good system of marking newly upgraded software as Beta, and then approving it for release after testing.
   * **USERS** are assigned to devices. All devices will be assigned to the same ‘system’ user for this ME-MDM ‘Customer’ account.  This user will need to be created in ME-MDM. The user must have the same email address that is used to set up Android for Work (AfW) / Managed Google Play when initially configuring the user’s account.
-  * **PROFILES** (security, Kiosk, etc.) are associated with Groups
+  * **PROFILES** (Restrictions, Kiosk, EFRP, etc.) are associated with Groups (or devices - not recommended)
-  * **APPS** are stored in the App Repository and distributed to Groups (profiles can also be associated with devices – however, this is not recommended)
+  * **APPS** are stored in the App Repository and distributed to Groups (or devices - 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.  This may be done using a spreadsheet or similar.
+<WRAP center round tip 60%> To record asset tags with sites, it is necessary to maintain a small database external to ME-MDM.  This may be done using a spreadsheet or similar.
-Note: that once the phone number is stored in ME-MDM, the external database only needs to record:
   * Device serial number
   * Device name
+  * Asset tag
+  * Phone (SIM) number
+Note: If you succeed in transferring the phone number on to the SIM card, it will be automatically stored in ME-MDM, and does not need to be stored in the external database.
 </WRAP>
@@ Line 72: / Line 76: @@
   - Once enrolment has been completed, profiles and apps (including mSupply mobile) will be pushed to the device through ME-MDM.
-We recommend that you use TeamViewer and Telegram on the mobiles to aid with support.   They can also be pushed through ME-MDM and configured as below.
+You can find the latest version of open source mSupply Mobile **[[https://github.com/openmsupply/mobile/releases|here]]**.\\
+We recommend that you use TeamViewer and Telegram on the devices to aid with support.   They can also be pushed through ME-MDM and configured as below.\\
 === 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.
+  - In the properties of the entry, change the ‘Alias’ to the Device site name.\\
@@ Line 85: / Line 91: @@
 The following section highlights the key steps for initialising mSupply Mobile once it has been pushed to the device through ME-MDM.
-==== Install mSupply Mobile ====
-**[[https://github.com/openmsupply/mobile/releases|Download open source mSupply Mobile from GitHub]]**
-==== Install other apps ====
-{{page>en:mobile:setup:device_side#&nodate&nouser}}
-**The following apps (or equivalent) should be included:**
-  * Calculator - use the device's calculator
-  * Wi-Fi centre - use the device's Wi-Fi control
-  * For communication between sites and with support workers:
-    * Instant messaging - we recommend [[https://play.google.com/store/apps/details?id=org.telegram.messenger|Telegram]].  Use the devices's SIM phone number, (not the operator)
-    * Email - set up the device email app with an email address for the site/device (not the operator).  We recommend Gmail.
-While apps can be installed remotely using a SureMDM job, it may be more convenient to install them manually from a PC at the same time as installing the SureMDM and SureLock apps.