'Exit Launcher' is a feature that can be used by a user to disable the functioning of the Seqrite Launcher for a specified duration. This can be done in two ways:

• The admin can send an 'Exit Launcher' command to the device and he can also specify the time duration for the same.
• The admin can share the Launcher passcode with the device user with the help of which the user can exit the Launcher.

The following methods can be used by an admin to remotely wipe data from a mobile device:

• Full Wipe - To wipe the internal memory and SD card memory.
• SD Card Wipe - Only to wipe the memory of the mounted SD card.
• Factory Reset - To wipe internal memory, SD card data, app data and customized settings.
• Custom Wipe - The wipe can be customized for specific folders and files.
  • Custom Folder - To delete a specified folder either on internal or external storage only.
  • File Type - To wipe a particular file type such as image, video, audio or others.

With the help of this setting, the admin can change the company name, details and logo. These details will get reflected on the MDM client app, Seqrite Launcher and the MDM portal. Please note that these details will reflect on the device client and the Launcher app only when the device is synced.

If the MDM client app that is installed on user devices is an older version, then the admin can recommend upgrading the MDM app to these users. This can be done by updating the MDM client app from Google Play, or via a custom URL or by uploading MDM.

A user can request an app from the 'Request App' page on the Seqrite Launcher tray. The app that is requested by a user can be a pre-installed app that has been blocked or it can be a new app from Google Play. Once the admin approves the request, the app gets listed on the device. The admin also has the option to reject the app request and provide a reason for the rejection. In the future, the user can also request for a previously rejected app again.

'Kiosk Mode' creates an extremely restricted environment on the Launcher. In this mode the admin can select a single app for the Launcher tray which would then be in auto-launch mode on the device. As soon as the configuration is applied on the device, the user can only use the single selected app and the MDM client app on the device.

The 'Block USB Connection' policy can be used to block a device from connecting with other devices through USB connections. Once this policy has been applied on a device, the user cannot use the device to connect with another device through USB. If the user attempts to do so, the device will get locked and it will only get unlocked once the USB is disconnected.

This policy can be used to restrict access to Safe Mode on any selected device. Once this policy has been applied, the device gets blocked and the password as per the password policy needs to be set. Once this password has been set, the device will not be allowed to access Safe Mode.

This is a command that can be sent by the admin to fetch the MDM app logs from any device. Once the command has been successfully sent, the 'Download Device Logs' button will be visible on the device overview page.

In order to publish a higher version of an installed app the admin needs to upload the new .apk in the app repository from the 'Upload Custom .APK' option or add the new URL from the 'Custom App URL' option in the repository. The admin then needs to go to the app configuration recommend list and select the code radio button of the specific version of the app which needs to be pushed. The user will then see the 'Upgrade' button in the recommended list and he can update the app at his convenience.

In order to publish a lower version of an installed app the admin needs to upload the old .apk in the app repository from the 'Upload Custom .APK' option or add the old URL from the 'Custom App URL' option in the repository. The admin then needs to go to the app configuration recommend list and select the code radio button of the specific version of the app which needs to be pushed. The user will then need to uninstall the existing version of the app and then install the recommended version at his convenience.

Both of these refer to the release version of the application code, as it should be shown to its users. 'Version Name' is a string value whereas 'Version Code' is an integer value that represents the release version.

The MDM admin can push higher or lower versions of apps to devices. With the 'Add and Publish' option the admin can add an app version from a custom app URL. With the 'Upload and Publish' option the admin can add an app version by uploading the custom .apk file.

While adding apps in the uninstall list OR block list, the MDM admin needs to select a specific version code checkbox. These options are listed under the package ID. Only the selected versions of apps will then be blocked on a device, and all other versions will be accessible.

In this case, only the pushed version codes of an app will be accessible or recommended to the device. All other versions of that app will be blocked on the device.

No. Once the admin publishes a higher/lower version of an app, then all other installed versions of that app will be blocked.

The admin can blacklist/whitelist specific websites by adding their name or certain keywords of theirs in the 'Blacklist/Whitelist URL' section of the 'Web Security' configuration.

Yes. Web security works on all browsing sessions of supported browsers and of the default Android browser.

The 'Web Security' configuration of MDM works on Google Chrome and its beta versions, Mozilla Firefox and its beta versions, Opera and its beta versions and the default Android browser.

In such a case the admin can add a specific URL in the whitelisted URLs section and block the other domains by adding the site's keyword in the blacklisted section.

To begin with, your network administrator needs to send an enrollment request to your device. In case you have not received the enrollment request, please contact your administrator. The enrollment request consists of an OTP, company code and the URL to download the MDM client. You then have to download the MDM client app from the URL and install it on your device. You need to enter the OTP and company code on the enrollment wizard to complete the enrollment.

• Go to the User List Page, select a user and click on Send Enrollment request from the dropdown menu.
• Enter the user details and go to the Enrolled Device tab and add a device for this user
• Go to the Device Page, add a device and then select it and click on Send Enrollment request from the dropdown menu.

Via the Send Enrollment request, the MDM portal sends an enrollment email and also an SMS to the user whose device needs to be enrolled through MDM. It contains the client app download link, OTP and the company code. End users can download the client app and complete the enrollment process by entering OTP and company code on the enrollment wizard.

Yes, the administrator can enroll different email domains that belong to a single user within the MDM portal.

Yes, an uninstalled device can be enrolled again on the portal. In order to enroll this device, a new enrollment request needs to be sent from the device list page or device overview page.

Once a device has been approved, a connection is established between the device and the server. Default anti-theft, default web security and default policies are pushed and applied on the device. Now the administrator can manage the device through the MDM portal.

• If the administrator approves a device enrollment request for a device and there is no Internet connectivity, then the Approve command goes into a Pending state until a timeout occurs. If the device receives Internet connectivity within the timeout period (24 hours) it is approved, or else the approval command will expire. If this happens, the administrator has to initiate the Approve command again for that device.
• If there is no Internet connectivity on a device after approval, then all the commands which could be initiated by the administrator go into a Pending state and expire after 24 hours. Internet connectivity is mandatory on devices so that the administrator can communicate with the device.

There are 2 methods to uninstall the MDM client app:

• If the device is not approved, the MDM client app can be uninstalled by the device user. To uninstall, go to the MDM app >> Menu >> Uninstall.
• If the device is approved, then only the administrator can send the uninstall command to the device. To uninstall, select a device from the device page, select the uninstall command from the dropdown menu and send to device.

For security reasons, we have restricted the user from uninstalling the MDM client app from his device. Only the administrator can send the uninstall command to uninstall the MDM application from a device.

In case of a factory reset, the MDM application will get removed from a device. The status of the device will show Uninstalled.

If a device has been approved, or its approval is pending, then the administrator cannot delete it from the MDM portal. In this case, he/she will need to send the uninstall command to the device in order to delete it. If the device status is inactive or pending, then the administrator can delete the device from the MDM portal.

In case you need to assign a device to another user, you need to change the owner of the device. You need to go the Devices listing page on the left-hand panel. Click on the Edit tab in the menu panel. Now click on Change Owner in order to assign this device to another user, or even to no user. You must then Save your changes.

This refers to a group of devices that require the same policies across all the devices. The administrator cannot apply any policy directly on any of these devices; rather, he has to apply a policy to any group and all the devices within the group will be configured with the policy. If the administrator wishes to apply the same policy to multiple devices, then he needs to carry out the following steps:

• Create a group and add devices into that group.
• Apply policy/configuration to that group.
• Applied policy/configuration is then pushed to all the devices of that group.

Here are the steps to grant administrator access to another user:

• Go to User Details >> Edit User
• Go to Edit >> Privileges
• Click the Allow Admin Access checkbox
• Select the user role from the dropdown menu and save it
• The user will then get an email to set password. Once this is done, he can access the admin portal using the email ID as username and password.

There are 5 different administrator roles as follows:

• Super Admin: He is the primary administrator of Quick Heal MDM. Only one Super Admin can exist within a company. He has all the privileges.
• Admin: He has all the same privileges as the Super Admin. Multiple Admins can exist within a company.
• Advanced User: He has all the privileges except for creating and deleting.
• Standard User: He only has update and assign/unassign privileges and has no privileges related to user roles.
• Basic User: He only has read-only privileges and export action privileges.

To track the activity performed by any administrator, go to Admin >> Activity Logs. This page shows the activities performed by any admin and it shows details such as date, user, action, context etc. that can be viewed.

• Ring: This command is to cause the device to ring.
• Locate: This command is to receive the latest location of the device. (Note: To get the location, Location Services/GPS must be enabled on the device. Enabling GPS could cause battery consumption.)
• Trace On : This command is to get the continuous location of the device (once every 30 minutes in case the device location changes).
• Trace Off: This command is to turn off the continuous trace command.
• Scan: This command is to initiate a scan on the device. The scan report is viewable on the server side.
• Sync : This command is to sync devices with the server. Scan reports and non-compliance alerts are sent to the server once this sync is initiated.
• Block: This command is to block the device completely.
• Unblock: This command is to unblock a device that has been previously blocked.
• Wipe: This command is to wipe all data from a user’s device. This includes data from the SD card, contacts, text messages, calendar entries and synced accounts.
• Approve : This command is to approve device enrollment requests. When the device status reads Approval Pending, it can be approved via this command.
• Unapprove: This command is to unapprove device enrollment requests. When the device status reads Approval Pending, it can be unapproved via this command.
• Uninstall: This command is to uninstall the client app from the user’s device.
• Push Policy: This command is to push a policy (a policy which is already mapped to the device) to a device. If a policy has failed to reach a device in the past, then we can repush that policy to the device.
• Push Anti-Theft: This command is to push anti-theft configuration to a device. If a configuration has failed to reach a device in the past, then we can repush that anti-theft configuration to the device.
• Push Web Security : This command is to push a web security configuration to a device. If a configuration has failed to reach a device in the past, then we can repush that web security configuration to the device.
• Push Wi-Fi: This command is to push a Wi-Fi configuration to a device. If a configuration has failed to reach a device in the past, then we can repush that Wi-Fi configuration to the device.

To unblock your device, you need to contact your administrator. If you are the administrator and would like to unblock a device you need to follow these steps:

• Go to the Device listing page or the device details page of the desired device
• Locate the device you wish to unblock and click on the edit symbol on the right
• In the Overview tab, click on Select an Action
• Now click on Unblock

If the administrator sends a Wipe command to your device, all data will be wiped from the device. This includes data from the SD card, contacts, text messages, calendar entries and synced accounts.

A smartphone or a tablet that runs on Android 2.3 (Gingerbread) and above, is supported by the Quick Heal MDM application.

In order to add a large number of devices, here are the steps:

• Go to the Users / Devices page from the menu panel on the left side
• Click on Import
• Select a file that you wish to import from your machine and then click on Import
• This file will need to be in the CSV format. This format can be downloaded from the same Import section.

Here are the steps for viewing the geo-location history of a device on a map:

• oGo to the Devices page and click on the edit button next to the device whose history you wish to view
• Click on the Location tab
• You can now select the checkbox next to the date and time of your choice, and the device’s location at that date and time will be displayed on the map
• You can view the location history of several time periods ranging from Yesterday, Last 30 days right up to the beginning of the device’s enrollment

You are viewing this message as there may be an issue with the device’s GPS location. These details will be available at a later stage.

The secret code is used by the administrator to unblock the device when there is no network or Internet connection available on the device.

When the administrator sends any commands to a device, the records are stored in the device details page. If the status there shows Success, then it implies that the command has been successfully sent to the device. The different statuses of commands are as follows:

• Pending: This signifies that the command/policy/configuration has not yet reached the device.
• Notified : This signifies that the command/policy/configuration has reached the device, but its acknowledgement has not yet been received by the server.
• In Progress : This signifies that the command/policy/configuration is in a continued state. This status is applicable for locate, trace on, scan and wipe process.
• Expired : This signifies that the command/policy/configuration was not able to reach the device due to no Internet connection or due to the phone being switched off.
• Cancelled: This signifies that the command was unable to be communicated with the GCM server.
• Expired : This signifies that the command/policy/configuration has reached the set timeout and has not reached the device.
• Success : This signifies that the command/policy/configuration has been successfully executed on the device.

There are 2 types of policies available and they are as follows:

• Device Policy: This consists of all policies that are used to apply restrictions on the mobile device. For instance, camera functionality, Bluetooth settings, Wi-Fi settings and more.
• Password Policy : This consists of all policies that are used to apple password restrictions on the device. For instance, password type, password length, auto-lock and more.

There are 3 types of configurations available and they are as follows:

• Anti-Theft Configuration: To protect the device from theft and loss, to block device in an emergency and to secure users.
• Web Security Configuration: To protect the device from malicious and phishing websites and to control Internet usage by blocking web categories which the administrator does not want the user to access.
• Wi-Fi Configuration: To grant the user access to Wi-Fi networks and to push Wi-Fi settings to the device so that the user can access the network.

On the configuration page, the Edit tab is present before each setting. The administrator can update any setting from here. When the settings are updated, the version gets incremented by 1 (the default setting is always 1).

Blacklisted URLs are those URLs which the administrator blocks the users from accessing. Whitelisted URLs are those URLs which the administrator specifically does not want to block.

You can apply multiple Wi-Fi policies to one device. However, you can only apply one web security/anti-theft policy to a single device.

Here are the steps to push a policy on a device:

• Go to the Devices page and locate the device where you wish to push a policy
• Click on the edit action on the right
• Under the Select an Action dropdown menu, select Push policy

Here are the steps to setup anti-theft on a device:

• Go to the Devices page and locate the device where you wish to setup anti-theft
• Click on the edit action on the right
• On the device details page, click on the Edit tab
• Click on Configurations
• Now you can select/update the anti-theft configuration as required

Here are the steps to setup web security on a device:

• Go to the Devices page and locate the device where you wish to setup web security
• Click on the edit action on the right
• On the device details page, click on the Edit tab
• Click on Configurations
• Now you can select/update the web security configuration as required

Here are the steps to setup Wi-Fi settings on a device:

• Go to the Devices page and locate the device where you wish to setup Wi-Fi settings
• Click on the edit action on the right
• On the device details page, click on the Edit tab
• Click on Configurations
• Now you can select/update the Wi-Fi configuration as required

If a user has not applied any policy/configuration which has been sent to him by the admin, then this device goes into non-compliance mode. The non-compliance mode shows that the user has violated/not followed configurations/policies as suggested by the administrator.

When the MDM client app communicates with the administrator portal, it sends non-compliant reports, enrollment requests and scan reports to the server. These reports show up as notifications on the server side. There are 4 types of notifications:

• Enrollment: When a user enrolls his device with OTP and the company code, the MDM portal gets notifications for approval or unapproval.
• Infection: When the administrator sends a scan command from the MDM portal, then an infection report is displayed in the notification window. If the device is infected, the report of the infected device is displayed in the proactive sync as well.
• Non-compliant: When a device goes into non-compliance, a notification is displayed after the sync command is sent by the administrator or when the device initiates proactive sync.

Google Cloud Messaging (GCM) is a service for Android that enables the transfer of data from your corporate server to the Android devices that your employees use. The devices that are on the same connection need to have GCM enabled in order to send and receive messages. GCM handles all avenues of queueing of messages and delivery to the Quick Heal MDM client app running on all targeted devices.

Configuring the GCM helps the Quick Heal MDM portal communicate with the mobile device. This establishes a bridge through which requests are delivered to the device. In case there is a change in GCM, the MDM portal will lose communication with existing devices so it is strongly recommended that GCM remains unchanged.

For the Free/Trial version, the administrator needs to send an email to corporate@seqrite.com in order to increase the number of devices supported.

For the trial version, the administrator can only manage the approved number of devices through Quick Heal MDM. You can purchase a license for as many devices as you wish. License subscription is based on a per device basis.

You need to send an email to corporate@seqrite.com in order to extend the MDM trial period duration.

Once your Trial Period has expired, the administrator will not be able to manage any device. All options and functionalities will be disabled. However, the administrator will have the ability to uninstall the MDM client app from devices with Approved or Approval Pending status.

In the window pane on the left-hand side of the portal, there is a section that says Help. The following options are available under this tab:

• Technical support contact details
• Live chat
• Submit ticket page
• FAQs
• User guide

The QR code enrollment feature is designed to make the device enrollment process easy and convenient. It enables Admins or users to enroll mobile devices simply by scanning a QR code.

You can make use of the QR code enrollment feature in order to enroll multiple devices against one/multiple user(s). The Admin needs to select the 'Send enrollment request using QR code' option to multiple users/devices. The Admin then needs to scan the QR code to immediately complete the enrollment process.

Currently, the QR code scan enrollment is only available for Android devices.

Install the Seqrite client app from Google Play and click on the Enrollment wizard header to show the 'Scan QR Code' option. Click on 'Scan QR Code' and then physically scan the QR code to complete the enrollment process.

Seqrite Launcher is an application through which an IT administrator can restrict Android device users from accessing certain applications or settings. The apps and settings which the device user can access can be customized by the administrator of Seqrite Mobile Device Management (MDM). With the help of Seqrite Launcher, admins gain complete control over how device perform, what apps are launched, how the home screen appears and more.

Using App Configuration, an admin can only block apps which are unwanted. However, with the help of Seqrite Launcher, the admin can customize the mobile device completely and only enable non-restricted apps to be visible on the device.

In case a user of a device does not install or activate Seqrite Launcher, that user’s device falls under the Launcher Non-Compliance list. The admin can view this list at any time and be updated about the non-compliant devices.

Once an admin pushes the app configuration (with Seqrite Launcher) to a device, the user of the device gets a prompt to install Seqrite Launcher. The user then needs to download and install the Seqrite Launcher app on the device. In order to activate it after installation, the user will be prompted to select one of the launchers present on the device. Hence, he will need to select Seqrite Launcher and also select the 'Always' option.

In order to add and activate apps, navigate to Apps > Configurations > Edit icon > Launcher > Add Apps. Then select the apps which you wish to enable on devices.

Seqrite Launcher can only be uninstalled by the Seqrite MDM portal admin in the following ways:

• Navigate to Manage > Devices > Edit icon > Edit > Configurations. Then assign a different app configuration which does not have the Seqrite Launcher setting enabled.
• Navigate to Manage > Devices > Edit icon > App Inventory. Then turn OFF the App Launcher toggle button.

This setting provides IT administrators with the option to add the IMEI numbers of all enterprise devices which are enrolled for Seqrite MDM. This helps in validating the devices when it comes to enrollment approval.

'Auto Approve' is an option through which device enrollment requests get approved automatically if their IMEI number is added in the 'Register IMEI' list and the 'Auto Approve' checkbox is ticked.

IT administrators can enable the call/SMS monitoring feature on devices in the following ways:

• Navigate to Manage > Devices. The ‘With Selected’ drop-down list then appears on the ‘Manage Devices’ page when a particular device is selected. Select “Call/SMS Monitoring ON” from the drop-down list and click Submit.
• Navigate to Manage > Devices > Edit icon > Call/SMS Logs. Then turn ON the ‘Call/SMS Monitoring’ toggle.

IT administrators can view logs for incoming/outgoing/missed/rejected voice calls or video calls. Incoming and outgoing SMS/MMS logs are also stored and can be viewed.

Navigate to Manage > Devices > Edit icon > Call/SMS Logs. Over here, all the call/SMS logs can be viewed.

Seqrite MDM does not provide call/SMS blocking features. The admin can only view the call/SMS logs from devices.

Seqrite MDM only monitors logs from the default calling/messaging apps installed on Android devices.

Seqrite MDM can only view the call/SMS logs since the feature gets enabled. Previous call/SMS records cannot be viewed.

Yes, the user can export these logs from the Call/SMS logs tab on the ‘Device Details’ page.

Call/SMS Monitoring is only supported on those devices which have calling/messaging facilities enabled on them.

With the help of the Network Usage configuration, admins can monitor data usage on Wi-Fi, mobile networks and roaming networks. The configuration also helps admins in identifying and tracking the data usage patterns of mobile devices within the MDM network.

Data usage can be monitored over Wi-Fi, mobile networks and roaming networks. Additionally, alert prompts can be set for users if a certain percentage of the mobile data plan is exceeded.

No, Wi-Fi or mobile data cannot be monitored independently. If the network usage configuration is pushed to a device, then both Wi-Fi data and mobile data will be monitored.

To monitor data usage through a company’s Wi-Fi, a network usage configuration needs to be created wherein the “MDM Configured Wi-Fi Networks Only” option is selected in the ‘Monitor Wi-Fi Usage’ drop-down under the Network Usage configuration.

To monitor data usage through a company’s Wi-Fi, a network usage configuration needs to be created wherein the “Monitor All Wi-Fi” option is selected in the ‘Monitor Wi-Fi Usage’ drop-down under the Network Usage configuration.

No, a user cannot be restricted from accessing the Internet when he exceeds the data usage limit. Only an alert prompt will be shown when the data usage limit is exceeded.

To see the data usage stats for individual devices, the admin needs to navigate to Manage > Devices > Edit icon > Network Usage tab. This tab shows the data usage by individual devices for the selected date range.

Yes, admins can set different mobile data plans or daily Wi-Fi limits for individual devices. To set this, they must navigate to Manage > Devices > Edit icon > Network Usage Tab. Once here, click on the Setting icon under the ‘Data Plan Information’ section. Upon doing so, the admin can change the billing cycle start date, number of days, mobile data plan limit, and Wi-Fi daily usage limit at the device level.