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.
StageNow - 5.10
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 File Manager (FileMgr) allows an application to manage files on the device. For example, FileMgr permits an app to download a file from a server to the device, copy a file or folder from one area of the device to another and to delete files on the device. The File Manager also can extract files embedded within an XML document and download from the internet with or without basic authentication.
/enterprise
/sdcard/Android/data
/storage/emulated/0/Download
Used to select an Action to be performed on a file or folder (if empty) on the device. StageNow limits file size to 2GB for FTP transfers from the workstation to devices. For larger files, an external staging server is required.
In preparation for Google-mandated security restrictions being phased in starting with Android 11, Zebra has implemented Secure Storage Manager (SSM), a mechanism for securely sharing files and/or data from an originating app to a target app in compliance with Android security mandates. In this process, direct file access is no longer permitted, and minor changes are required to ANY app intended to receive data shared through SSM.
SSM is compatible with the File Manger CSP delivered with MX 11.3 (and later) and its processes were designed to be transparent to the administrator in many file- and/or data-sharing scenarios. However, apps designated as the recipient of files and/or data shared through SSM must be able to access a file via URI. Such changes would be required not specifically for working with Zebra devices, but for compliance with Android security mandates that will eventually be required of all Android devices sharing data.
SSM is preinstalled on all Zebra devices running Android 11 and later.
File Action Option 10 (in the table, below) requires (or optionally works with, as indicated) these additional parameters:
com.targetApp.package.name/optionalAppFolderName/file.name
(see notes, below)The "Target Application File Definition" parameter (aka 'TargetApplicationAndFileName') accepts a combination of an app's package name (com.targetApp.package.name
in the example above), and the name of the file (file.name
) being shared. This file can be an app installer package (.apk) for installation on the device, a config file for configuring app settings, or any other type of file.
The middle section of the definition (/optionalAppFolderName/
) is an OPTIONAL folder (or path) under the target app (or created there if it did not already exist) that can be used to organize files for the target app. This storage area is accessible only by the designated target app, which can be another app on the device or the target app itself.
Any app intended to receive data shared through SSM must be capable of consuming data via URI.
Also see docs for Android Content Provider
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Parm Name: FileAction
Used to enter the location (URI) of the file to copy from the device to a remote server.
When exporting a StageNow Profile that contains any "external" URI field, data in that field is encrypted. If such a Profile is imported, contents of external URI field(s) in the Profile cannot be edited. See video, below.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Upload File(s)"
Parm Name: TargetURI
Requires:
- MX: 10.1+
Controls whether a file is copied/transferred to the device file system or embedded within an XML file.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Transfer/Copy"
Parm Name: TargetAccessMethod
Used to enter the path and file name on the device on which to perform the selected File Action.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Transfer/Copy"
Parm Name: TargetPathAndFileName
Requires:
- MX: 4.3+
Used to enter the path and folder name on the device on which to perform the selected File Action.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Transfer/Copy"
Parm Name: TargetPathAndFolderName
Requires:
- MX: 4.3+
Used to (optionally) enter a pattern to generate file names for files uploaded to a remote system.
Parm value input rules:
Example: A specified pattern of "model-serial-date-time" results in the file name:
"TC57-12345678901234-DD-MM-YYYY-HH:MM:SS-FileName
"
Note: Supported only on devices running Android 8.x Oreo and Android 10 or later.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Upload file(s)"
Parm Name: TargetFileNamePattern
Requires:
- MX: 10.1+
Used to enter the target application package name, optional path/folder name and file name of a file to be retrieved by the target application.
On devices running Android 11 and later, the target application must retrieve the file from Zebra Secure Storage Manager (SSM) in order to consume it. The optional folder path entered using this parameter can help the application maintain an application-specific file structure, if required.
Parm value input rules:
com.targetApp.package.name/optionalAppFolderName/filename.ext
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Deploy file for an application" and New Source Access Method is "File on device file system"
Parm Name: TargetApplicationAndFileName
Requires:
- MX: 11.3+
Used to enter the signature of the target application.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Deploy file for an application"
Parm Name: TargetApplicationSignature
Requires:
- MX: 11.3+
Used to enter the path and name of an on-device file to be uploaded to a remote system.
Parm value input rules:
Note: Supported only on devices running Android 8.x Oreo and Android 10 or later.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Upload file(s)"
Parm Name: SourcePathAndFileSpec
Requires:
- MX: 10.1+
Used to select the sort order when multiple files are copied or moved.
Note: Supported only on devices running Android 8.x Oreo and Android 10 or later.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Parm Name: UploadOrder
Used to control File Manager behavior when moving or copying files when a file of the same name exists at the destination.
Note: Supported only on devices running Android 8.x Oreo and Android 10 or later.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Upload File(s)" or "Transfer/Copy File" and Target Access Method is "File in Device File System"
Parm Name: IfDuplicate
Used to enter the location of the source file to be copied or transferred.
Note: Zebra recommends using this feature for files no larger than 2-300KB.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs. Deprecated in MX 11.2.
Parm Name: SourceAccessMethod
Used to enter the location of the source file to be copied or transferred.
Note: Zebra recommends using this feature for files no larger than 2-300KB.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Deploy file for an application"
Parm Name: SourceAccessMethod2
Used to select whether the file should persist locally on the device following an Enterprise Reset. Learn more about Enterprise Reset.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Deploy file for an application"
Parm Name: PersistFile
Used to enter the URI of the location of the file on a server. Supports HTTP, HTTPS, FTP and FTPS (FTP over TLS or SSL) protocols and basic authentication of URL-embedded credentials. See Examples section for syntax.
IMPORTANT: File Manager does NOT support anonymous FTP.
Parm value input rules:
Note: HTTP/S requires MX 7.0+; FTPS requires MX 7.1+. HTTP/S not supported on devices running Android 4.4 (KitKat); use built-in source URI references only. File Manager does NOT support anonymous FTP.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs. Deprecated in MX 11.2.
Shown if: File Action is Transfer/Copy and source is remote server
Parm Name: SourceURI
Requires:
- MX: 4.3+
Used to enter the URI of the location of the file on a server. Supports HTTP, HTTPS, FTP and FTPS (FTP over TLS or SSL) protocols and basic authentication of URL-embedded credentials. See Examples section for syntax.
Parm value input rules:
Note: HTTP/S requires MX 7.0+; FTPS requires MX 7.1+. HTTP/S not supported on devices running Android 4.4 (KitKat); use built-in source URI references only. File Manager does NOT support anonymous FTP. StageNow limits file size for some FTP transfers to 2GB.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Deploy file for an application" and New Source Access Method is "File on device file system"
Parm Name: SourceURI2
Requires:
- MX: 11.3+
- Android API: 30+
Used to enter the path and file name of the source file location on the device.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs. Deprecated in MX 11.2.
Shown if: File Action is "Transfer/Copy" and source is on device
Parm Name: SourcePathAndFileName
Requires:
- MX: 4.3+
Used to enter the path and file name of the source file location on the device.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Deploy file for an application" and New Source Access Method is "File on device file system"
Parm Name: SourcePathAndFileName2
Requires:
- MX: 11.3+
Controls whether source files are deleted after being uploaded.
Note: Supported only on devices running Android 8.x Oreo and Android 10 or later.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Parm Name: DeleteAfterUpload
Used to enter the type of file to be embedded.
Note: Zebra recommends using this feature for files no larger than 2-300KB.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Transfer/Copy" and Source is "Embedded"
Parm Name: SourceType
Used to enter the source file data to be embedded in the XML.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Transfer/Copy "and Source Type is "File Embedded in XML" and Source Type is "General Data File"
Parm Name: SourceDataAny
Requires:
- MX: 4.3+
Used to enter the APK source file data to be embedded in the XML.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is Transfer/Copy and source type is 'File embedded in XML' and Embed type is 'Android Application' remote server
Parm Name: SourceDataApk
Requires:
- MX: 4.3+
Provide the source ZIP file data to be embedded in the XML.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is Transfer/Copy and source type is 'File embedded in XML' and Embed type is 'Android OS Update' remote server
Parm Name: SourceDataZip
Requires:
- MX: 4.3+
Used to enter the path and folder name into which the downloaded archive file should be expanded.
Parm value input rules:
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Download and Expand Archive"
Parm Name: ArchiveTargetPathAndFolderName
Requires:
- MX: 5.0+
Used to enter the URI of the source archive/ZIP file.
Parm value input rules:
Note: MX 8.3 (or later) is required to specify a remote (external) download server, if desired.
Status: In devices running Android 13 and later, this feature can be accessed through StageNow and compatible EMM systems, or using Android system APIs.
Shown if: File Action is "Download and Expand Archive"
Parm Name: ArchiveSourceURI
Requires:
- MX: 5.0+
<wap-provisioningdoc>
<characteristic type="FileMgr" version="5.0" >
<parm name="FileAction" value="1"/>
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2"/>
<parm name="SourceAccessMethod" value="1"/>
<parm name="SourceURI" value=" http://mycompany.com/file/emmtk.war"/>
<parm name="TargetPathAndFileName" value="/internal/tmpp/10m_testfile.bin"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="FileMgr" version="5.0" >
<parm name="FileAction" value="9"/>
<characteristic type="file-details">
<parm name="ArchiveTargetPathAndFolderName" value="/sdcard/Android/extract3"/>
<parm name="ArchiveSourceURI" value="https://secure.mycompany.com/httpsdownload/ArchiveFileTemp.archive"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="FileMgr" version="5.0" >
<parm name="FileAction" value="1"/>
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2"/>
<parm name="SourceAccessMethod" value="1"/>
<parm name="SourceURI" value="http://username:password@192.168.0.100:21/secure/10m_testfile.bin"/>
<parm name="TargetPathAndFileName" value="/internal/tmpp/10m_testfile.bin"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
NOTE: File Manager does NOT support anonymous FTP.
<wap-provisioningdoc>
<characteristic version="0.6" type="FileMgr">
<parm name="FileAction" value="1" />
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2" />
<parm name="TargetPathAndFileName" value="/storage/sdcard0/sample.apk"/>
<parm name="SourceAccessMethod" value="1" />
<parm name="SourceURI" value="ftps://username:password@192.168.0.100:21/secure/10m_testfile.bin" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
NOTE: File Manager does NOT support anonymous FTP.
<wap-provisioningdoc>
<characteristic version="0.6" type="FileMgr">
<parm name="FileAction" value="1" />
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2" />
<parm name="TargetPathAndFileName" value="/storage/sdcard0/sample.apk"/>
<parm name="SourceAccessMethod" value="1" />
<parm name="SourceURI" value="ftps://username:password@192.168.0.100:21/secure/10m_testfile.bin?implicit=true" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="FileMgr" version="5.0" >
<parm name="FileAction" value="1"/>
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2"/>
<parm name="SourceAccessMethod" value="1"/>
<parm name="SourceURI" value="ftp-p://username:password@192.168.0.100:21/secure/TestFile.apk"/>
<parm name="TargetPathAndFileName" value="/sdcard/TestFile.apk"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
NOTE: File Manager does NOT support anonymous FTP.
<wap-provisioningdoc>
<characteristic type="FileMgr" version="5.0" >
<parm name="FileAction" value="1"/>
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2"/>
<parm name="SourceAccessMethod" value="1"/>
<parm name="SourceURI" value="ftp-p://username:password@192.168.0.100:21/secure/TestFile.apk?ftpClient.keyStore.file=/enterprise/usr/stagenow/vsftpd.p12&ftpClient.keyStore.password=password&ftpClient.keyStore.type=PKCS12&implicit=true&protocol=SSL"/>
<parm name="TargetPathAndFileName" value="/sdcard/TestFile.apk"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Special (reserved) characters in a user name (i.e. the @ sign) must be encoded. For example, "username@company.com" should appear as "username%40company.com" in the SourceURI (as below).
<wap-provisioningdoc>
<characteristic version="5.0" type="FileMgr">
<parm name="FileAction" value="1" />
<characteristic type="file-details">
<parm name="TargetAccessMethod" value="2" />
<parm name="TargetPathAndFileName" value="/sdcard/TestFile.apk" />
<parm name="SourceAccessMethod" value="1" />
<parm name="SourceURI" value="ftp-p://username%40company.com:password@192.168.0.100:21/Test/TestFile.apk />
</characteristic>
</characteristic>
</wap-provisioningdoc>