Free EditionWelcome to the ManageEngine Mobile Device Management FAQ Section. This resource is designed to assist you in navigating and resolving common issues encountered during the management of your mobile devices. Our comprehensive solutions aim to address these challenges effectively.
If you encounter any issues that remain unresolved, please reach out to us via email, attaching the necessary log files. Our dedicated support team will promptly review your case and work with you to resolve the issues efficiently.
MDM Cloud is the SaaS version of the MDM On-Premises. With MDM Cloud, you only have to sign in using your Zoho account and start managing your devices. The data and server configuration is managed by Zoho. Whereas in case of the On-Premises, you have to install the application and configure network settings to setup MDM and manage devices.
Currently, the following software platforms are managed by MDM:
MDMP currently supports pgSQL and MS-SQL.
Yes, MDM supports migration from cloud to on-premises using our in-house migration tool.
Yes, we support migrating from the standalone version to the MSP version in case of cloud. Contact the MDM cloud support team (mdmcloud-support@manageengine.com) for further details.
MDM provides you with a 30-day trial of the Professional Edition, where you can manage unlimited devices and add unlimited additional technicians. Once the 30-day trial expires, you can either extend you trial, purchase the product or move to Free edition. After trial expiry if you move to the Free edition, you are allowed to choose the devices(up to 25) that you want to manage. All the apps and profiles distributed to these devices as well as other configurations associated to the selected devices are retained. Free Edition is similar to Trial edition except that Free Edition allows a maximum 25 devices to be managed and no additional technicians can be added.
When trying to sign up, you encounter an error stating you are part of another organization such as "Access denied for this service. Please contact your Org (<org_name>) administrator [admin@org.com], it implies you are already a registered user as your organization has registered for Zoho Services. There is a super admin assigned for Zoho Services, who is the only who can sign up for any other Zoho service including MDM Cloud. If the super admin has signed up for Zoho services, you may request the super admin to add yourself as a technician to use MDM Cloud. In case you want to try MDM Cloud, you can use an alternate e-mail address to sign up and use the service. If you get redirected to https://mdm.manageengine.eu/enroll.do, then you may request the super admin to add yourself as a technician to use MDM Cloud.
In MDM cloud, the default storage will be 5GB. You can avail for additional storage with addons. Contact support for more info.
To delete you MDM account, go to the MDM web console and click on Admin tab from the top menu. Now, select Company Details and click on Delete Account. Follow the on-screen instructions to removed your MDM account.
Ensure that the following ports are open in the proxy/firewall. In addition to ports, ensure these domains are allowed in any proxy/firewall/third-party filters.
| Port Number | Type | Purpose | Connection | Traffic |
| 9020 | HTTP | ME MDM app and server communication. | Inbound to Server |   |
| 9383 | HTTPS | ME MDM App and server communication. | Inbound to Server | |
| 443 | HTTPS | Should be open on Mobile Device Manager Plus server to reach APN, FCM, WNS server. For Android devices: android.googleapis.com; www.google.com; android.clients.google.com; *.googleapis.com; play.google.com; google-analytics.com; googleusercontent.com; gstatic.com; *.gvt1.com; *ggpht.com; dl.google.com; accounts.google.com; gcm-http.googleapis.com; fcm.googleapis.com; fcm-xmpp.googleapis.com; pki.google.com; clients1.google.com; clients[2...6].google.com The following domains must be open, based on the country that the server is located in: Global: analytics.samsungknox.com; prod-knoxlog.secb2b.com; account.samsung.com; gslb.secb2b.com; gsl.samsunggsl.comUS : us-elm.secb2b.com; us-prod-klm-b2c.secb2b.com; us-prod-klm.secb2b.com; usprod-knoxlog.secb2b.com China : china-gslb.secb2b.com.cn; china-elm.secb2b.com.cn; china-b2c-klm.secb2b.com.cn; china-prod-klm.secb2b.com.cn; china-klm.secb2b.com.cn; china-segd-api.secb2b.com.cn; myknoxapk.blob.core.chinacloudapi.cn Asia, Africa, Europe, or other regions : eu-elm.secb2b.com; eu-prod-klm-b2c.secb2b.com; eu-prod-klm.secb2b.com; euprod-knoxlog.secb2b.com For Apple devices: albert.apple.com; captive.apple.com; gs.apple.com; humb.apple.com; static.ips.apple.com; tbsc.apple.com; *.push.apple.com; gdmf.apple.com; deviceenrollment.apple.com; deviceservices-external.apple.com; identity.apple.com; iprofiles.apple.com; mdmenrollment.apple.com; setup.icloud.com; vpp.itunes.apple.com; gg.apple.com; gnf-mdn.apple.com; gnf-mr.apple.com; gs.apple.com; ig.apple.com; mesu.apple.com; ns.itunes.apple.com; oscdn.apple.com; osrecovery.apple.com; skl.apple.com; swdist.apple.com; swdownload.apple.com; swscan.apple.com; updates.cdn-apple.com; xp.apple.com; *.itunes.apple.com; *.apps.apple.com; *.mzstatic.com; ppq.apple.com For a detailed list, refer to this document from Apple. For Windows devices: https://login.live.com; https://*.notify.windows.com These ports need to be opened to enable remote control/view with Zoho Assist. |
Outbound to Server | |
| 5223 | HTTPS | Should be open, if the mobile device connects to the internet through the corporate Wi-Fi, it is recommended to configure the IP in the range 17.0.0.0/8. | Outbound from Corporate Network Firewall | |
| 5228, 5229, 5230 | HTTPS | For FCM to reach the managed mobile device. Host address: https://android.com; play.google.com; android.clients.google.com; www.google.com; googleapis.com; android.googleapis.com; gstatic.com; google-analytics.com; googleusercontent.com; *.gvt1.com; *ggpht.com; dl.google.com; fcm.googleapis.com; fcm-xmpp.googleapis.com; gcm-http.googleapis.com; gcm-xmpp.googleapis.com As FCM doesn't provide specific IPs, you should allow your firewall to accept outgoing connections to all IP addresses contained in the IP blocks listed in Google's ASN of 15169. |
Outbound from Corporate Network Firewall | |
| 5235,5236 | HTTPS | For Firebase Cloud Messaging (eg. EMM-DPC communication). Host address: https://gcm-xmpp.googleapis.com; gcm-http.googleapis.com; android.googleapis.com | Outbound from Corporate Network Firewall | |
Also, ensure Mobile Device Manager Plus server has adequate permission(s) to contact the domains listed here.
TLS and TCP protocols are used for enrolling devices in MDM.
Both the MDM server and the device to be enrolled in MDM must have access to the following domains, which are to be excluded/allowed in firewall and/or any third-party filters.
To identify the domains which are not reachable by the MDM server, click here
The domains which the MDM server is unable to reach are specified within the product. To view the these domains, follow the given instructions
NOTE : Entering the domain URLs in the browser address bar does not provide the reachability of the same.
Ports such as 5223, 5228, 5229, and 5230 should be open if the mobile device connects to the internet through the corporate Wi-Fi. If the managed devices connect through the cellular data network, this requirement is not necessary (HTTPS port).
If account credentials of the admin are available, log into MDM Cloud and follow the steps given here to transfer the admin privilege to a new user. If the credentials are not available, contact MDM Support at mdmcloud-support@manageengine.com with either of the following:
Admins can transfer admin privileges directly from the MDM server in case they are changing their jobs or if the organization has purchased only one technician license. Refer this document for the steps to tranfer the MDM admin role to a different user.
The user's account might be configured as part of a different organization or the person is using other Zoho services. This can be resolved by deleting the account from the Zoho application and inviting the user to the right organization.
Note: Deleting the organization removes all the Zoho services which have been configured with this account. Zoho services being utilized for personal use, also get deleted. If the user is unsure about the services being used with the Zoho account or if the organizations need to be merged into one, contact MDM Cloud Support (mdmcloud-support@manageengine.com).
Please contact MDM Cloud Support (mdmcloud-support@manageengine.com).
In case you need to make a secondary e-mail address as primary, click on the mail icon present against the mail address. This makes the selected e-mail address as primary.
Ensure that the SCEP template reflects the same authentication values as configured in the Exchange server. Additionally, for the authentication to work, the client certificate must contain the user principal name(UPN) of the user in the certificate's subject or subject alternative name fields. Refer to this link for more details.
If client-based authentication is enabled in your organization's AD, you can configure the SCEP policy to ensure one-time login for the applications and services that depend on AD, like VPN, Wi-Fi, etc.
MDM secures the communication between the managed devices and the server using SSL certificates. Importing third party SSL certificates signed by a valid Certificate Authority secures the communication by encrypting it. Upon importing valid certificates, the user need not manually trust them while accessing the MDM server. The user can hence, securely access the server without the warning message.
All communication between MDM and mobile devices is encrypted using TLS 1.2 protocol and certificates issued by SHA 256, thereby ensuring data security.
Zoho Directory's sync tool can be used to sync directory services like Active Directory/Azure Directory with MDM, for features like self-enrollment, auto-user assignment, and others which involves the directory services.
Reason: This issue occurs when you have already integrated Google Workspace(G Suite AD) with MDM and you try to integrate it once again. This integration can either be with MDM on-prem or MDM cloud.
Solution:
The prerequisites for enrolling a mobile device are:
End user should have the following for self enrolling a device.
To transition a device from work profile mode to fully managed mode, the user must initiate the enrollment process from scratch. If the device was previously enrolled in work profile mode, a factory reset is necessary. Afterward, the user can enroll the device once again using the fully managed enrollment method.
User can view or execute actions on the enrolled devices from the Devices section within the Enrollment Tab, as well as from the Inventory Tab and Management Tab.
Yes, you can apply kiosk mode or lock down devices to selected apps for fully managed devices. You cannot apply Kiosk mode or block users from installing personal apps if the device is enrolled as a work profile.
To know more about kiosk mode, please refer to the Kiosk help page.
Remote wiping of a device is feasible only on fully managed devices, while devices enrolled in work profiles can only have the work profile removed, meaning full data wipe is not possible on such devices.
User can view the enrollment type of an enrolled device from the Devices section within the Enrollment Tab.
User can view the Management Method of an enrolled device by opening the Device details from the Devices section within the Inventory.
No, You need not re-enroll the managed mobile devices, because the mobile devices will reach the Mobile Device Manager Plus server using the external IP.
No, the devices need not be factory reset (unless specified otherwise) to be enrolled and managed by MDM.
The app size will differ from device to device based on the platform type, but on average, the app size will be around 25-30 MB upon installation. However, the app size will increase based on the profiles/documents distributed to the device as these documents and profiles are stored in the app.
ME MDM app consumes network data and battery only for downloading apps pushed to the device, with the data consumed depending on the size of the app. Other actions consume approximately 2 MB of network data monthly. Additionally, the consumption varies in case of geo-tracking based on the accuracy level specified.
If the device is CDMA activated, then the IMEI contains only 14 digits and is referred as MEID. You can check the IMEI of your device by dialing *#06#.
To avoid using invites, you can prefer Self Enrollment, where the users enroll the devices themselves and Admin enrollment. Admin enrollment as the name suggests, is a type of enrollment where the enrollment process is carried out by the Admin. The other advantage with Admin enrollment, is that the process is automated, requiring minimum user intervention and/or admin action. MDM supports the following types of Admin enrollment for Android:
The following types of Admin enrollment is supported in iOS:
Verify if Restricted Sign-in is disabled on the OneAuth app present on users' devices, even if you have not enabled two-factor authentication. If the issue is not still persists, contact MDM Cloud Support (mdmcloud-support@manageengine.com).
In case multiple teams(referred henceforth as org) in your enterprise use any Zoho service, follow the instructions specific to your scenario.
If this page is displayed when trying to enroll a device, ensure your accessing the appropriate enrollment URL from the device to be enrolled.
If this page is displayed when trying to access MDM Cloud, ensure your MDM Cloud admin has added you as a user.
Mobile Device Manager Plus allows the admins to modify the username and email address associated with enrolled devices without having to re-enroll the devices. To modify the associated credentials follow the steps given below:
Modifying the user details will reassign the account based profiles to the new email address.
If you are re-issuing managed devices to new users, you may want to erase all content while keeping the associated apps and profiles intact. To re-issue a managed device, it is recommended to deprovision the device which will wipe the device data and thus remove all the apps and policies associated with the device. After deprovisioning, you have to re-enroll the device before issuing them to employees to ensure that the device is pre-configured with all the requisite apps and policies.
You can make use of admin enrollment methods like Apple Business Manager (ABM) for iOS devices, Zero Touch Enrollment for Android devices or Knox Mobile Enrollment for Knox supported Samsung devices to enroll devices remotely. These methods ensure that the device gets automatically enrolled and the profiles and apps are distributed as soon as the users are assigned to the devices.
If you are an existing Zoho customer, you can sign up for MDM Cloud using your organization's Zoho account. To enroll the devices, follow the steps given below.
For Andorid devices, the users can download ME MDM app from Play store.
For iOS devices, you need to enable Self enrollment and enroll using Zoho account credentials.
You can also enable Conditional Access for Zoho Mail using MDM as explained in this document.
Follow the below mentioned steps to enable Chrome Device Management API
To enable Chrome Policy API, login to Google Admin Console using your admin account.
To enable Admin SDK API, login to Google Admin Console using your admin account.
New policies, restrictions, and inventory actions have been added to Chrome device management features. Integrating Google Workspace (G Suite) with MDM requires specific permissions and scopes. To do this, go to MDM Console > Enrollment > Chrome Enrollment > Integration Details > Re-Integrate.
When the third party SSL (Secure Sockets Layer) certificates are not imported to the server, the communication between the MDM server and the ME MDM app is not secure. To establish a secure connection, the user has to manually trust the certificates during MDM profile installation. To automate this, SSL certificates signed by a valid Certificate Authority is to be imported to the MDM server. This will verify the MDM Profile installation during enrollment.
NOTE: The error Not Verified does not alter any of the functionalities offered by Mobile Device Manager Plus.
If the APNs certificate has expired, Apple Push Notification service will not be able to contact the managed mobile devices. Renewing an APNs after expiry is the same as creating new APNs, which means all the devices need to be enrolled again to be managed. Assume that the APNs expires on 30th of June, you need to ensure that you renew your APNs well before the expiry date and update it in the Mobile Device Manager Plus server. All the managed mobile devices should contact Mobile Device Manager Plus server at least once before 30th of June. If any of the managed mobile device fails to contact the Mobile Device Manager Plus server, then those devices should be enrolled again. Hence we recommend renewing APNs before a month of its expiry.
Devices receive the APNs certificate once they come in contact with the MDM server. There can be a slight delay in the process but that does not affect the communication between the server and the devices. Password-protected devices need to be unlocked in order to contact the server.
The devices need not be re-enrolled. Renewing the APNs certificate is sufficient. It is recommended that the certificate be renewed at the earliest.
No, you do not require an Apple Developer Account to manage the iOS devices using Mobile Device Manager Plus.
You can use local authentication and specify a user name and email address. If you want to enroll corporate devices, then you can use Admin Enrollment options such as NFC and QR code for Android devices, ABM and Apple Configurator for iOS and Windows ICD for Windows.
Ensure the following before enrolling devices using Apple Configurator:
iOS 11 and above devices can be enrolled into ABM using Apple configurator, even if they aren't purchased directly from Apple or authorised resellers. Follow the steps given in this document to enroll these devices.
This error is usually encountered when you have enrolled iPhones previously using Apple Configurator. In case of iPhones, Apple Configurator fetches the IMEI and thus, in case of iPads it tries to fetch the IMEI(which is not available for iPads) and shows an error. In such cases, you can factory reset the device using Apple Configurator and retry the process.
By enrolling devices using ABM, you can leverage additional features such as,
Click here to learn more about Apple Business Manager. To use ABM for device enrollment, it must be available in your country. Click here to find the list of countries where ABM is supported. To make effective use of MDM, it is recommended to enroll corporate owned devices using ABM or Apple Configurator and employee owned devices using Invites or Self Enrollment.
When an ABM token is removed from a server, the licenses used to distribute the apps will be reverted to your account. When you use this token on another server, the licenses can be used to distribute the apps to the devices.
It is not possible to use the same ABM token on multiple MDM server, as each MDM server manages the complete set of licenses purchased with the token. This results in the MDM server revoking the licenses of the apps distributed to devices and also removes the apps from the devices.
Enterprises need Android device management software for several reasons. And Android device management tool or solution can:
Overall, Android device management software ensures efficient and secure management of Android devices in the enterprise environment.
Android MDM software offers a range of benefits to enterprises seeking efficient and secure management of their Android device fleet. By leveraging this software, organizations can enjoy the following advantages:
Mobile Device Manager Plus (MDM) provides a range of features to manage your organization's Android devices. Visit our help page to learn more about the extensive list of features supported by MDM and their compatibility based on device and provisioning type.
The ManageEngine MDM app is the companion app installed on a device during enrollment to ManageEngine Mobile Device Manager Plus. It serves as the agent app, facilitating the agent-server communication necessary for ongoing device management. Visit our help page to learn more about Mobile Device Management app.
For a device to utilize Android for Work(AfW)-based features and configurations, the OEMs(Original Equipment Manufacturers) must provide support for the same on the devices. If AfW support is not provided for a specific device model by the OEMs, they cannot support Android for Work and hence, features requiring the device to be provisioned as Profile Owner/Device Owner cannot be pushed to the device. Some of the devices supporting Android for Work are listed in these links - link #1, link #2 and link #3.
In this case, on the MDM console, navigate to Enrollment->ME MDM app (under Android) and set Communication Type to Periodic. Click on Save Changes. You can then enroll devices using EMM Token Enrollment, ADB enrollment, or NFC enrollment methods.
Work profiles are installed when Android devices are provisioned as Profile Owner using Android for Work. To verify whether Work profile has been installed in the device, go to Settings, and select Accounts. Work profile is listed under the Work section.
In Android devices running 5.0 or later versions, go to Settings, click on Accounts and select Remove work profile. Click on Delete to confirm the removal of all apps and data within the work profile.
We can delete an existing Web Shortcut by clicking on the delete icon beside the name. Deleting a Web Shortcut will re-publish the profiles to the device without the Web Shortcut.
No, passcode policy that is forced on the mobile device cannot be revoked by the user. Though users can disable passcode settings on their device, users will be forced to set passcode when the device is unlocked. However if MDM profile is removed from the device the device can no longer be managed by Mobile Device Manager Plus.
Policies and Restrictions which are applied successfully to the managed mobile device are called imposed policies.
Administrator instructs the users to accept the Policies and Restrictions which are pushed to the device. When the user over rules the policies and restrictions, then those policies and restrictions are called as violated policies.
When a user overrides the policies and restrictions pushed by the administrator, these policies will be marked as violated policies and will be listed under Violated Policies tab in ME MDM app. The consequence of violated policies differ based on the policy that is violated
Idle timeout before device lock specifies the time allowed for the device before the screen turns off. This is similar to the settings that can be configured in the device (Settings > General > Auto Lock). Grace period for device lock refers to the time allowed for the user before prompting for a passcode. The screen of the device turns off and when the user slides the arrow to unlock the screen he would be prompted to enter his passcode. This is similar to the settings that can be configured in the device (Settings > General > Passcode Lock).
In case of iOS devices, the settings can be restricted by disabling the individual settings under Restriction in Profiles. For Android devices, the Settings app can be disabled by disabling the option "Modify default device settings" under Restrictions in Profiles.
In addition to these methods, user can be prevented from changing any settings by running the device in Single App Kiosk Mode.
Yes, you can configure E-mail, Wi-Fi and other essential settings (such as VPN, Exchange etc.,) across platforms on MDM server and then associate it to groups. Devices added to this group on enrollment, are automatically distributed the configured policies and thus, getting pre-configured on device. Know more about all the policies supported by iOS, Android and Windows in MDM.
Admins can automatically Blocklist inappropriate or malicious content by enabling the checkbox Automatic restriction of malicious content or Automatically restrict inappropriate content under Web Content Filtering for Android and iOS device profiles respectively.
No, the profiles deal with specific device functionalities and are platform dependent. Therefore they cannot be applied to different platforms.
Yes, multiple profiles can be applied to devices. We recommend applying all account based policies as one profile and the restrictions as separate profile, as every time a modified version of the profile containing all these policies is re-distributed, the passcode for the account-based services such as Exchange and configurations such as Wi-Fi preferences, previously synced mails etc., specified in the account-related policies is reset and has to be manually entered by the user again.
For iOS devices, the most secure profile will be associated. Whereas in the case of Android devices, the most recently applied profile will be applied. For instance, if you distribute profile A with camera disabled and profile B with camera enabled, profile B will be applied on Android devices since that is the most recent. While in Apple, profile A will be associated since that is the most secure.
Restrict users from installing third party VPN apps as users can bypass the VPN restriction. You can blocklist VPN apps by navigating to Inventory -> Apps (Choose the VPN apps to be blocklisted) -> Blocklist.
One should always choose the device to be activated by the "Admin" to ensure a successful migration procedure of the device from one server to another.
The iCloud sign out will be greyed out on the device if Screen Time is enabled on the device. In that case, turn off the screen time from device settings to enable iCloud sign out.
We can prevent the installation and uninstallation of apps from devices by applying a few restrictions to devices.
Email, Exchange, and VPN can be configured through MDM by applying profiles, or by distributing the required apps. Profiles with the required configurations can be pushed to the devices, and using dynamic variables, user details will be mapped to the respective devices. However, the required apps for Email, Exchange, and VPN can be provided with app configurations, and distributed to the devices. This ensures that if an app gets a new feature, the user will be able to avail it. Refer this link for more details on app configurations.
Press the back button or tap on top of the home screen four times and enter the Revoke Administration Password in the space provided to remove ME MDM app when prompted, thus temporarily revoking management. If the device is in Kiosk, the password needs to be entered twice, i.e., once to exit Kiosk and again to revoke management from the device.
Mobile Device Manager Plus assures high security through restriction policies. Whenever more than one policy is applied for a same cause, whichever policy provides more security will get applied automatically. For example, assume two restriction policies are assigned to a device, where one is applied to authenticate the usage of camera and the other is to restrict the usage of camera, the policy which assures high security will get applied automatically. So the usage of camera will be restricted in the device.
No, Apple doesn't permit MDM solutions to restrict OS updates. However, MDM provides a workaround to prevent OS updates as explained here.
Restricting users from changing the date and time settings on devices is not permitted by Apple. Mobile Device Manager Plus can restrict the user from accessing any settings by running the device in Kiosk Mode where the device has access only to one app. Another method that can be used is, by ensuring the required apps are dependent only on the network date and time and not the device date and time.
You can make use of the CardDAV profile to distribute contacts to the managed devices. Here you can make use of Google contacts or any other third party service that supports CardDAV.
You can restrict users from modifying accounts on the devices by navigating Device Management -> Profiles -> Restrictions -> Advanced Security and restricting the Modify Account Settings option.
The user will not be able to modify accounts like mail accounts, iCloud and iMessage settings. If you want to completely restrict iCloud, then navigate to Profiles -> iCloud and restrict it. This will completed restrict the apps from syncing with iCloud and also the device backup on iCloud.
With iOS 11, Apple released a feature that allowed users to share the wi-fi credentials to new devices by bringing two devices running iOS 11 close to each other. Though this feature is useful and allows easy access to personal wi-fi, it can cause problems in corporate scenarios. That is why Apple ensured that any wi-fi distributed through a mobile device management solution cannot be shared to others using wi-fi sharing. Therefore, any wi-fi preconfigured using Mobile Device Manager Plus cannot be shared to other users using wi-fi sharing feature.
Case 1:
Case 2:
If the admin forgets or does not know the passcode, the only solution is to clear the passcode in the MDM server. If wrong passcodes are entered multiple times, the device will be disabled. After the device is disabled or locked by Apple if the device is switched off or restarted, the device will lose connection with the MDM server and the remote commands such as remove passcode issued from MDM server will not be executed on the device.
Guided Access can be overruled using the following methods:
Android has restricted backup and restore data functionality in devices provisioned as Device Owner by default. If you want to allow backup and restore, you can enable it using Restrictions profile. In case of Samsung devices provisioned as Device Owner, backup through Samsung Cloud and Smart Switch backup features is restricted by default and can not be enabled.
Users can be allowed to make phone calls and access contacts from Android devices in kiosk mode by adding the respective apps to the kiosk profile. Samsung and other Android devices make use of different package names for this app and hence it is recommended to search for the apps using the following bundle identifiers.
For policies and restrictions to be applied to the devices immediately, the devices have to be connected to the Internet. For Android and Windows devices, by default the MDM server communicates to the devices through FCM and WNS. This can be changed under Enrollment > ME MDM app> Configure mode of communication > Periodic. However, to manage iOS devices, the devices must have Internet connectivity.
App Store apps are those which are available in the App Store. They can be either paid App or free app. Enterprise apps, also called as In-House apps are specially developed and designed for every Enterprise. This is unique and completely owned and distributed by the Enterprise itself.
Volume Purchase Program(VPP) is used for purchasing app licenses in bulk and distributing the same to user either through managed distribution or redemption codes. Know more about Volume Purchase Program here.
Mobile Device Manager Plus app distribution is designed in such a way that you can only distribute iOS apps to iOS devices, Android apps to Android devices and Windows apps to Windows devices.
For mobile devices running Windows 8 and 8.1, the steps to perform App distribution:
AET refers to Application Enrollment Token. The Windows Phone 8 operating system requires users to enroll each device with the enterprise before users can install company applications on their devices. Only way to achieve this is using Application Enrollment Token, which enables you to distribute enterprise applications on a Windows Phone 8 device. For more information visit help.
Once a device is put into Single App Mode, no permission prompt will be generated. This means that the app cannot access any other features that use camera, contacts, or location services. The admin should allow these settings before putting the device into Single App kiosk.
Follow one of the given methods to distribute enterprise apps using Mobile Device Manager Plus:
Yes, you can remove apps present on the devices, by blocklisting them as explained here.
Yes. An app that is dis tributed by the admin using Mobile Device Manager Plus will be available in the container. An app that is installed by the user will be available outside the container. For example, you can have a Gmail app inside the container for corporate Email account and outside the container for personal Email account.
Currently we support only APK files. Kindly follow the right syntax while uploading XML files to avoid errors while uploading Enterprise apps.
App Bundle is a publishing format that lets developers deliver customizable features with smaller app size. Since MDM does not support distributing App Bundles, host the App Bundle privately to distribute using MDM.
You can restrict App Store on managed devices, by creating a profile and navigating to Restrictions -> Applications and restricting Users can install apps from App Store. This ensures only apps distributed through MDM can be installed on the device(must be running iOS 9.0 or later versions). If this is restricted for devices running other OS versions, even MDM-distributed apps cannot be installed on the device.
App Store apps can be installed without entering Apple ID, as explained here.
Yes, with the help of iOS app license management feature in ABM, Mobile Device Manager Plus will let you to revoke and reassign app licenses to the required user device.
Yes, the user has to enter the Apple ID to install the apps. To install apps silently or without requiring Apple ID, refer to this.
Yes, you can install enterprise apps silently on iOS devices, if they are Supervised. Firstly, add the enterprise app source .ipa file to App Repository. Distribute it to devices and/or groups, after ensuring the Force Install option is enabled in Distribution Settings
Yes, you can stop and/or control app updates on managed iOS devices, if the apps are distributed and installed on the devices through ABM. Also, ensure Without Apple ID is selected during the initial ABM settings. This allows the app to be installed without requiring Apple ID and the app gets associated to the device instead of Apple ID, which is how it is usually associated. As the app is not associated with the Apple ID present on the device, the App Store doesn't notify the users of possible app updates, when distributed through MDM. You can choose to force app updates on the device as explained here
Yes, you can choose to completely lock down the device by preventing users for installing/uninstalling apps and ensure only apps distributed via MDM is installed on the device. To lock the device to specific app(s)/settings, you can use Kiosk mode.
System apps also known as pre-installed apps can be blocklisted using MDM by following the steps given below:
Apple restricts users from updating apps that are more than 200MB in size over mobile data, so by default they get updated over Wifi. This can be changed under App Store-> App downloads -> Always allow.
To enable Developer Mode
The different app versions displayed are the versions compatible with each platform. Each app version is the supported version to that platform.
Note: The app developer decides whether the app version has to be same or different for each device(iOS, TVOS, macOS).
For example, Here in this case, The version 9.34.8 is compatible with iPhone, iPod and iPad. The version 2.3 is supported for Apple TV.
Unlisted apps are apps published in App store that can be accessed with their direct link. These apps are hidden and cannot be found by search.
You can distribute an unlisted app to devices through MDM via ABM.
If there is an app update available, ME MDM app is silently updated in Non-Samsung devices running 6.0 or later versions, provisioned as Device Owner and all Samsung devices. For other devices, a notification stating the same is displayed in the managed device and the user has to manually update the app. App updates are usually made available when there is a build update for MDM On-Premises or on a monthly basis(approx.) in case of MDM Cloud.
'APK' refers to application package file. Android program files are compiled in a package as .apk file, which is used for distributing the apps. When you need to add an android App to the App Repository you need to ensure that the android app is in .apk format.
Device Administrator should be enabled in the Android mobile device to authenticate Mobile Device Manager Plus Mobile Device Management to perform remote management activities in the device.
Samsung Smart Switch might not work for all devices as it is not designed for enterprise environments and the only way the app will work is through managed app configurations, kindly refer here for a detailed explanation.
Note: Smart Switch app should be enabled to run in the managed App configuration, for the app to work normally.
Yes, you can install enterprise apps silently on Android devices as explained here
This is an issue on particular models of Xiaomi devices. If you're unable to distribute enterprise apps to Xiaomi devices, follow the steps given below:
The ME MDM app on the Android devices (running Android versions below 8.0), creates an app shortcut when the app is installed on the devices. In most cases the user has enabled the Add icon to Homescreen option in Google Play Store. This creates another shortcut on the devices. Sometimes, even when the app is updated the existing shortcut is not replaced with a new one, resulting in multiple app shortcuts. This can also happen when specific device launchers are being used.
To avoid creation of multiple shortcuts, the user should disable the Add icon to Homescreen option from Play Store by navigating to Play Store->Settings->Add icon to Homescreen.
Upload the .apk file of the app to App repository and distribute it to devices as explained here.
This is due to staged rollouts of app updates on the Google Play store. An app developer can release updates only to a percentage of devices, which are chosen randomly. Click here for more information on staged rollouts.
Only the app versions which have completely rolled out (100%) are added to MDM. For example, say a staged rollout for an app is released for 20% of the devices. If the device falls into this category at the time of distributing the app via MDM, this issue of different app versions occurs. The app installed on the device will be of the latest version (The latest rollout), and the MDM server will have the previous version which has completely rolled out.
For apps developed using Google Play's multiple APK support (Listed as "Varies with device"), different APKs are targeted for different device configurations. Each APK of the app is an independent version, but they share the same app listing on Google Play. This might again display different app versions on the server and the device, based on the device type.
Android for Work (AfW) has stopped supporting paid apps. You can still distribute paid apps using MDM by adding them as Play Store apps (Non-AfW) to the App Repository. Once these apps are distributed to the devices, the user needs to access Play Store using a personal Google account where the apps can be purchased and downloaded. A personal Google account is also necessary to make in-app purchases. If a managed account is used in this place, only the free version of the app can be downloaded and in-app purchases cannot be made. To ensure that the user is able to add a personal account, navigate to Device Mgmt->Profiles->Android->Restrictions->Device Functionality on the MDM server and ensure that Add Accounts is set to Allow.
NOTE: If there are multiple accounts on the device, the user needs to switch to the personal account to make the purchases.
This can be done in 3 different ways.
This is due to staged rollouts of app updates on the Google Play store. An app developer can release updates only to a percentage of devices, which are chosen randomly. Click here for more information on staged rollouts.
Only the app versions which have completely rolled out (100%) are added to MDM. If the device falls into this category at the time of distributing the app via MDM, this issue of different app versions occurs. The app installed on the device will be of the latest version (The latest rollout), and the MDM server will have the previous version which has completely rolled out.
In Samsung devices, MDM restricts users from being able to close the ME MDM app. Once the device is switched on, the app will automatically start running. This is to ensure that the device maintains connectivity with the MDM server and that any policies or restrictions are immediately applied to the device.
We recommend that the notifications from the ME MDM app are always on, as these would keep the user informed about imposed policies or violated policies. Notifications can be turned off on the device's settings, but for devices running on Android 8.0 and higher, the notifications will by default be shown to the user. This is a privacy feature enabled by Android.
MDM enables apps on devices provisioned as Device Owner based on the following conditions:
If an app satisfies the above conditions, but still is not enabled on the device, this can be resolved by distributing the app via MDM. Navigate to App Repository> Add App> Play Store App>enter the Bundle Identifier of the app and save it. This app can then be distributed to the devices.
This issue is caused because MDM uses a tool called appt as recommended by google to analyze apk details. Recently aapt has been upgraded to the latest version - aapt2, which requires certain dll requirements that are missing in older versions of Windows Server 2012 R2 system. Thus, an error is thrown when executing the aapt2.exe. This can be solved in the following two ways:
In case of iOS and Windows devices, Mobile Device Manager Plus leverages the native MDM client already available in all the devices. The agent is required only to perform the following-
Whereas, in case of Android devices, an ME MDM app is required to manage mobile devices. The installation of the app is taken care of during the enrollment process.
If the device is enrolled with MDM, it has to be deprovisioned before being removed from the server. On the MDM console, open the Enrollment tab and click on the ellipsis button under the Action column, corresponding to the device to be removed from management. Now, click on Deprovision. The device will be moved to Staged tab from where it can be deleted using Remove Device option. If the device is offline or if it has already been unmanaged, it can be directly removed from the MDM server.
The admin can choose to deprovision the device to revoke MDM Management using the following options:
Repair Device, Employee left organization and Retire Device factory resets the device whereas under Others, the admin can choose between a Complete Wipe and a Corporate Wipe.
When the Complete Wipe option is chosen during deprovision, the device is factory reset resulting in the removal of all content and settings. When the Corporate Wipe option is chosen during deprovision, the consequences are as follows:
| PLATFORM | PROVISIONING TYPE | DESCRIPTION |
| Android | Device Owner, Core Android and Samsung devices | On device deprovision, all the associated profiles are automatically removed without uninstalling the formerly distributed apps. |
| Profile Owner | The complete work profile is removed resulting in the removal of every policy, app, and content distributed via MDM. | |
| Apple | On deprovision, all the associated profiles, apps and distributed content are removed from the device. The ME MDM app is also removed if Remove app on MDM Profile Removal option was checked at the time of adding it to the App Repository | |
| Windows | On deprovision, all the associated profiles, apps and distributed content are removed from the device. All configurations in Company/Workspace are cleared for devices running Windows 8.1 and above. | |
NOTE: If a passcode policy is associated with the device, only the policy is removed and the passcode remains on the device on deprovision.
To change the device name, navigate to Inventory and click on the Edit button next to the device name. To change user details, select the device in the Inventory tab, under Actions choose Edit User Details.
If the device has SIM slot, then MDM can display the IMEI. In case you've enrolled iPads that do not have SIM slots, the IMEI cannot be obtained and thus, not displayed by MDM.
The device status will be marked as inactive when the device loses contact with the server for a period longer than the duration specified by the admin. Below are the scenarios when a device may lose contact with the server. If the device,
Both Supervision as well as Device Owner provisioning lets the Administrator leverage additional control over the managed devices. It can be undone by factory resetting the device.
"Bring Your Own Device" (BYOD) being the integral part of Mobile Device Manager Plus, you can ensure the security of corporate data. Whenever any user's personal device is lost, or the employee quits an organization, administrators can execute security commands like corporate wipe or complete wipe to ensure data security. Hence Mobile Device Manager Plus MDM is a smart choice for every enterprise to manage BYOD.
Corporate wipe is a security command used to wipe data on the device. This security command is mostly used to secure the corporate data from devices, when they are lost. Corporate Wipe is used to remove only the configurations and Apps that have been pushed using Mobile Device Manager Plus and this command will not wipe any personal data of the user.
Corporate Wipe will remove Exchange Server or Email only, if they are configured via Mobile Device Manager Plus. This includes, the files and documents shared using the corporate e-mail.
Complete wipe command is used to wipe all in the data in the device, which makes the device as good as a new.
Yes, you can wipe data on the device's external memory.
You can secure corporate data on mobile devices by applying the following restrictions:
These restrictions will help you to secure Corporate data on mobile devices.
Mobile Device Manager Plus allows admins to remotely control Samsung, Sony and Lenovo devices running android 5.0 and above. Remote viewing capability is available for other Android devices above 5.0 and iOS devices.
Most organizations prefer to disable geotracking due to user privacy concerns. While admins have an option to track devices only when lost by configuring Geo-tracking Settings, some admins prefer to completely disable location tracking on devices. This can be achieved by navigate to Admin -> Device Privacy. Click on Modify and under Geo-location select Do not collect. Under Applicable Devices, select whether this setting must be applied only to personal, corporate or all devices. Click on Save and MDM would not collect any location details from the managed devices
You can associate users to either pre-defined roles or create roles and associate them. Additionally, you can modify the users, their roles and even delete them. Know more about user management here
It is to be noted the Super Admin of all the Zoho services are changed, when this is done.
For iOS device management, the Apple IDs are used by both the organization and the users. The organizations Apple ID should preferably be mapped to the organization and not any individual in the organization. While the user's Apple ID is mapped to the individual device user.
Following are the services that make use of the organization's Apple ID-
NOTE: It is recommended to only make use of the organization's corporate Apple ID for the above mentioned services, as they all require the same Apple ID to be used during renewal.
The user's Apple ID can be used for the following-
If the iPadOS devices are enrolled as shared iPad devices then this option will be missing. Admin can factory reset the device in the Inventory on MDM console by using Complete Wipe option.
Disable lost mode command may fail occasionally when Apple returns the command with error code 12069. To recover, factory reset the device using Apple Configurator or iTunes.
Note: But in the case of devices with no sim cards such as iPads when the device is in lost mode and is restarted then the Wi-Fi connectivity is lost and the device is locked. To avoid this, it is suggested to clear the passcode on the devices after successfully enabling lost mode on the device but before restarting the device.
The clear passcode action may occasionally fail due to mismatch in the unlock token(Unlock Token is used to unlock a device where a user has forgotten the device passcode. These tokens should be saved for devices when the devices are initially configured). The mismatch of this unlock token may happen if the OS update is pending or due to several other reasons. Hence, this issue can be resolved by updating the OS or restoring the device.
Declarative Device Management streamlines app tracking and reporting by enabling devices to automatically update statuses and report changes instantly. This ensures the inventory remains accurate in real-time without requiring frequent server check-ins, making device management faster and more efficient. To learn more click here
MDM requires these permissions to perform certain functions. Location permission is required to identify the already connected WiFi(from Android 8). So, we will use this while applying WiFi in restrictions payload or WiFi payload. We use bluetooth connect permission(from Android 12) to fetch the bluetooth mac address and also while applying the bluetooth always on/off restriction.
Android restricts collecting device identifier details like serial number, IMEI number, MEID etc in Profile owner devices as a part of privacy policy from Android 12 devices. To know more about this, refer here.
The Secure Folder option is prevented in the Samsung framework itself and when the device is enrolled as Device Owner, apps like a Secure Folder, Dual Workspace will be restricted by default because they will be using a separate user which cannot be managed by MDM.
For Non-Samsung devices: While factory resetting the device, the accounts will get removed and the FRP will be skipped.
For Samsung devices: Google Accounts present in the device need to be manually removed before wiping the device. The Account removal will be successful, only if the Google Play services are supported above a specified version.
A device enrolled using ABM/ASM cannot be unmanaged simply by factory resetting the device. To unmanage this device, we first need to remove the device from the ABM server and then reset the device in Recovery Mode.
Data encryption is mandated by Google for provisioning Android devices running 5.0 or later versions and 6.0 or later versions. Only for devices running 7.0 or later versions is encryption not required for provisioning the device as Profile Owner/Device Owner.
When Managed Google Play is integrated without G Suite on the MDM server, a Managed Account is created on the device. By default, this Managed Account cannot be removed by the user. However,
If the G Suite account is configured on the device by enabling Enforce EMM policies under G Suite admin console->Settings->Security->Mange EMM provider for Android, the account gets added to the Work Profile on the device. A Corporate Wipe command, erases the Work Profile along with the G Suite account.
Conditional Exchange Access can not be offered for Outlook for the following reasons:
You can compile the iOS logs from the device, using MDM app and mail it MDM Cloud support team(mdmcloud-support@manageengine.com)
You can compile the Android logs from the device, either using MDM app or without using MDM app and mail it to MDM Cloud support team(mdmcloud-support@manageengine.com)
The other option is to send the logs directly from the MDM app. Open the MDM app, click on the horizontal blue bar at the top 5 times.
Provide logs@memdm as password and then specify the issue details. Click OK to send the logs.
This is a pay-as-you-go Service and can be mended as and when you need. Additionally, you can also purchase offline(Non-Store) by mailing to sales@manageengine.com.
Payments are securely done using Zoho Store. MDM Cloud supports payment via Visa, MasterCard, American Express and PayPal. You can also purchase offline(Non-Store), by mailing to sales@manageengine.com.
For changing payment method from offline(purchasing licenses by mailing to sales@manageengine.com) to online,
You can also change the billing address here as well. All your confidential data is secured using VeriSign.