9,275
edits
Join the Power Platform Masterclass #2 starting April 23
Mobile device management: Difference between revisions
Jump to navigation
Jump to search
→Third-party MDM providers
| Line 13: | Line 13: | ||
MDM also adds another layer to the complexity of the update and change management. See [[Best_practices_for_upgrading_Resco_software#MDM|best practices for upgrading Resco apps]] for more information. | MDM also adds another layer to the complexity of the update and change management. See [[Best_practices_for_upgrading_Resco_software#MDM|best practices for upgrading Resco apps]] for more information. | ||
Essentially, there are two main scenarios for MDM: | |||
* Distribution | |||
* Security | |||
=== App distribution === | |||
The main motivators for centralized distribution are: | |||
* manage the version that users have installed | |||
* block access to the app store for security reasons | |||
For example, if you have a custom JavaScript solution that you have meticulously tested with a certain version of the app or a finetuned custom integration solution, you might decide to skip some releases so that you don't have to test everything anew. However, in order to be eligible for Resco support, you need to update your app at least once a year. Also, the operating systems on mobile devices should be kept up to date at least once a year. | |||
If you want to use MDM for centralized distribution of the app on a larger number of devices, this should not be a problem. Resco support team has been able to help with any requested MDM solution. In this scenario, the MDM provider should request a custom version of the Resco app, either as an IPA file (iOS) or APK/AAB file (Android). Resco support will provide a version of the app ready to be signed by the customer's provisioning profile and certificate. | |||
We have received reports from our customers, that in the case of iOS, many have successfully used the app store version of the app for distribution - no need for a custom installation file from Resco. However, we are happy to provide such custom files if needed. Contact Resco support for more information. | |||
=== Security === | |||
In the case of security, the situation can be more complicated. The common use cases for security features of MDM include: | |||
* Using key-value pairs for prefill URL, name, or even password of the CRM | |||
* Setting up Exchange or SharePoint access | |||
* Restricting the communication between the managed Resco app and non-managed apps | |||
* Blocking features like copy/paste, taking screenshots, and much more. | |||
{{Note|Keep in mind that if you block email clients, the app cannot send a log file to the support email address.|Warning}} | |||
The process is the same as for distribution - you need a custom IPA/APK/AAB file. However, in this case, the MDM needs to add their custom wrapper for our app. The exact procedure depends on the MDM, often, this is a website where you upload the app to receive a wrapped version, or there is a program for that. In some cases, a wrapped iOS app needs to be re-signed; sometimes this is done by the wrapping process. The customer and their MDM provider are responsible for the wrapping - Resco support is ready for consultations. | |||
A different option is to use SDK. The MDM provider gives us their SDK and we have to integrate it into our app. However, this approach is generally discouraged: the SDK is a black box from our point of view and we cannot predict how the code will react, because we use Xamarin. We recommend using key-value pairs in the case of iOS. | |||
For Android and Windows Store versions, we do have an app with integrated Intune SDK that we can build on-demand, without the need for wrapping (in theory, as the MDM requirements can change any time). | |||