Adding Windows executable (exe) files

Information about adding an exe file to the App Catalog.

Procedure

  1. From the MaaS360® Portal Home page, select Apps > Catalog.
    The App Catalog page is displayed.
  2. Click Add, expand the Windows section, and then select Enterprise App for Windows.
    The Select an app type to Add enterprise app for Windows window is displayed.
  3. Select Windows Executables (.exe).
    The Enterprise App for Windows window is displayed.
  4. Provide the following details in the App Details tab:
    Option Description
    App Uploads an .exe file from your device.
    App Name Specifies the name of the app. For example, VLC Player.
    App Version Defines the version of the app. For example, 2.0.1.
    App Icon The app icon. The recommended size is 30 x 30 px.
    Description Provides additional information about the app.
    Category Assigns a category to your app.
    Screenshots The screenshots of the app.
  5. Select the Installation Requirements tab and provide the following details:
    Windows Install Requirements
    Option Description
    Installation Mode
    • Silent Installation: Enables the installation to run on its own without user interaction.
    • UI or Wizard based: Enables the (attended) manual installation that requires user inputs such as User ID or License key during the installation process.
      Note: UI-based installation is supported only on Windows 10 devices and newer devices that are enrolled in MDM.
    Installation Context
    • System or All Users: Enables all users of the computer to use and access the application. This installation context is recommended if the app installation requires admin privileges. The packages are installed in the Silent installation mode as the installation is run by system administrator.
    • Per User (Enrolled User): Restricts the access and use of the application to the user that installs the application on the computer. This installation context is recommended if the app does not require admin privileges. You must ensure that the user has proper permissions to install the app because some apps require admin rights.
    Execution Commands
    • Install: Specifies the silent installation command. The command must include the application name followed by the installation command switches.
      Some of the common EXE package silent installation commands are:
      • filename /S
      • filename /Silent
      • filename /quiet
      Note: Contact the application vendor or see the application documentation for silent installation and uninstallation commands that are supported by the application.

      For example, use the following command to silently install the VLC media player:

      vlc-2.0.1-win32.exe /L=1033 /S

      where
      • vlc-2.0.1-win32.exe is the filename.
      • /L is the language code.

      For more information about the VLC media player, see https://wiki.videolan.org/Documentation:Installing_VLC/.

    • Uninstall: Specifies the silent uninstallation command. Choose to automatically uninstall the app in the following scenarios:
      • MDM control is removed.
      • Selective wipe is issued to the device.
      • Distribution is removed.
      For example, to silently uninstall an VLC media player app, use C:\Program Files (x86)\VideoLAN\VLC\uninstall.exe /S.
    Relevance to install Defines the prerequisite component that is required for installing the app. The prerequisite is based on a registry key, file, or process. During app installation, MaaS360 checks for the prerequisite and installs or uninstalls the app only on the devices that meet the requirements.

    For example, use the javaw.exe process as a prerequisite for the Eclipse.exe package.

    The distributed apps that do not meet the requirement are marked as Not Relevant in the App Distribution and Installation Details page.
    Note: If an app is not relevant, the Get option to download the app is disabled in the end user App Catalog.

    Using negative install success/relevance criteria to check whether a script/job executed successfully on a Windows device (applies to MSI, EXE, and scripts)

    The negative install success/relevance criteria determines whether an app was successfully uninstalled or removed from the device during app upload based on the following criteria:
    • Registry key does not exist: Provide the path to the registry key, value name, and value data. For example: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Now
    • File does not exist: Provide the full path to the file name without quotes. For example: c:\recovery.txt
    • Process not running: Provide the process name. For example: testScriptProcessNew.
    Using exit code based install success criteria to check whether a script/job executed successfully on a Windows device

    Administrators enter exit code based install success criteria as a numerical value or as a comma-separated list of numerical values to determine whether an app was successfully uninstalled or removed from the device during app upload.

    Example of configuring negative install success/relevance criteria and exit code based install success criteria for an app

    Criteria
    Requires restart Indicates that a restart is required after the app is installed.
    Install Success Criteria Defines the criteria for detecting the app on the device. After installing the app, MaaS360 validates the criteria to determine the presence of the app on the device and returns the status of the installation. You can also provide an exit code (numerical value or comma-separated set of numbers) that determines the status of the app on the device.
    The app detection criteria is based on an existing registry key, file, or process.
    Note: The app installation is successful only if the criteria is met.

    For example, use the following file path to determine if the VLC media player is installed: C:\Program Files\VideoLAN\VLC\vlc.exe

  6. Select the Policies and Distribution tab and provide the following details:
    Option Description
    Remove app on Removes the app automatically from the device in the following scenarios:
    • MDM Control Removal: When MDM control of a device is terminated by the administrator or a user.
    • Selective Wipe: When a selective wipe is issued to the device.
    • Deletion from portal or stopping distribution: When the app has already been deleted from the MaaS360 Portal or when distribution is stopped on the device.
    Note: The Selective Wipe and the Stopping Distribution options are supported only on Windows desktops that use OS version 10 and later.
    Install Settings Indicates that the app is installed without user intervention.
    Distribute to Distribute to: The devices that receive the app. Use the plus icon to add multiple distributions. MaaS360 allows you to distribute an app to devices in the following ways:
    • None: The app is loaded in the App Catalog, but the app is not distributed to devices immediately.
    • Specific Device: The app is loaded in the App Catalog and deployed to a specific device.
    • Group: The app is deployed to a group of devices.
    • All Devices: All devices receive the app.