1. Home
  2. Knowledge Base
  3. SureLock: StandAlone vs Integrated

SureLock: StandAlone vs Integrated

What is SureLock?

Businesses with mobile workforce require secured and locked mobile devices to ensure responsible usage, improved productivity, and reduced device maintenance cost. One of the ways to achieve the above-mentioned objectives is by allowing access to only required applications for users and preventing them from making any intended or unintended changes in the device. With SureLock, only the approved applications are allowed to run on the device and only the administrator can access the password-protected settings to either modify settings or exit lockdown.

42Gears offers Standalone SureLock and Integrated SureLock with the same features.


The purpose of this knowledge article is to provide instructions and recommendations for using Integrated SureLock to overcome the challenges of Standalone SureLock.




Standalone SureLock

In this model, SureLock (SL) is standalone and can be downloaded and installed manually from the 42Gears website and Google PlayStore. The management of licenses is handled on the Activation portal. This can be done by submitting a “deactivation request” on the portal by identifying the device using non-resettable identifiers such as IMEI, Serial, etc, or by deactivating the license manually from the device by navigating to “About SureLock” and selecting “Deactivate License.”

Limitations with Standalone SureLock on Devices running Android version 10 & Above.

Managing licenses on devices using the Standalone SureLock application can be challenging when dealing with Android 10 and newer versions. With Android 10 and later versions, SureLock would not be able to capture critical device identification information such as IMEI, Wi-Fi MAC address, or Serial number as per the limitations brought about by Google (refer to the link for more details). As a result, identifying and managing devices on the SureLock License Management Console becomes a more complex task. 

To address the challenges posed by Android 10 and above devices not sharing certain identifiers and the limitations of using IP addresses, Android ID, and GUID for device identification, it is indeed a practical approach for customers to note down the Android ID and GUID during the activation process. A summary is listed below:

  • IMEI, IMSI, and Wi-Fi Mac: Android 10 and newer devices do not share critical identifiers like IMEI, IMSI, or Wi-Fi MAC addresses to the activation portal, which can hinder device identification.
  • Static Identifiers: Android 10+ devices provide limited static identifiers such as IP address, Android ID, and GUID, which can be used for device identification.
  • Limitations of IP Address: Relying solely on IP addresses for identification becomes challenging when activating multiple devices within the same network, as they may share the same IP address.
  • Android ID Uniqueness: While Android ID is unique to each application, it may not be suitable for device identification, especially when multiple devices use the same SureMDM application.
  • GUID Visibility in SureMDM: The GUID, while useful for device identification, might not be visible in the SureMDM console, making it difficult to identify devices solely through the console.

To overcome these challenges:

It is advisable for customers to maintain a manual tracking setup during the activation process that records both the Android ID and GUID for each device. This manual tracking (Eg:  spreadsheet, excel etc.) can serve as a reference for device identification within the SureMDM system, providing a workaround for Android 10+ devices that do not share traditional identifiers.

By documenting these unique identifiers during activation, customers can enhance their ability to manage and identify devices effectively, even when dealing with the limitations posed by Android 10 and newer versions.

Technical Steps to follow:-

For users using Standalone SureLock:

Device GUID Spreadsheet: It is recommended to maintain a manual tracking that records the device GUID (Globally Unique Identifier) at the time of activation. This manual tracking (Eg:  spreadsheet, excel etc.) can serve as a reference for device management and centralized tracking of devices and licenses.

For SureLock Subscription License Modules:

Activation Date Process: we follow the activation date process to free up license (Monthly Subscription) renewals or device deactivation from the activation portal. This ensures efficient license utilization.

For Perpetual Licenses:

SureLock App GUID: It is advisable to record the GUID associated with the SureLock App for perpetual licenses. This information can be valuable for ongoing reference and management.

This revised suggestion provides a clear and concise approach to managing devices and licenses in Standalone SureLock, whether using subscription or perpetual license models.

Integrated SureLock:

In this model, SureLock (SL) is integrated as a major component within SureMDM Agent (NIX). SureMDM agent is responsible for communicating between the Device and Server to facilitate all the necessary information. Here, the license consumption is directly tied to device enrollment on the SureMDM console. Management of licenses (while deactivating SureLock) is handled in a much easier way with this model.


Advantages of Integrated SureLock

Deactivate SureLock Within Kiosk Mode: Customers can choose to deactivate SureLock on a device by exiting the kiosk mode. However, it’s important to note that the license will still be consumed as long as the device remains enrolled on the SureMDM console. This option is useful when customers want to temporarily disable SureLock without deleting the device.

Delete Device from Console: To release the associated SureLock license, customers can opt to delete the device from the SureMDM console. This action not only removes the device but also frees up the SureLock license for reassignment. This approach is suitable when customers no longer need SureLock on a specific device.

No Need for Manual Identifiers or Deactivation Requests: With the integrated SureLock and SureMDM solution, it would not be required to manually track the device identifiers or send deactivation requests. The license management process is streamlined within the console itself.

New Feature: SureLock Activation via SureMDM Agent: SureMDM introduces a convenient feature where administrators can enable SureLock on devices using the SureMDM Agent. This eliminates the need to separately install the SureLock application on each device. By simply installing the SureMDM Agent, administrators can access and utilize SureLock features on the devices, enhancing ease of deployment and management.

By leveraging these capabilities within SureMDM, users can efficiently manage their SureLock licenses and control the activation and deactivation of SureLock on enrolled devices, all from a centralized console.

Hence, we strongly recommend that customers choose Integrated SureLock for a better experience and seamless license management. 

Need help? CONTACT US

Was this helpful?
Updated on April 2024