Device Diagnostic Tool (DDT) can be remotely configured through Managed Configurations, specifications developed by Google and the Android community to configure installed applications and deploy these configurations through an EMM (Enterprise Mobility Management). A schema defines the DDT features available for consumption by the EMM, providing the information necessary to present to the EMM's corresponding data-driven UI. This mechanism integrates DDT remote configuration within the EMM for seamless operation and allows Zebra to release a new schema as soon as new features are available for use. DDT and the Zebra schema are available from the Google Play Store and must be used together to leverage DDT with its managed configurations to perform diagnostic operations.
Requirements for use of Managed Configurations with DDT:
- Zebra device with Android 10 or Android 11
- DDT with the Zebra schema downloaded from the Google Play Store
- DDT is installed on the device and must be launched at least once
- An EMM for device deployment
- FTP Server to upload DDT test data
Recommended: To minimize security risks from disclosure of login credentials, Zebra recommends uploading test data to a dedicated server.
This section provides general instructions to use Managed Configurations through an EMM. The UI layout may vary depending on the EMM. In the EMM, after adding DDT to the device app catalog for app installation, the corresponding schema is automatically retrieved and presented to the EMM managed configuration UI based on the data defined. Through this UI, the administrator can select the desired Managed Configurations. Prior to pushing the Managed Configurations to the device(s), DDT must be launched at least once in order to accept these configurations. Instructions include how DDT can be launched remotely with OEMConfig.
General instructions to use Managed Configurations:
Add Device Diagnostic Tool to the application catalog. In the EMM, browse or search for Device Diagnostic Tool 2.7 or higher from the Google Play Store and add it to the app catalog. This automatically retrieves the corresponding schema for the app and makes the app available for deployment to the device(s) through the EMM.
Configure app restrictions using Managed Configurations as described in the schema. See App Restrictions section that follows, which describes the available options.
Push a policy that deploys the DDT app and the created Managed Configurations to the device(s).
Launch DDT remotely using OEMConfig - DDT must be installed from step 3 prior to executing this step:
Install OEMConfig on the device, if not previously installed.
In OEMConfig, open Device Administration Configuration.
Select Action > Submit XML.
In the input field for Submit XML, enter the text below to launch DDT:
<wap-provisioningdoc> <characteristic type="Intent"> <parm name="Action" value="StartActivity"/> <parm name="ActionName" value="android.intent.action.MAIN"/> <parm name="Package" value="com.symbol.selfdiagnostics"/> <parm name="Class" value="com.symbol.selfdiagnostics.activities.MainActivity"/> <characteristic type="Extra"> <parm name="ExtraType" value="string"/> <parm name="ExtraName" value="LAUNCH_DDT"/> <parm name="ExtraValue" value="1"/> </characteristic> </characteristic> </wap-provisioningdoc>
Note: Line breaks should be removed.
Apply OEMConfig configuration to the device(s).
There are 2 modes of operations for DDT: admin mode and user mode. Currently only admin mode is supported with managed configuration to schedule recurring tests and configure log uploads.
In admin mode, the DDT app restrictions are as follows:
- Test Plan - Create or modify a test plan that includes Schedule, Activity, and Delivery.
- Test Log Retention - Select whether to keep or discard test plans on device after automatic upload to server.
- Upload Preference - Select whether to upload logs based on a specified schedule or only after a test failure.
This section provides the options available for each app restriction.
Test Plan creates or modifies a test plan that includes the weekly test schedule, specifying the test to perform and configuring the server to receive the test results.
|Schedule||Test Day||Day of the week to automatically perform the weekly test||• Monday
|Test Time||Designated time to run the test and upload the result log file||[Time in HH:MM 24-hour format]|
|Activity||System to Test||Test to perform on the device||• Bluetooth
• SD card
|Delivery||Protocol||Protocol used by the server that receives DDT file uploads||FTP|
|IP Address||IP address for the user to access the DDT upload server||[valid IP address]|
|User Name||User name to access the DDT upload server||[valid user name]|
|Password||Password to access the DDT upload server||[valid password]|
Test Log Retention specifies the action to take for all test plan files on the device after uploading them to the designated server.
|Test Log Retention||Retain or discard test plan files on device after file upload to server||• Keep after upload
• Delete after upload
Upload Preference provides the selection to upload logs based on a specified schedule or only after a test failure.
|Upload Preference||Select whether to upload logs based on specified schedule or only after a test failure||• All test logs
• Only on failure
- OEMConfig - for launching apps remotely