How To Start A Deployment

Use this page to learn about different deployment types in MANTLE Mobile.
If your MkDocs configuration limits the table of contents (TOC) depth to 2, only this top-level heading will appear in the sidebar. Below, each deployment type is presented as a tab.

Important: Before starting any Local or Workspace ONE deployment, ensure you have imported all required files (e.g., APKs, config files, etc.).

Local Deployment (Ad-Hoc)Local Baseline DeploymentWorkspace ONE Baseline DeploymentEnterprise DeploymentHandling Failures

Ad-Hoc deployments (sometimes called Local Ad-Hoc deployments) are user-initiated and on-demand, launched from the Home tab in the main GUI. This method allows you to select specific applications and configuration files to install immediately.

Steps to Perform an Ad-Hoc Deployment
1. (Optional) Check the "Device Management Pin" box if your devices require a stored PIN/password to unlock.
Leave it unchecked if no PIN or password is set.
2. Select the applications you want to install from the "Select Applications" column on the left.
3. Choose the configuration files in the right column "Select Config Files."
4. Click Provision to install and configure the chosen applications. Multiple apps install in the order they were selected.

Note

• APK and Configuration Files must be imported into MANTLE Mobile’s system using File Manager prior to deployment.
• See the File Manager section in Understanding The GUI for more details.

Local Baseline deployments also occur within MANTLE Mobile’s GUI but use a Baseline File to define which apps, configs, and prep settings to apply. This file is created through the Baseline Manager and must be imported before use.

Contents of a Baseline File
- Applications to install
- Configuration Files to execute
- Settings (Prep tasks) to apply to devices

See Baseline Configurations for more details on baseline file structure.

Steps to Execute a Local Baseline Deployment
1. In the Baseline tab (main GUI), select the baseline file you wish to use.
2. Click Deploy Selected Baseline to install and configure all items in that file.

Note

• Baseline Files, along with APKs and Config Files they reference, must be imported via the File Manager.
• See the File Manager section in Understanding The GUI.

Workspace ONE Baseline Deployments mirror Local Baseline Deployments but pull applications from Workspace ONE (AirWatch) rather than from MANTLE Mobile’s locally imported APK list.

Creating a Workspace ONE Baseline File
1. Configure MANTLE Mobile for Workspace ONE in the API Credentials Manager within Integrations.
2. Toggle on Integrations → Toggle Airwatch API Connection, confirming a green status stoplight on the Home screen (indicating a successful connection).
3. Open the Baseline Manager (Tools → Baseline Manager).
4. Change the dropdown above Select APKs from Local to Airwatch.

5. Select your Workspace ONE OG (organizational group), then click Fetch OG Applications.
- The Select APKs menu populates with the apps assigned to devices in that OG.
6. Select the desired APKs and transfer them to the table on the right. Repeat for any Configuration Files.
7. Click Generate Baseline to create the JSON file.
8. Import this new Baseline File via the File Manager.

After this file is imported, it appears under the Baseline tab in MANTLE Mobile, where you can deploy it exactly as you would a local baseline.

Note

• For a Workspace ONE Baseline, you do not need to import the APKs themselves into MANTLE Mobile; they install from Workspace ONE during the deployment.
• You do import the Baseline File and any referenced Config Files into MANTLE Mobile’s File Manager.

Enterprise Deployments integrate with Mantle Enterprise, allowing you to manage deployments from a centralized platform. These can be executed in two ways:

1. Toggling Enterprise Mode in MANTLE Mobile
2. Using the Enterprise Management Menu to manually sync and deploy

Prerequisites
- Register MANTLE Mobile as a “Node” in your Mantle Enterprise group.
- Have an active Provision in that group.
- See Enterprise Management in Integrations for details on node registration and Provision creation.

Enterprise Mode Toggle

• Once registered with Mantle Enterprise, toggle Integrations → Toggle Enterprise Connection to let Mantle Enterprise become the single source of truth.
• MANTLE Mobile will automatically:
• Sync devices from Enterprise
• Download any missing assets
• Check for active Provisions

Enterprise Management Menu

1. Go to Integrations → Enterprise Management.
2. Open the Devices tab, where you can:
3. Populate Local Device Table: Lists devices currently connected locally.
4. Sync Devices To Enterprise: Sends local device info from Device Management up to Mantle Enterprise.
5. Sync Devices From Enterprise: Pulls all devices from your Enterprise group and replaces your local list.
6. If a Provision is active for your group, click Check Enterprise Queue and Deploy to:
7. Download missing assets
8. Execute the Baseline File specified in the active Provision

When any number of devices failed to successfully provision due to an issue within a Configuration File, you will be presented with the option to Fix Failed Devices.

Selecting Yes will present you with a list of the devices that failed with the task they failed on.

After selecting the task you would like to fix, you have two available methods to modify the failed Configuration File:

• Record Conditional Tasks should be used if a pop-up or unexpected window that only occurs sometimes obscured the intended view for the failed task. This type of task will execute the configured tasks only if the Condition is met.

  • Ensure the obscuring screen is visible on the device and press Yes to continue.
    
  • Select a view to identify the Condition to begin the conditional tasks. (Example: The title of a pop-up.). Select Continue.
  • You will then begin recording the tasks that are to be executed to remove the obscurring window. (See Recording).
  • Once complete, you will be prompted to save a new Configuration File. This new file will be identical to the original failed Configuration File with a conditional task replacing the original failed task. With this new Configuration File, on devices where this pop-up occurs, the tasks you recorded will execute to remove the pop up. Devices without this pop up will continue as normal.

• Record Tasks to Insert should be used if there are additional tasks required to insert prior to the failed task that are always expected to occur.

  • After selecting Record Tasks to Insert, you will begin recording the tasks you would like to insert prior to the selected failed task. (See Recording).
  • Once complete, you will be prompted to save a new Configuration File. This new file wil be identical to the original failed Configuration File with the tasks you recorded here being inserted prior to the selected failed task.