Difference between revisions of "Information Systems:MobiControl"
m |
|||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Overview= |
=Overview= |
||
| − | MobiControl is MDM (Mobile Device Management) software that was |
+ | MobiControl is an MDM (Mobile Device Management) software that was purchased for the centralized management of the RF guns used in the [[:Category:Distribution Centre | Distribution Centre]]. The software makes it possible to configure, monitor and manage all 37 RF guns in a consistent and automated fashion. Prior to MobiControl, each RF gun had to be configured independently. All were found to have different versions of the OS as well as the TekTerm program, and thus all would behave differently, making them hard to manage collectively. MobiControl also has remote control / screen-sharing capabilites for the RF guns, similar to Techinline/Fixme.IT for desktops. |
| − | As of August 2016, MobiControl device agents were also installed on the 8 new laptops purchased for select staff ([[Information Systems: Evergreen Project | |
+ | As of August 2016, MobiControl device agents were also installed on the 8 new laptops purchased for select staff ([[Information Systems: Evergreen Project |see Evergreen project]]). |
| − | MobiControl is software that is meant to manage mobile devices of all sorts, but it was acquired primarily for management of the RF guns. In fact, the company (SOTI Inc.) has its roots in Psion; MobiControl was once known as Mobile Control Center (MCC), |
+ | History note: MobiControl is software that is meant to manage mobile devices of all sorts, but it was acquired primarily for management of the RF guns. In fact, the company (SOTI Inc.) has its roots in Psion; MobiControl was once known as Mobile Control Center (MCC), a software offering by Psion. It was presumably purchased by SOTI. |
| − | |||
| ⚫ | While MobiControl |
||
This page attempts to detail as best possible all the work that has been done with MobiControl at uniPHARM. |
This page attempts to detail as best possible all the work that has been done with MobiControl at uniPHARM. |
||
| + | =MobiControl= |
||
| − | =Administration overview= |
||
| + | MobiControl is installed on [[Information Systems:Smithers | SMITHERS]]. |
||
| + | |||
| ⚫ | |||
| + | Access: [https://smithers.unipharm.local/MobiControl/ Web GUI] |
||
| + | |||
| ⚫ | |||
| + | |||
| + | ==Managing RF guns with MobiControl== |
||
| + | |||
| + | For a more thorough understanding of the value MobiControl presents to the management of RF guns, it may be worth first understanding how our particular model of RF gun works. [[Information Systems:Workabout Pro G2 7527C |Read this article for more.]] |
||
| + | |||
| ⚫ | While MobiControl makes it easier to manage devices, the fact that the RF guns run Windows CE means that most custom configuration has to be done through registry changes. (True mobile platforms such as Android/iOS are much easier to manage, and each new version of MobiControl is geared more and more towards management of those platforms.) |
||
| ⚫ | MobiControl Package Studio can be downloaded from the web interface. The management of devices is done through packages. In the context of the RF guns, a packageDevice configuration is consistent across all RF devices and comprise 4 main MobiControl packages. That is, 4 MobiControl packages contain the payloads that take a device from stock Windows CE to a state ready to deploy into the Distribution Centre: |
||
| ⚫ | |||
| ⚫ | |||
| − | ==Device configuration== |
||
| ⚫ | |||
* uRF Initial Package - configures wireless and installs the MobiControl device agent (not visible when viewing installed packages as this is not a persistent package, rather it's purpose is to get wireless configured and MobiControl installed on the device so that it can talk to the server) |
* uRF Initial Package - configures wireless and installs the MobiControl device agent (not visible when viewing installed packages as this is not a persistent package, rather it's purpose is to get wireless configured and MobiControl installed on the device so that it can talk to the server) |
||
| Line 22: | Line 29: | ||
* MSI Info Package for CE5 - reports Psion-proprietary device stats; this package doesn't do much and is pretty unimportant |
* MSI Info Package for CE5 - reports Psion-proprietary device stats; this package doesn't do much and is pretty unimportant |
||
| − | The first 3 packages are critical. See [[Information Systems:RF configuration / Standard deployment package | RF configuration / Standard deployment package]] for more information about their contents. |
+ | The first 3 packages are critical. See [[Information Systems:RF configuration / Standard deployment package | RF configuration / Standard deployment package]] for more information about their contents. |
==Packages== |
==Packages== |
||
Latest revision as of 11:44, 9 August 2017
Overview
MobiControl is an MDM (Mobile Device Management) software that was purchased for the centralized management of the RF guns used in the Distribution Centre. The software makes it possible to configure, monitor and manage all 37 RF guns in a consistent and automated fashion. Prior to MobiControl, each RF gun had to be configured independently. All were found to have different versions of the OS as well as the TekTerm program, and thus all would behave differently, making them hard to manage collectively. MobiControl also has remote control / screen-sharing capabilites for the RF guns, similar to Techinline/Fixme.IT for desktops.
As of August 2016, MobiControl device agents were also installed on the 8 new laptops purchased for select staff (see Evergreen project).
History note: MobiControl is software that is meant to manage mobile devices of all sorts, but it was acquired primarily for management of the RF guns. In fact, the company (SOTI Inc.) has its roots in Psion; MobiControl was once known as Mobile Control Center (MCC), a software offering by Psion. It was presumably purchased by SOTI.
This page attempts to detail as best possible all the work that has been done with MobiControl at uniPHARM.
MobiControl
MobiControl is installed on SMITHERS.
Logging in to the web GUI
Access: Web GUI
MobiControl is configured for AD/LDAP authentication (connected to UWDDC3, so log in with your Windows credentials.
Managing RF guns with MobiControl
For a more thorough understanding of the value MobiControl presents to the management of RF guns, it may be worth first understanding how our particular model of RF gun works. Read this article for more.
While MobiControl makes it easier to manage devices, the fact that the RF guns run Windows CE means that most custom configuration has to be done through registry changes. (True mobile platforms such as Android/iOS are much easier to manage, and each new version of MobiControl is geared more and more towards management of those platforms.)
MobiControl Package Studio can be downloaded from the web interface. The management of devices is done through packages. In the context of the RF guns, a packageDevice configuration is consistent across all RF devices and comprise 4 main MobiControl packages. That is, 4 MobiControl packages contain the payloads that take a device from stock Windows CE to a state ready to deploy into the Distribution Centre:
- uRF Initial Package - configures wireless and installs the MobiControl device agent (not visible when viewing installed packages as this is not a persistent package, rather it's purpose is to get wireless configured and MobiControl installed on the device so that it can talk to the server)
- uRF Main Package - contains registry settings to customize the device (device sounds, power management etc.)
- Install TekTerm8 and Configure Settings - installs the TekTerm terminal emulation program
- MSI Info Package for CE5 - reports Psion-proprietary device stats; this package doesn't do much and is pretty unimportant
The first 3 packages are critical. See RF configuration / Standard deployment package for more information about their contents.
Packages
Packages are what are deployed to devices to deliver settings, files, or scripts.
Rules
Packages are governed by device rules - rules specify how, when, and to what devices packages apply to. There must also exist an Add Device rule for each type of device added to MobiControl that corresponds to the device agent for that device, so that MobiControl will know how to group the device (and hence which packages apply).