Create Files/Actions to install and configure files and upgrades onto your devices using product provisioning.

Windows Unified Agent is a 32-bit application, so when trying to run scripts in a 64-bit machine, proper redirections must be used to get access to the 64-bit folder or the registry hive.

To add files and actions to a Files/Actions component, take the following steps.

  1. Navigate to Devices > Staging & Provisioning > Components > Files/Actions and select Add Files/Actions.

  2. Select the device Platform for which you want to make the files/actions.

  3. Complete the General text boxes.
    Settings Descriptions
    Name Enter a name for the files/actions. The name cannot be longer than 255 characters.
    Description Enter a short description for the files/actions.
    Version The UEM console pre-populates this setting.
    Platform Read-only setting displays the selected platform.
    Managed By Select the organization group that can edit the files/actions.
  4. Select the Files tab.

  5. Select Add Files. The Add Files window displays.

  6. Select Choose Files to browse for a file or multiple files to upload.

    Windows Rugged devices can use the files/actions option to install XML onto a device. For more information, see Create an XML Provisioning File.

  7. Select Save to upload the files. Once the files upload, the file grouping screen opens. File groups allow you to assign different download paths and settings to different groups of files you have uploaded to a single file/action.

  8. Select uploaded files and select Add to move the files into a new file group.
  9. Define the Download Path the device uses to store the file group in a specific device folder. If the download path entered does not exist, the folder structure is created as part of installation.
  10. Windows Rugged devices can enable Relay Server Only to ensure that the device only receives the files/actions from a Relay Server and not from other sources. This option applies to Windows Rugged devices only.
  11. Select Save. You can repeat the previous steps for as many files as you want.
  12. Select the Manifest tab. Actions are not required if you have at least one file uploaded.

  13. Add actions to the Install Manifest or the Uninstall Manifest if needed.

    The uninstall manifest only runs when the Uninstall action is added to the product. Also, if nothing is added to the Uninstall Manifest, uninstalling the file/action results in no effect.

    Settings Descriptions
    AirWatch Agent Upgrade Install the new AirWatch Agent to the device. Before using this file/action,

    see Upload the AirWatch Agent .APF File for more information.

    Apply Custom Settings .

    Apply custom, OEM-specific device settings based on the selected XML file. You must upload the custom XML or ZIP file as part of the file/action.

    Supported Devices:

    • Android Motorola Solutions devices with the Android Agent v7.1+
      • Upload the ZIP file created by MSI.
    • Android Zebra devices with the Android Agent v7.2+
      • Create your XML configuration file using Zebra Stage Now.
      • Upload the XML configuration file and select it from the drop-down menu.
      • After pushing the product containing an Apply Custom Setting file/action, the status information reports in the Job Log. If an error occurs, the failed response XML is reported in the Job Log. For more information, see Product Job Statuses.
    Copy Files . Copy files from one location to another on the device.
    Create Folder . Create a new folder on the device.
    Delete Files . Delete folders from the device.
    Execute Script .

    Runs the selected script on the device. This command supports .sh and .scpt files.

    You must enter the script file path and name. Select Execute as Root to run the script as the Root user. If you do not enable this option, the script runs as the user currently logged in.

    Install . Install files on the device. You must use the Run manifest action to install files or applications. This is accomplished using command lines. Supports the following file types.
    • macOS: DMG, PKG, or APP (zipped).

      If the DMG file contains an APP file, Workspace ONE ™ UEM moves the APP file to the /Applications folder. If the DMG contains a PKG or MPKG file, extract the file from the DMG and push the PKG or MPKG directly.

      Workspace ONE UEM supports installing and managing .app files as internal applications which provide additional control for removing apps upon unenrollment.

    • Windows 7: REG, CAB, MSI, and XML.

    • Windows Desktop: REG, CAB, MSI, and XML.

      REG files require batch files and PowerShell commands.

    • Windows Rugged: REG, CAB, and XML.

      Workspace ONE UEM recommends using the Workspace ONE UEM CAB Creator to create CAB files that combine multiple files into one CAB file.

    Install Unmanaged Application .

    Install an unmanaged .APK file. Workspace ONE UEM does not add the app to the managed app list. Enterprise wipes or unenrollment do not remove the app from the device. You must use the Uninstall Unmanaged Application file/action. Consider adding Uninstall Unmanaged Application to the uninstall manifest of any product including the Install Unmanaged Application file/action.

    Move Files . Move files from one location to another on the device.
    OS Upgrade Install a new OS upgrade and the relevant AirWatch Agent. For more information on this option, see Create an Android OS Upgrade File/Action.
    Reboot Restart the device.
    Remove Folder . Remove a folder from the device.

    Rename File .

    Rename a file on the device.
    Rename Folder . Rename a folder located in the device.
    Run Intent . Run command lines and arguments on the device. See Appendix: Run Intent Action for more information.
    Run .

    Use the manifest to run an application. This is accomplished using command lines. The Run command must use the syntax of "\[full file path]". For example, \program files\program.exe.

    You must select the context of the command. Select whether the command runs at the system level, the user level, or the admin account level.

    Note:

    With macOS devices, you can run any root command that you normally use within Terminal. The automatically appends sudo before running any command.

    Terminate . End a process or application running on the device.
    Uninstall .

    Uninstall a program or application on the device. You must enter the application name.

    The application name must match the name that appears in the Uninstall menu in the Control Panel.

    Note:

    The Uninstall Manifest is for deleting files when a product is removed. If you remove a product from a device, any files installed remain on the device until uninstalled using an Uninstall Manifest.

    Uninstall Unmanaged Application .

    Uninstall an unmanaged application. Enter the package ID of the app.

    Warm Boot Restart the device.
    • Path Variables – For all file management-related actions listed above (copy files, create folder, delete files, move files, remove folder, rename file, and rename folder), you have the option of inserting a path variable for both source and target, as applicable. The use of these variables in your Files/Actions path means you do not need to account for the randomly generated OEM-specific path definitions in the creation of your Files/Actions.
    • $internal$ – Use this variable at the beginning of your path to indicate your source/target path to be read from/written to the internal storage space. Supports read and write actions.

      For example: /$internal$/agreement/license.txt addresses the file license.txt in the agreement folder on the device's internal storage space.

      Note:

      $internal$ does not work with all Files/Actions.

    • $external$ – Use this variable at the beginning of your path to indicate your source path to be from the external memory card storage, which the device must feature.

      External storage supports read-only access so any usage must involve a memory card that has been properly formatted and furnished with the correct files in the correct locations.

      For example: /$external$/sdcard/license.txt reads the file license.txt from the sdcard folder found on the device's external memory card storage.

  14. When finished adding actions to the Manifest, select Save.