简体繁体 English

支持MDM的移动应用程序能否在未在MDM上运行的设备上工作

[英]Can a mobile app which supports an MDM work on devices which do not run on MDMs

原文 2017-01-12 13:58:50 2 2 android/ ios/ windows-phone/ enterprise/ mdm

Can a mobile app built with an MDM integration (Mobile Device Management solution ie Maas360, Airwatch, etc.), work on some other devices which are not enrolled in that MDM? 使用MDM集成构建的移动应用程序（移动设备管理解决方案，即Maas360，Airwatch等）可以在未注册该MDM的其他某些设备上运行吗？ Does this depend on which MDM in particular? 这是否特别取决于哪个MDM？

2 个解决方案

Yes, the app can work outside of MDM (unless you use a legacy app-wrapping techniques, not commonly implemented today, eg Knox v1 app signing service). 是的，该应用程序可以在MDM之外运行（除非您使用传统的应用程序包装技术，例如Knox v1应用程序签名服务，这种技术目前并不常见）。

Important: while the app will work, the features that rely on MDM need to be coded in such a way so they gracefully fallback when MDM is not available (eg prompt for user input or disable features) 重要提示：在应用正常运行的同时，需要对依赖MDM的功能进行编码，以便在MDM不可用时（例如提示用户输入或禁用功能）优雅地回退

I think maybe the distinction between MDM and MAM will be useful to understanding the answer to this. 我认为也许MDM和MAM之间的区别将有助于理解答案。

An MDM is typically a system where devices are enrolled in control by a central server. MDM通常是一个由中央服务器注册设备控制权的系统。 The exact mechanism of this varies between iOS and Android and it's important to note that an iOS device can be enrolled in only one MDM system while an Android device an be part of many. 确切的机制在iOS和Android之间有所不同，需要特别注意的是，iOS设备只能在一个MDM系统中注册，而Android设备是其中的一部分。

MAM is broadly speaking adding administrative controls to an app, usually by way of inclusion of an SDK and often using a secondary app to provide things like authentication services by way of custom protocols and other forms of inter-app communication. 从广义上讲，MAM通常是通过包含SDK的方式向应用程序添加管理控制，并且通常使用辅助应用程序通过自定义协议和其他形式的应用程序间通信来提供身份验证服务。

Many systems support a blend of these two approaches so the distinction can become a bit blurred. 许多系统支持这两种方法的混合，因此区别可能会变得有点模糊。