All references to Device Guardian also apply to Device Guardian Access Management within this guide, unless otherwise specified.
Overview
Device Guardian and Device Guardian Access Management is a cloud-based solution that consists of:
- A cloud-based server, hosted and managed by Zebra
- Client software designed for Zebra Android devices
To enable communication between the device and the server, the client app must be installed and the device enrolled with the server. This allows for device tracking through the Device Guardian solution.
This section discusses the process to install Device Guardian and enroll those devices with the server. Device Guardian licenses are required for use.
Device Guardian Access Management (DGAM) follows the same installation and enrollment process as Device Guardian but requires a DGAM license instead of the Device Guardian license, with additional steps for setup that are detailed in the Access Management section.
Important for Android 11: For Android 11 devices, Device Guardian must be launched after installation to apply the configurations.
Installation Notes
- Google Play Services update - During an update, the Android system automatically stops Device Guardian. After the update is complete, relaunch the Device Guardian app or reboot the device to resume device tracking.
- Config Service Notification - When configuring Device Guardian client for the first time, a notification appears indicating the Config Service is running. This notification disappears following a subsequent device reboot.
- Compatibility with Device Tracker - The Device Guardian server is backward compatible with Device Tracker client apps. However, the Device Tracker client app cannot be upgraded to the Device Guardian client app; a new installation of the Device Guardian client is required.
Requirements
Device Requirements
Requirements for Device Guardian client on the device:
- Licenses - Device Guardian and Device Guardian Access Management require device licenses to operate. Contact a Zebra reseller to procure the licenses.
- Supported Devices - Check the Zebra support portal for compatible hardware.
Important: The WS50, as a non-GMS device, does not support:- Map-based Locationing (due to the lack of Location Services API support)
- Tracking of Bluetooth Scanner Accessories
- Operating System - Check the Zebra support portal for compatible Android versions and LifeGuard updates.
- Single Sign-On - To enable single sign-on (SSO) for user accountability, Identity Guardian v2.0 or higher must be installed separately on devices and configured with SSO Authentication Configuration.
- Optional: Secondary BLE allows a device to be located even if it loses battery power or is powered off. This feature is available on select hardware with secondary BLE capability; see compatible hardware. Refer to the Secondary BLE Configuration guide for setup instructions.
Network Requirements
Network requirements for the web portal and communication between the device client app and the cloud server:
Open HTTPS port. By default, port 443 is typically used for HTTPS communication. However, this may vary based on network configuration.
For administrators and managers to access the web portal (supplied by Zebra during onboarding), allow the web portal URL through the firewall or proxy.
An email is sent from
zdtrksupport@zebra.com
if reporting is enabled and if the password is reset.For web portal access and communication between the device client app and the cloud server, specific domain names must be allowed through the firewall or proxy.
If the firewall or proxy supports wildcards, add the following domain names to the allow list:
connectivitycheck.gstatic.com
*.googleapis.com
*.firebaseio.com
*.cloudfunctions.net
[ProjectID].firebaseapp.com
1[Web portal URL]
(supplied by Zebra during onboarding)
If the firewall or proxy does not support wildcards, add the following domain names to the allow list:
connectivitycheck.gstatic.com
www.googleapis.com
firestore.googleapis.com
firebasestorage.googleapis.com
cloudfunctions.googleapis.com
us-central1-[ProjectID].cloudfunctions.net
1[ProjectID].firebaseio.com
1[ProjectID]-default-rtdb.firebaseio.com
1*.firebaseio.com
2[ProjectID].firebaseapp.com
[Web portal URL]
(supplied by Zebra during onboarding)
1[ProjectID]
is included in the welcome email sent by Zebra services during the onboarding process.
2 For the Device Guardian client to communicate with the Cloud, *.firebaseio.com
must be accessible. It is required to allow this URL in your Firewall or Proxy settings. If your Firewall or Proxy policy does not support wildcard entries, follow these steps to obtain the specific URL:
- Open the following link in your browser (
[ProjectID]
is provided during onboarding):https://[ProjectID]-default-rtdb.firebaseio.com/.settings/owner.json
- Copy the URL displayed on the web page and add it to your Firewall or Proxy settings.
- Important Note: The URL from step 2 may change periodically due to Google’s server resource allocation. Steps 1 and 2 may need to be repeated regularly to retrieve the latest URL.
Web Portal Requirements
The web portal allows adminstrators to (1) configure Device Guardian, (2) manage users, (3) manage access points, sites, and devices, (4) automate workflows, (5) generate reports, and (6) view licenses. The web portal URL is supplied by Zebra during onboarding.
To access the web portal, in a supported browser enter the web portal URL. The supported browsers are:
- Chrome
- Edge
- Safari (v14.0 and later)
For first-time use, the administrator must set their password. Click Forgot Your Password in the web portal and enter the administrator email address, which is registered as a user in the system during onboarding. An email will be sent to the administrator with a link to set the password in order for the administrator to login.
If using single sign-on (SSO), see SSO for procedures on configuring SSO.
Licenses
End-user licenses are required for Device Guardian and Device Guardian Access Management to operate. Additionally, separate BLE licenses are required for secondary BLE operation, allowing devices to be tracked even after losing battery power. See Licensing.
Using ZDNA Cloud
Follow these steps to install Device Guardian via Managed Configurations with ZDNA Cloud and apply a policy that enrolls the device with the Device Guardian cloud server.
Part I: Enroll Device
Create and apply the StageNow barcode for device enrollment in ZDNA Cloud:
- Log in to ZDNA web portal. In the left menu, click New Device Setup.
- From the top-right, click Set Up Device.
- Configure the device for enrollment. Enter the appropriate internet settings, then click Next.
- Optionally, select the service for device enrollment. Click Next.
- Enter the properties and select the barcode type. Click Next.
- Review the information and click Next.
- The barcode is created. Click Done.
- The new setup is listed. Click View Barcode.
- For new enrollments, factory reset the device. Open StageNow and scan the barcode.
- After staging is complete, in ZDNA Cloud, click on My Devices and verify that the the enrolled device is listed.
- Allocate the license for the enrolled device. Click Licensing from the left menu. Under DNA CLoud License, click Allocate.
- Select the target device(s) to allocate the license to and click Allocate.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a Device Guardian Managed Configurations policy, which installs Device Guardian on the device and enrolls it in the Device Guardian server:
- In the ZDNA Cloud web portal, click My Apps.
- If adding Device Guardian for the first time, click Add App.
- If a new Device Guardian app version is needed, click Add Version.
- Select the appropriate hosting location, provide the details, and click Upload.
- The application version is added. Click Setup.
- Click Next.
- Click Yes to configure the app. Enable Server Connectivity Settings and copy and paste the content from the Managed Configurations .CONFIG file from step II.2, then click Next.
- Enter a description for the setup and click Next.
- Review the settings and click Apply Now.
- Select the target device(s). Click Apply.
- The device(s) is listed under the App Setup tab with the status of applying the configuration. Once complete, "Success" is displayed as the status.
Part IV: Send Intents (Android 11 Only)
For Android 11 devices, intents must be sent to grant the necessary permissions and start Device Guardian, allowing the configurations to be applied:
- Download the DeviceGuardian.xml file, which will be needed in a later step.
- In the ZDNA Cloud web portal, go to Device Settings. Click New Setting, then Create New Setting (Advanced).
- Select System Configuration. Enable Pass-Through Command and paste the content from
DeviceGuardian.xml
into the text field. Click Next. - Enter a Device Settings Name and Description, if needed, then click Next.
- Review the configuration settings. Click Apply Now.
- Select the target device(s) to apply the configuration. Click Apply.
Using Microsoft Intune
Follow these steps to use Microsoft Intune to install Device Guardian from the Google Play Store and apply a policy that enrolls the device with the Device Guardian server.
Screen Variations Note: The screen UI may vary depending on the EMM version in use. Refer to your EMM user guide for additional guidance.
Part I: Enroll Device
Enroll the device in Microsoft Intune using the standard EMM procedure.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a policy to install Device Guardian and enroll it in the Device Guardian server:
- In the Microsoft Intune web console, in Apps click Android.
- Click Create.
- From the dropdown, select Managed Google Play app, then click Select.
- Search for the Device Guardian app and click on it.
- Click Select, then click Sync.
- The Device Guardian app is added to the Play Store. Click on the app in the list.
- Click on Properties and Edit near the Assignments section.
- Under the Required section, click Add group.
- Choose the group to install the app and click Select.
- Update the priority. Click Default under the Update Priority column.
- For the Update Priority dropdown, select High Priority. Click OK.
- The group is added with the updated priority. Click Review + save.
- Click Save.
- Create a profile to enroll the device to Device Guardian. From the left menu, click Apps > Configuration. Click Create and select Managed devices.
- Enter or select the following, then click OK.
- Name: [Enter a name for the policy]
- Platform: Android Enterprise
- Profile Type: Fully Manged, Dedicated, and Corporate-Owned Work Profile Only
- Targeted App: Device Guardian
- Click Save.
- In the Settings screen, for Configuration settings format select Use configuration designer. Click Next.
- Select all the configuration keys and click OK.
- For Server Connectivity Settings, copy and paste the content from the Managed Configurations .CONFIG file from step II.2. Click Next.
- Under Included groups, click Add groups.
- Choose the group to apply the policy and click Select.
- Click Next.
- Review the configuration and click Create.
Device Guardian is installed and the devices are enrolled to the server.
Part IV: Send Intent (Android 11 Only)
For Android 11 devices, an intent must be sent to start Device Guardian, allowing the configurations to be applied:
In the Microsoft Intune web console, go to Apps and select Android.
Click Create.
For App type, select Managed Google Play app and click Select.
Search for Zebra OEMConfig app, then click on the app.
Click Select, then click Sync.
The Zebra OEMConfig app is added to the app list. Select the app.
Click Properties.
By Assignments, click Edit.
Under the Required section, click Add group.
Choose the required device group, then click Select.
The group is added. To enable automatic app installation, update the priority by setting it to high. Under Update Priority, click Default.
For Update Priority, select High Priority. Then, click OK.
Check that the device group is added to the list, then click Review and Save.
Click Save. The OEMConfig app gets installed to the assigned device group.
Configure the Device Guardian app to get enrolled to the server. Go to Devices and select Android.
Under Managed Devices, click Configuration. Click Create > New Policy.
Select the following and click Create:
- Platform: Android Enterprise
- Profile Type: OEMConfig
Enter a name, click Select an OEMConfig app and select Zebra OEMConfig Powered by MX. Click Select. When the app is added, click Next.
In Configuration settings, scroll down and select System Configuration.
Copy and paste the following text into the Pass-Through Command field, then click Next:
<wap-provisioningdoc> <characteristic version="9.2" type="Intent"> <parm name="Action" value="StartActivity"/> <parm name="ActionName" value="android.intent.action.MAIN"/> <parm name="Type" value="explicit"/> <parm name="Package" value="com.zebra.mdna.dg"/> <parm name="Class" value="com.zebra.mdna.dg.SplashActivity"/> </characteristic> </wap-provisioningdoc>
Click Next.
Under Included groups, click Add groups to assign the configurations to the devices.
Choose the device group and click Select.
The group is added. Click Next.
Review the changes and click Create. This launches Device Guardian, allowing the app configurations to be applied.
Using SOTI MobiControl
Choose one of two methods to install Device Guardian and enroll devices to the server using SOTI MobiControl:
Screen Variations Note: The screen UI may vary depending on the EMM version in use. Refer to your EMM user guide for additional guidance.
Google Play
Follow these steps to use SOTI MobiControl to install Device Guardian from the Google Play Store and apply a policy that enrolls the device with the Device Guardian server.
Part I: Enroll Device
Enroll the device in SOTI MobiControl using the standard EMM procedure.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a policy to install Device Guardian and enroll the device in the Device Guardian server:
- In the SOTI MobiControl web console, go to Apps > Policies. Click New App Policy.
- Select Android Enterprise.
- Enter an App Policy Name, then click the Apps tab.
- Click +.
- Select the following, then search for the Device Guardian app.
- App Source: Managed Google Play
- Select: Zebra Technologies
- Click on the Device Guardian app.
- Click on the options menu and select Configure.
- The application details are populated. Click Installation Options.
- In Installation Options, set the Priority to High Priority and enable Launch App After Installation. This step is particularly important for Android 11 devices. Then, click Managed App Config.
- Toggle to Enable Managed App Config. Enter the following, then click Save:
- Server Connectivity Settings: [When a prompt appears to import the config from a previous version, click Cancel and enter copy/paste the content from the Managed Configurations .CONFIG file from step II.2.]
- Kiosk Mode: [Toggle to enable if the device is a kiosk.]
- Select the new policy created.
- Click on the Assign icon, the second icon from the top menu.
- Search for the enrolled device, select the device, and click Assign. This applies the policy to the device.
Managed Configurations
Follow these steps to install Device Guardian via Managed Configurations with SOTI MobiControl and apply a policy that enrolls the device with the Device Guardian server.
Part I: Enroll Device
Enroll the device to SOTI MobiControl using the standard EMM procedure. After enrollment is complete, verify that the device has been added to the system.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a Device Guardian Managed Configurations policy, which installs Device Guardian on the device and enrolls it in the Device Guardian server:
- In the SOTI MobiControl web console, click Policies.
- Click New App Policy.
- Select Android and choose Android Enterprise.
- Enter a policy name and click on the Apps tab.
- Click +.
- For the App Source dropdown, select Enterprise.
- By default, Import is selected for the Source. Click Browse File and select the Device Guardian .APK file.
- After the file is uploaded, click Configure.
- The App Details are populated. Click Installation Options.
- Deployment Type is set to Mandatory by default. Toggle to enable Launch App After Installation and click Managed App Config.
- Toggle on Enable Managed App Config.
- Tap Cancel when prompted to import config to create a new config.
- For Server Connectivity Settings, copy and paste the content from the Managed Configurations .CONFIG file from step II.2. Click Save.
- Click Add.
- The policy is created. Click Save and Assign.
- Search for the enrolled device and select it. Click Assign.
- Navigate to the Devices section.
- Search for the enrolled device and select it.
- Click the Configurations tab and verify that the policy is assigned, ensuring the device is installed and registered in Device Guardian.
Part IV: Send Intents (Android 11 Only)
For Android 11 devices, intents must be sent to grant the necessary permissions and start Device Guardian, allowing the configurations to be applied:
Download the DeviceGuardian.xml file, which will be needed in a later step.
Create a file named
DG_XML_SOTI.CMD
with the following content and place this file in the same folder as the .XML file:mxconfig /sdcard/DeviceGuardian.xml
In the SOTI MobiControl web console, click Packages from the left menu.
Click Download Package Studio.
MobiControl Package Studio
MCStudio.exe
is downloaded. Execute to launch this app.Create a new package file for Device Guardian .XML. Click File > Create New Package File.
Enter the following and click Next:
- Project Name - [Enter a name for the project]
- Project Location - [Browse to the folder location to save the project]
- Platform - Android
Click Post-Install, browse to
DG_XML_SOTI.CMD
created in step 2 and click Next.Click Add. Click Add Files and browse to add
DeviceGuardian.xml
.Leave the default destination as
%sdcard%/
. Click OK.The file is added. Click Next, then click Finish.
A popup message appears indicating that the package is created. Click Build Package Now.
When complete, the output window displays the folder path with the package (.PCG file) is created. Record this folder path.
Upload the .PCG file to Soti MobiControl. In the SOTI MobiControl web console, click Packages and Add Package.
Click Import.
Select Android.
Browse to the package file (.PCG) folder path from step 13 and click Upload.
The new created package is listed.
Create a profile containing this package to deploy to devices. From the left menu, click Profiles.
Click Add Profiles, select Android, and select Work Managed.
In the General tab, enter the Profile Name and then click the Packages tab.
Click "+"
Search for the package just created, select it, and click Add to Profile.
Click Save and Assign.
Search for the device(s) to deploy the policy and click Assign.
Using Workspace ONE UEM
Choose one of two methods to install Device Guardian and enroll devices to the server using Workspace ONE Unified Endpoint Management (UEM), formerly known as AirWatch:
Screen Variations Note: The screen UI may vary depending on the EMM version in use. Refer to your EMM user guide for additional guidance.
Google Play
Follow these steps to use Workspace ONE UEM to install Device Guardian from the Google Play Store and apply a policy that enrolls the device with the Device Guardian server.
Part I: Enroll Device
Enroll the device in Workspace ONE UEM using the standard EMM procedure. After enrollment is complete, go to Devices > List View in the web console to verify that the device is listed.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a policy to install Device Guardian and enroll the device in the Device Guardian server:
- In the Workspace ONE UEM web console, go to Resources > Native. Click Public, then Add Application.
- Enter the following, then click Search App Store.
- Platform: Android
- Name: [Enter a name for the application]
- Search for Device Guardian app and click on the app.
- Click Select.
- Click on the app.
- Click Edit.
- Enter a name and click Save & Assign.
- Click Add Assignment.
- Enter or select the following, then click Application Configuration:
- Name: [Enter an assignment name]
- Assignment Groups: [Enter group to assign the app]
- App Delivery Method: Auto
- Auto Update Priority: High priority
- Enable Managed Access and Send Configuration. For Server Connectivity Settings, copy and paste the content from the Managed Configurations .CONFIG file from step II.2. Click Save.
- Click Publish.
- From the left menu, click Groups & Settings > Assignment Groups. Click on the assignment group created.
- Add the configured device(s) and click Next.
- Check for the assigned app and click Publish.
Part IV: Send Intent (Android 11 Only)
For Android 11 devices, an intent must be sent to start Device Guardian, allowing the configurations to be applied:
In the Workspace ONE UEM web console, go to Orchestration > File Actions. Click Add Files/Actions.
Select Android.
Enter a name for the file/action and click on the Manifest tab.
Under Installation Manifest, click Add Action.
Enter or select the following, then click Save.
Action(s) To Perform: Run Intent
Command Line and Arguments to run: [Copy and paste the text below.]
mode=explicit,broadcast=false,action=android.intent.action.MAIN,package=com.zebra.mdna.dg,class=com.zebra.mdna.dg.SplashActivity
TimeOut: [Enter any timeout value.]
Click Save. The file/action is created.
Create a product using the file/action just created. Go to Orchestration > Products and click Add Product.
Select Android.
Enter a name, assign a Smart Group, and click on the Manifest tab.
Click Add.
Select the following and click Save.
- Action(s) To Perform: File/Action - Install
- Files/Actions: [Select the File/Action created from step 6.]
Click Activate.
The assigned devices are listed. Click Activate. This sends the intent, launching Device Guardian on the devices for the configurations to be applied.
Managed Configurations
Follow these steps to install Device Guardian via Managed Configurations with Workspace ONE Unified Endpoint Management (UEM) and apply a policy that enrolls the device with the Device Guardian server.
Part I: Enroll Device
Enroll the device in Workspace ONE UEM using the standard EMM procedure. After enrollment is complete, go to Devices > List View in the web console to verify that the device is listed.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a Device Guardian Managed Configurations policy, which installs Device Guardian on the device and enrolls it in the Device Guardian server:
- In the Workspace ONE UEM web console, go to Resources > Native. Click Internal, then Add, and select Application File.
- Click Upload.
- Click Choose File. Select the Device Guardian .APK file to upload, then click Save.
- The Application File is populated with the file name. Click Continue.
- Enter the application name and version. Click Save and Assign.
- In the Assignment screen, enter the information prompted. From the left menu, click Restrictions.
- Enable Managed Access. From the left menu, click Application Configuration.
- Enable Send Configuration. For Server Connectivity Settings, copy and paste the content from the Managed Configurations .CONFIG file from step II.2. Select the target device(s). Click Save.
- Preview the assigned device group and click Publish.
- Navigate to Groups & Settings > Assignment Groups. Select the group to apply the policy.
- Select the device(s) to configure, then click Next.
- Verify the assigned applications and click Publish. The policy is applied to the device.
Part IV: Send Intents (Android 11 Only)
For Android 11 devices, follow these steps to send intents that grant the necessary permissions and start Device Guardian:
- Download the DeviceGuardian.xml file, which will be needed in a later step.
- In the Workspace ONE UEM web console, go to Orchestration > File Actions. Click Add Files/Actions.
- Select Android.
- Enter a name for the File/Action and click the Files tab.
- Click Add Files.
- Choose the
DeviceGuardian.xml
downloaded from step 1 and click Save. - Enter
/sdcard
for the Download Path, and enter the version if needed. Click Save. - The file is added. Click the Manifest tab.
- Under Installation Manifest, click Add Action.
- Select the following, then click Save.
- Action(s) To Perform: Apply Custom Settings
- File: DeviceGuardiana.xml
- The manifest is added. Click Save.
- The File/Action is created. Next, apply it to the device(s). Go to Orchestration > Product. Click Add Product.
- Select Android.
- Enter a name and assign it to the appropriate Smart Groups. Click the Manifest tab.
- Click Add.
- Select the following options and click Save:
- Action(s) To Perform: Application - Install
- Application: Device Guardian
- The application is added to the manifest. Click Add again to include the XML file.
- Enter the following, then click Save:
- Action(s) To Perform: File/Action - Install
- Application: [Nme of XML file added]
- Click Save.
- Click Activate. The policy is applied to the selected device(s).
Using 42Gears SureMDM
Choose one of two methods to install Device Guardian and enroll devices to the server using 42Gears SureMDM:
Screen Variations Note: The screen UI may vary depending on the EMM version in use. Refer to your EMM user guide for additional guidance.
Google Play
Follow these steps to use 42Gears SureMDM to install Device Guardian from the Google Play Store and apply a policy that enrolls the device with the Device Guardian server.
Part I: Enroll Device
Enroll the device in 42Gears SureMDM using the standard EMM procedure.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a policy to install Device Guardian and enroll the device in the Device Guardian server:
- In the 42Gears SureMDM web console, click on Profiles > Application Policy and click Add.
- For the Application Source, select Play For Work.
- Search for Device Guardian and click on the app.
- Click Select.
- Enter the following, then click Save:
- Configuration Name: [Enter a name]
- Server Connectivity Settings: [Copy and paste the content from the Managed Configurations .CONFIG file from step II.2.]
- Kiosk Mode: [Toggle to enable if the device is a kiosk]
- Enter or select the following for the application policy, then click Next.
- Install Silently: [Toggle to enable]
- Allow in Kiosk Mode: [Toggle to enable if the device is a kiosk]
- App Update Mode: High Priority Mode
- Grant all permissions, then click Finish.
- Enter a profile name and click Save.
- From the options menu click Assign Profile to Group.
- Select the device group(s) to apply the profile. Click OK.
Managed Configurations
Follow these steps to install Device Guardian via Managed Configurations with 42Gears SureMDM and apply a policy that enrolls the device with the Device Guardian server.
Part I: Enroll Device
Enroll the device in 42Gears SureMDM using the standard EMM procedure. After enrollment is complete, verify that the device has been added to the system.
Part II: Download Config File
Download the required configuration file from the Device Guardian web portal:
- In the left menu of the Device Guardian web portal, go to Settings > Device Enrollment. Click on Download Kit.
- Download the file and extract its contents. The Managed Configurations .CONFIG file is required for a later step.
Part III: Create and Apply Policy
Create and apply a Device Guardian Managed Configurations policy, which installs Device Guardian on the device and enrolls it in the Device Guardian server:
- In the 42Gears SureMDM web console, go to the Android App Store and click Add New App.
- Select Upload Apk.
- Upload the Device Guardian .APK.
- Enter the required information. Click Add.
- Create the application policy. Click Profiles and Add.
- Select Primary Profile for the Profile Type.
- Click Configure.
- Click Add.
- Select SureMDM App Store.
- From the dropdown, select the Device Guardian app uploaded. Click Next.
- For Server Connectivity Settings, copy and paste the content from the Managed Configurations .CONFIG file from step II.2. If the device is a kiosk, enable Kiosk Mode. Click Done.
- Select any desired options, then click Add.
- Select the app policy created, enter a profile name and click Save.
- From the top-right hamburger menu, select Assign Profile to Group.
- Select the group and click OK. The policy is applied to the device.
Prevent Play Store Updates
By default, Device Guardian, along with other Google Play apps, is set to update automatically. However, administrators managing Android devices may prefer to prevent Device Guardian from updating automatically via the Google Play Store. To manage updates, follow one of these options:
- Disable Automatic Updates - Submit the Disable_AutoUpgrade_DG.xml through your EMM platform.
- Enable Automatic Updates - Submit the Enable_AutoUpgrade_DG.xml through your EMM platform.
For alternative methods, refer to the blog post Preventing Play Store Apps from Updating Automatically.
Uninstallation
To uninstall Device Guardian from the device, remove the Device Guardian client app manually or through an EMM.
Server Termination
To terminate the Device Guardian cloud server, contact Zebra services. This removes the cloud server instance and deletes all data stored.