Configure details about the Win32 application, which include to define when to install it, how to install it, and when to identify installation is complete. To complete the process, assign the application to smart groups with the flexible deployment feature.

Configuration Process

  1. Configure the Details tab options.

    The AirWatch system cannot parse data from an EXE or ZIP file. Enter the information for the EXE and ZIP files on this tab.

    The system parses the listed information for MSI files.

    • Application name
    • Application version
    • Application identifier (also called a product code)
  2. Complete the Files tab options.

    Review the file initially uploaded and upload dependencies, transforms, patches, and uninstallation processes.

    File Description

    Configurations

    App Dependencies

    MSI, EXE, ZIP

    The environment and devices need these applications to run the Win32 application.

     

    1. Select dependency files in the Select Dependent Applications option.
    2. Enable the system to apply dependencies in a specified order. The system works from top to bottom.

    App Transforms

    MST file type

    These files control the installation of the application and can add or prevent components, configurations, and processes during the process.

    Select Add to browse to the MST file on the network.

    App Patches

    MSP file type

    These files add changes that are fixes, updates, or new features to applications. The two types are additive and cumulative.

    • Additive – Includes only changes developed after the latest version of the application or the last additive patch.
    • Cumulative – Includes the entire application including any changes since the latest version of the application or the last patches.
    1. Select Add.
    2. Identify the patch as cumulative or additive.
    3. Select Choose File to browse to the MSP file on the network.

    App Uninstall Process

    These scripts instruct the system to uninstall an application under specific circumstances.

     

    Customized scripts are optional for MSI files.

    1. Select the Use Custom Script option.
    2. Select to upload or enter a script to the system for Custom Script Type.
      • Select Upload and browse to the script file on the network.
      • Select Input and enter the custom script.
  3. Complete the settings on the Deployment Options tab.

    This tab instructs the system to install the application with specific criteria. The system can parse information for MSI files. However, for EXE and ZIP files, the system requires you to enter this information.

    1. When To Install

      Configure AirWatch to install Win32 applications when devices and your mobile network are in a specific state.

      Data contingencies work for both when to install and when to call install complete.

      • Instruction – This explanation describes system behavior for When To Install.
      • Completion – This explanation describes system behavior for When To Call Install Complete.
      Setting Description
      Data Contingencies

      Select Add and complete the options that depend on the criteria type you select. Set contingencies for these scenarios:

      • Instruction – Contingencies instruct the system to install applications when the device meets specific criteria.
      • Completion – Contingencies identify when an installation is complete.

      Add multiple criteria and configure the system to apply all contingencies (AND) or to apply alternative ones (OR).

      Criteria Type – App

      App exists

      App does not exist

      • Instruction – Configure the system to install the application when a specific application is or is not on devices.
      • Completion – Configure the system to identify the installation is complete when a specific application is or is not on devices.

      AirWatch checks for the existence of the application but it does not deploy the application to devices.

      Application Identifier

      Enter the application identifier so the system can recognize the existence or non-existence of the auxiliary application.

      This value is also known as the product code of the application.

      Application Version Enter the specific version.
      Criteria Type – File

      File exists

      File does not exist

      • Instruction – Configure the system to install the application when a specific file is or is not on devices.
      • Completion – Configure the system to identify the installation is complete when a specific file is or is not on devices.
      Path

      Enter the path on the device where you want the system to look for the file and include the filename.

      Modified On Enter the date the file was last modified.
        Criteria Type – Registry

      Registry exists

      Registry does not exist

      • Instruction – Configure the system to install the application when a specific registry is or is not on devices.
      • Completion – Configure the system to identify the installation is complete when a specific registry is or is not on devices.
      Path Enter the path on the device where the system can find the keys and values. Include the complete path starting from HKEY.
      Value Name

      Enter the name of the key.

      This container object stores the value and it displays in the file structure of the device.

      Value Type

      Select the type of key displayed in the file structure of the device.

      Value Data

      Enter the value of key.

      The name-data pairs stored in the key display in the file structure of the device.

      Select Add to continue setting deployment options.

      Setting Description
      Disk Space Required

      Set the disk space devices must have available for the system to install the application.

      Device Power Required

      Set the battery power devices must have available for the system to install the application.

      RAM Required Set the random access memory devices must have available for the system to install the application.
    2. How To Install

      Configure AirWatch to install Win32 applications to define the installation behavior on devices.

      Setting Description
      Install Context

      Select how the system applies the installation.

      • Device — Define installation by the device and all the users of that device.
      • User — Define installation by particular user accounts (enrolled).
      Install Command

      Enter a command to control the installation of the application.

      • MSI — The system automatically populates the installation commands, and the commands include patches and transforms.

        • Patches — To update the order in which the patches install on devices, update their listed order in the install command.
        • Transforms — The order in which the system applies transforms is set when you assign the application. You see a placeholder name for the transform until you associate the transform during the assignment process.
      • EXE and ZIP — Populate the install command and specify the patch names and their order of application in the command. You must also enter the install command that triggers the installation of the Win32 application.

        If you do not package the patches and transforms in the EXE or ZIP file and you add them separately, ensure to add the patch file names and the transform lookup text boxes in the install command.

      Admin Privileges Set the installation to bypass admin privilege requirements.
      Device Restart Require the device to restart after the application installs successfully, require the device to restart only if necessary for the application to function, or do not require the device to restart.
      Retry Count Enter the number of times the system attempts to install the application after an unsuccessful attempt.
      Retry Interval

      Enter the time, in minutes, the system waits when it tries to install the application after an unsuccessful attempt.

      Install Timeout Enter the maximum time, in minutes, the system allows the installation process to run without success.
      Installer Reboot Exit Code

      Enter the code the installer outputs to identify a reboot action.

      Review the entry for Device Restart. If you selected to Do not restart but you enter a reboot exit code, the system considers the installation a success after the reboot completes even though the Device Restart settings do not require a restart for success.

      Installer Success Exit Code Enter the code the installer outputs to identify a successful installation.
    3. When To Call Install Complete

      Configure AirWatch to identify successful installation of Win32 applications. The system requires this information for EXE and ZIP files.

      Setting Description
      Use Additional Criteria Configure the system to use specific criteria to recognize the completion of the installation process.
      Identify Application By

      Add specific criteria to identify installation completion or use custom scripts.

      Defining Criteria

      Select Add to enter criteria to identify the installation is complete.

      These settings are the same as the data contingencies.

      Using Custom Script
      Script Type

      Select the type of script.

      Command to Run the Script Enter the value that triggers the script.
      Custom Script Type

      Select Upload and navigate to the custom script file on the network.

      Success Exit Code Enter the code that the script outputs to identify successful installation.
  4. Select Save & Assign to configure flexible deployment options.

  5. Select Add Assignment and complete the options.

    Setting Description
    Select Smart Group Type a smart group name to select the groups of devices to receive the assignment.
    Push Mode
    • On Demand – Deploys content to a catalog or other deployment agent and lets the device user decide if and when to install the content.

      This option is the best choice for content that is not critical to the organization. Allowing users to download the content when they want helps conserve bandwidth and limits unnecessary traffic.

    • Automatic – Deploys content to a catalog or other deployment agent on a device upon enrollment. After the device enrolls, the system prompts users to install the content on their devices.

      This option is the best choice for content that is critical to your organization and its mobile users.

    Deployment Begins On

    Set a day of the month and a time of day for the deployment to start.

    The Priority setting governs which deployments push first. AirWatch then pushes deployments according to the Effective configuration.

    To set a beginning date with enough bandwidth for successful deployment, consider the traffic patterns of your network.

    Policies

    DLP

    Configure a device profile with a Restrictions profile to set data loss prevention policies for the application.

    Select Configure. The system navigates to Devices > Profiles. Select Add > Add Profile and the platform.

    For Windows Desktop, select Device Profile > Restrictions and enable options that apply to the data you want to protect.

    Application Transforms Associate transform files to the Win32 applications. This setting replaces the placeholder transform name in the Install Command option.
  6. Select Add and then Save & Publish.

See Dependency Files in Software Distribution for an explanation of what dependency files can do when deployed through AirWatch and possible issues that might arise if you delete dependency files that are associated to many Win32 applications.

See Patches in Software Distribution for an explanation of the system behavior for assigning cumulative patches to applications and restrictions for patches.

For information how to configure the restrictions payload for Windows Desktop, see Configure a Restrictions Payload (Windows Desktop).