Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
en:mobile:setup:device_side:prep_device [2020/12/23 20:31] rowenaen: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 =====
  
-**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 
 +  * The details of how the organisation plans to manage devices and communicate with users 
 + 
 +Please consult with Sustainable Solutions on this.
  
  
Line 36: 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.   * 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.   * **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 serial number
   * Device name   * 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> </WRAP>
  
  • en/mobile/setup/device_side/prep_device.txt
  • Last modified: 2021/04/28 00:33
  • by Mark Glover