To display only the features present on a particular device, select one or more filters from the SmartDocs bar below.
Input fields accept ENGLISH ONLY.
Queries from MX are not supported on Zebra devices running Android 11 or later. See alternative method.
EMDK For Android - 9.0
The "SmartDocs" bar can customize this page to show only the features present on a particular Zebra device.
OSX, MX and Android version information for a device can be found in the Android Settings panel or by querying the device through ADB, EMDK or the MX CSP. More info.
The Batch Manager (BatchMgr) is used to execute one Profile from within another, and can be viewed as sort of a subroutine call. In StageNow, a Batch setting is used internally (without explicit reference by the staging administrator) to generate barcodes and NFC tags, and to implement execution of the Deployment Section read from a Deployment Server.
A Batch setting also can be used explicitly by a staging administrator to leverage the functionality of one Profile (which can contain any number of settings) from within another. This could be used to create reusable "components" as Profiles that could then be used from other Profiles by embedding or referencing them from a Batch setting. For example, one staging administrator might create and test a Profile to demonstrate and prove that it provides some functionality. This Profile could then be exported as XML or saved as a binary file (e.g. for programming into an NFC tag). The Profile (as XML or binary) could then be embedded into a Batch setting. That Batch setting could then be used by a staging administrator (via "Re-use Saved Setting") in another Profile to perform the entire functionality of the embedded Profile at the point in the created Profile where the Batch setting is placed. The staging administrator using the Batch setting would have no visibility to the Profile that is embedded in that Batch setting but would nonetheless be able to exploit the functionality of that embedded Profile.
A Batch setting also can refer to a file in the device file system that contains a Profile (as either XML or binary) instead of embedding the Profile into the Batch setting. Such usage would require the "batch file" (the file containing the Profile) to be present in the device file system before the Batch setting that references it is executed for the proper result to occur. Such a "batch file" might be transferred to the device using a File setting or through some other "out-of-band" method. The Deployment Section functionality of StageNow is implemented internally and automatically using a combination of File and Batch settings without the need for the staging administrator to explicitly create either a File setting or a Batch setting. But a staging administrator could use such settings to construct more advanced or customized staging deployment scenarios.
Allows selection of a Batch Action to perform on a device.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Parm Name: BatchAction
Used to enter the path and file name of the certificate file (with .cer extension) on the device when Trusted Mode is used.
Parm value input rules:
.cer extensionStatus: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: Batch Action is "Turn On Trusted Mode"
Parm Name: TrustedModeCertificateFile
Requires:
- MX: 9.2+
- Android API: 26+
Enter the type of file to be processed.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Parm Name: BatchFileType
Used to enter whether the batch file is available on the device file system or embedded in the XML.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Parm Name: BatchFileAccessMethod
Provide the security password (empty = none) to decrypt the binary batch file.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: Batch File Type is "Binary" and Require Encodings box is "checked"
Parm Name: BinFilePassword
Requires:
- MX: 4.3+
Enter the path and file name on the device for location of the XML or binary file to be processed.
Note: Path must be a readable/writable location on device.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: File Access Method is "File in Device File System"
Parm Name: XmlFilePathAndName
Requires:
- MX: 4.3+
Select an XML or binary file in the workstation file system to be encoded and placed into the Batch setting.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: File Access method is embedded in XML
Parm Name: XmlFileData
Requires:
- MX: 4.3+
Enter the type of file to be processed.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: Batch File Type is "Binary"
Parm Name: BinFileRequireEncodings
Used to select whether the file can be examined by the StageNow client and descypted using a private key.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: Batch File Type is "Binary" and Require Encodings checkbox is checked
Parm Name: RequireOpaque
Used to select whether the file can be modified and descypted using a public key. Not supported in StageNow 2.0.
Status: Deprecated. This feature will be discontinued in devices running Android 14 and later.
Shown if: File Access method is "Batch File Type" and Bin File Require Encodings checkbox is checked
Parm Name: RequireImmutable