Adding an enterprise app for Windows

Information about adding a Windows enterprise app to the App Catalog.

Procedure

  1. From the IBM® MaaS360® Portal Home page, select Apps > Catalog.
  2. In the App Catalog page, click Add. Expand the Windows section, and then click Enterprise App for Windows.
  3. In the Select an app type to Add enterprise app for Windows window, select the type of enterprise app that you want to add to the App Catalog. MaaS360 supports the following enterprise app types.
    App Type Description
    Windows Universal App Package Uploads apps that are built from the Windows 10+ SDK.
    • Supported file types - .appx or .appxbundle
    • Supported devices - Windows 10+ desktops, tablets, or phones
      Note:
      • Depending on the architecture of the app, the app is distributed to relevant devices: phones, laptops, or tablets.
      • MaaS360 automatically configures some settings in the background on devices to successfully distribute and publish appx packages on devices.

        For example, for every appx app distribution, the 'Developer settings' for the device is changed to 'Sideload apps' on the device, which sideloads an app successfully. When you sideload an app, you deploy a signed app package to a device. MaaS360 takes care of changing these settings during installation and after these appx apps are installed, the 'Developer settings' on the device reverts to the original settings.
    Windows Installers Uploads a Microsoft installer MSI program.
    • Supported file types - .msi
    • Supported devices - Windows 10+ desktops or tablets
    Windows Executables Uploads a Win32 EXE program.
    • Supported file types - .exe
    • Supported devices - Windows desktops or tablets
    Windows Scripts Uploads a Win32 script.
    • Supported file types - .bat, .vbs, .ps1, .reg, or .py
    • Supported devices - Windows desktops or tablets
    Note: If you upload a script that updates registry entries, make sure that you include the /s option. For example, regedit /s IMPORT %appname%

    The /s option allows the script to run silently. The script might fail if you do not use the /s option.
    Windows Downloadable Files Uploads any file.
    • Supported file types - .docx, .pptx, .jpeg, .png, .xml, or .init
    • Supported devices - Windows desktops or tablets
  4. In the Enterprise App for Windows window, go to the App Details tab and enter the following details based on the app type.
    • Windows universal app package (.appx or .appxbundle) files
      Option Description
      App Uploads an .appx or .appxbundle file from your device.
      Package Family Name Enter the package family name (PFN) of the app. To find the package family name of the app, follow the steps provided.
      1. Download and install the Windows App Management Admin Utility (https://m3.maas360.com/app-management/downloadAppInfoUtility.htm) on a Windows 10+ machine that uses PowerShell version 2.0+.
      2. Copy the app to the machine and run the utility.
      3. Select the app from a location on the machine and click Get App Properties to extract the Package Family Name.
      Description Provide a detailed app description.
      Category Provide comma-separated app categories.
      Screenshots Provide screenshots of the app.
    • Windows installers (.msi files)
      Option Description
      App Uploads a .msi file from your device.
      App Code, App Name, App Version Use the Windows App Management Admin Utility to extract the app code, name, and version. These details uniquely identify the .msi app.
      1. Download and install the Windows App Management Admin Utility (https://m3.maas360.com/app-management/downloadAppInfoUtility.htm) on a Windows 10+ machine that uses PowerShell version 2.0+.
      2. Copy the app to the machine and run the utility.
      3. Select the app from a location on the machine and click Get App Properties to extract the App Code, App Name, and App Version.
      App Icon Uploads an app icon. Recommended size - 30 x 30 px
    • Windows scripts (.bat, .vbs, .ps1, .reg, .py), and Windows downloadable files (.docx, .pptx, .jpeg, .png)
  5. Select the Installation Requirements tab and provide the following details.
    Option Description
    Installation Mode
    • Silent Installation - Installs packages in the System installation context.
    • UI or Wizard Based - Installs packages in the per-user installation context.
    Installation Context
    • System or All Users - Runs the script with the System privilege. The System or All Users installation is mandatory to enable all users of the computer to access and use the app.
    • Per User (Installed User) - Runs scripts with the user privilege. The Per User (Installed User) is mandatory to enable only the enrolled user to access and use the app.
    Execution Commands
    • Install - Specifies the installation commands along with parameters that are based on the type of the script.
    • Uninstall - Specifies the uninstall commands along with parameters that are based on the type of the script. (Users can edit this field now.)
    Use the following sample set of installation commands for standard script file types:
    • Batch file (.bat) - %APPNAME%
    • VBScript file (.vbs) - cscript.exe %APPNAME%
    • PowerShell file (.ps1) - powershell.exe -file %APPNAME%
      Note: If the machine's ExectutionPolicy is set to restrict, run the following installation script to bypass the restricted policy setting: powershell.exe -windowstyle hidden Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass; & \"%APPNAME%\"
      • Start the PowerShell process as hidden because the MDMExtenderService runs as the SYSTEM user.
      • The ExecutionPolicy is set to Bypass the restriction for the PowerShell process that runs. The Bypass setting is ended when PowerShell finishes running the script.
      • & is the call operator that helps you to run a command, a script, or a function.
      • The machine's ExecutionPolicy settings remain unchanged after the script execution is complete.
    • Reg file (.reg) - reg.exe IMPORT %APPNAME%
    • Others - %APPNAME%
    Note: MaaS360 runs PowerShell scripts as a 32-bit process from the following location. C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe.

    The PowerShell script that the administrator distributes from the App Catalog must run as a process based on the architecture of the device. For 64-bit devices, run the powershell.exe file from the following location. C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe -file %APPNAME%.
    Relevance to install Defines the app installation criteria or preconditions for the app so that the app installs only on devices that meet the predefined criteria. For example, the app is installed only if the supported registry key exists. The distributed apps that do not meet the criteria 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 user App Catalog.
    Requires Restart Specifies whether a restart is required after the app is installed.
    Install Success Criteria Defines the criteria to determine the status of an installed app.
  6. Select the Policies and Distribution tab and provide the following details.
    Option Description
    Remove App on
    The app is automatically removed in the following scenarios.
    • MDM Control Removal - When MDM control of a device is ended by the administrator or a user.
    • Selective Wipe - When a selective wipe is issued to the device.
    • Stopping Distribution - 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 Install Automatically - The app is automatically installed on devices.
    Distribute to
    Distribute to - The devices that receive the app. Use the plus icon to add multiple distributions. MaaS360 helps 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.
  7. Select the Advanced tab and provide the following details.
    Option Description
    App Discovery Portal Enter the custom app attribute values that are supplied for the app and specify whether to display the app in the App Discovery Portal. For more information about custom app attribute values, see Adding an app to the App Catalog. Users can use the App Discovery Portal to request apps that are distributed to other users in the organization.
    • Not Available - The app is not visible in the App Discovery Portal.
    • Viewing Only - The app is visible in the App Discovery Portal.
    • Viewing & Request - The app is visible in the App Discovery Portal for requests.