1) Which features does an MDM need?
Once you have decided to implement an MDM (Mobile Device Management System) in your company, there is still the question of which product to choose.
If you look around in common forums, the same products are often recommended. Among them are often big companies like Relution, AppTec or Microsoft Intune. This almost gives the impression that these vendors offer a one-fits-all solution that can meet the needs of a wide variety of businesses.
True to the motto: using a sledgehammer to crack a nut, an abundance of functions, price models and different packages is supposed to suggest that the right one can be found for really every industry.
We are of the opinion that this is not the case. In principle, there are a certain number of functions and settings that a mobile device management system must have in order to be considered as such. These include, for example, the possibility to offer remote support, to send apps via mass command or to set up the single-app mode. In addition, there are various other functions that vary depending on how extensive the MDM program is.
Large providers often seem to offer the larger range of functions at first glance. This can be fine, of course, but can lead to the program becoming overloaded and difficult to learn. In addition, there may be numerous functions that you don't need at all. What other aspects to consider when deciding for or against an MDM can be found here: In search of an MDM?
The question you have to ask yourself is not: Which functions does the MDM need? But rather: What do I want to achieve with the MDM? You then have to specifically ask and try out whether this can be implemented.
2) What is an MDM license?
An MDM license is the permission to use the mobile device management system on a company's mobile devices, which is defined in a contract.
A separate MDM license is required for each device. This means that if you want to operate 150 devices in your company, you will also need 150 MDM licenses.
Essentially, almost all providers of Mobile Device Management have a license model with a basic price that covers the basic provision of the MDM. This price covers the 'maintenance costs', so to speak. Often, however, this does not include any, or only rudimentary, functions. In theory, for example, you could only log in but not install any apps, create user groups or assign policies. However, this is only for illustration. In practice, this is not how MDM is sold.
The licensing model has the advantage that it is common practice in the software-as-a-service world and therefore familiar to potential buyers. For providers, this also simplifies the sales process, because there is no need to explain how billing and the right of use are structured. The fact that the company always remains the owner of the software also means that updates and changes to the software can be made without further ado. The functionality and security of the software is thus ensured.