Managing Windows Applications

Managing Windows applications in Esper is straightforward and flexible. From uploading applictions to deploying apps across devices using blueprints, groups, or scripts, the Esper console provides multiple ways to control how and where your Windows apps are installed.

Requirements: 

• Windows MSI or EXE applications under 2 GB

In this article: 

• Uploading MSI Apps
• Managing MSIX and MSIXBundle Windows Apps
  • Uploading an MSIX or MSIXBundle App
  • Managing Dependencies
  • Uploading a Signing Certificate
• Managing EXE Applications
  • Uploading an EXE Application
  • Activating the EXE Application Version
• Deleting and Editing App Details
• Uploading Apps to Windows Devices

Uploading MSI Apps 

In Apps, go to the Windows tab. Click on Upload Apps to add the app. 

Then click on Browse Files and select the MSI file. Alternatively, drag and drop the file on the screen. 

File size limit: 2 GB

The upload will begin. 

Once the upload completes, the app will be available in the Apps section. 

Click on the app to see more details.

You can also upload multiple versions of the same application. All versions will be saved under the application. 

Managing MSIX and MSIXBundle Windows Apps

Esper supports uploading and deploying MSIX and MSIXBundle packages to your Windows devices, in addition to MSI apps. Use MSIX when you need app containerization, guaranteed clean install and uninstall, or when your app is already packaged for the Microsoft Store or sideloading.

An MSIXBundle (.msixbundle) is a container that holds multiple MSIX packages targeting different architectures or languages. Esper's deployment logic selects the package that matches the target device at install time, so you can upload one MSIXBundle instead of separate MSIX files per architecture.

Uploading an MSIX or MSIXBundle App

Step 1: Navigate to Apps and select your Windows Apps group.

Step 2: Click on Upload Apps.

Step 3: Select your .msix or .msixbundle file and wait for the upload to complete.

Once the upload finishes, Esper reads the package manifest and extracts its metadata. Click on the app, then click on Artifacts to view:

• Package Format: MSIX or MSIXBundle
• Package Family Name and Identity Name: the package's identity, as defined in its manifest
• Publisher: the certificate subject that signed the package
• Architecture: x86, x64, or ARM
• Entry Point Type: DesktopBridge for a converted Win32 app packaged in MSIX, or a native UWP entry point for an app built directly on the UWP platform
• Application User Model IDs (AUMIDs): one or more launchable entry points within the package. A package can expose multiple AUMIDs; Esper marks one as the default.

Note: The version name and version code shown for MSIX and MSIXBundle apps come directly from the package manifest and cannot be edited after upload.

With MSIX apps, admins can also manage dependencies and certificates from the Esper console. 

Managing Dependencies

MSIX apps can declare framework packages they require to run, rather than bundling every dependency into a single installer. If an app requires a dependency, ensure you upload it before deploying the app to devices.

Step 1: Open the app and click on Artifacts.

Step 2: Under Dependencies, click on Add Dependency.

Step 3: Upload the required framework package. Esper accepts .msix and .appx files for dependencies.

Currently, dependencies are not detected or resolved automatically. Check your app's documentation to confirm which framework packages it requires before deploying it to a blueprint.

Uploading a Signing Certificate

MSIX packages must be signed, and Esper requires the corresponding signing certificate before a device can install the package.

Step 1: Open the app and click on Artifacts.

Step 2: Under Signing Certificate, click on Upload Certificate.

Step 3: Upload the .cer file that corresponds to the publisher identity in the package manifest.

Only one certificate is allowed per version. If you upload a new version of the app, you'll need to upload its certificate separately.

Managing EXE Applications

Uploading an EXE Application 

Click on Upload Apps to upload an EXE application. After upload, an EXE file must be configured in order to be used in a blueprint or other places. EXE files require the following to be configured: 

• Version Code
• Install script
• Uninstall script
• Validation criteria: registry information or file path 

Once uploaded, the version will appear on the application’s details page with the following information: 

• Version Name: The version name. 
• Version Code: The version number. 
• Size: The size of the file. 
• Uploaded on: The date the file was uploaded.
• Description: An optional description. 
• Status: Once an EXE file has been configured, it’s considered active. Active files may be used in blueprints or other places where applications are installed. 

Activating the EXE Application Version

Click on the Actions (...) ellipsis button and select Edit EXE Configuration to configure scripts and other information for the EXE file. 

• Version Code: This number is usually prepopulated and is the numbered release of the app version.
• Install Script: Once this script reaches the device, the application will install according to the script’s specifications. Use the $INSTALLER_PATH variable to refer to the EXE installer location.
• Uninstall Script: Once this script reaches the device, or if there’s a problem with the initial install script, the application will uninstall according to this script’s specifications. 
• Verification Criteria: Define the criteria for a successful install or uninstall. After the install or uninstall command reaches the device, the console will report back on the command’s progress according to this criteria. There are two options: 
  • Registry Validation: Input the information displayed in Windows built-in Registry Editor. 
    • Registry Path: The path defined in the Registry Editor. 
    • Registry Key: The key name in Registry Editor. 
    • Registry Value: The value of the key in the Registry Editor. 
  • File Path Validation: Input the path where the file will be installed.

Once configured, the EXE version will appear in the console in a blueprint, on the device’s details page, and other places.

Deleting and Editing App Details 

Click on Actions > Delete Version to delete an app version. If that app version is part of a blueprint, you’ll need to remove it from the blueprint before deleting it. 

Click on Actions > Edit Description to edit the app description. 

Uploading Apps to Windows Devices

There are different ways to add applications to a device. When making changes to multiple devices, use a blueprint. 

You can also install the app to a group of devices from that group’s App Management section. 

Finally, you can use a script to add an application, including EXE apps.

Manage multiple Windows app versions under a single application, and deploy apps to devices using blueprints, groups, or scripts. These options give you the flexibility to manage app deployments at scale while maintaining control over versions. To get started, upload and deploy your enterprise Windows applications in the Esper console and ensure your devices have the tools they need to stay productive and compliant.