Installing Win32 Apps (exe) on Windows 10 and above Managed Devices
  • 06 May 2024
  • 7 Minutes to read
  • PDF

Installing Win32 Apps (exe) on Windows 10 and above Managed Devices

  • PDF

Article summary


Generally most enterprise software for Windows offer a MSI installer that can be deployed via MDM's easily. However there are still a lot of publishers that do not offer an MSI package for their apps and offer EXEs that need to be installed on the devices. These can be in-house enterprise applications, utility software etc. To allow IT Admins to easily deploy them via MDM, Scalefusion offers the ability to upload and publish Exe installers to the managed Windows 10 and above devices.

If you are looking to deploy MSI packages or UWP app bundles, then please refer to our Installing Enterprise Applications guide.

Deploying executable (exe) based installers is a little different than deploying MSI files. It requires the IT Admins to prepare some information related to the Exe before they upload to Scalefusion and initiate the remote deployment. Here we detail the pre-requisites and the steps to install an executable (exe) via Scalefusion Dashboard to Windows 10 and above managed devices.

Important Note

For remotely installing executable (exe) based applications, the Scalefusion agent needs to be updated to v1.0.3 and above. Scalefusion agent can be updated from Application Management > Scalefusion Apps


  1. Scalefusion Account
  2. Windows 10 and above Test machine: Used to find information about the Exe that needs to be installed.
  3. Windows 10 and above managed device: The actual managed device where the exe will be remotely installed.
    1. Scalefusion MDM agent v1.0.3 or above

Parameters required for Remote Installation of Executables (EXEs)

The first step before you upload the exe to Scalefusion, is to get all the required information about the executable that you plan to remotely install. The easiest way to figure out this information is basing on the publisher/developer documentation or installing the application on a test machine and then get the information. Below is the information that needs to be collected,

  1. Version & Logo of the App: Scalefusion cannot extract the version and logo from the exe. Hence you would first need to get the version of the app to be installed and the logo. Logo is optional, however version info is important.
  2. User Level Installation vs Device Level Installation: The first thing to find out is whether this app installs at a per-user level or installs at a device level. Typically this information is given by the publisher/developer of the app. Generally applications that install to Program Files(x86) or Program Files are device level installers and the ones that install to AppData/Local/Programs or AppData/Roaming/Programsare installed for the current user.
    1. Example of a Device level installer: Notepad++
    2. Example of a User level installer: Opera
  3. Background vs Foreground Installation: For applications that do not support silent installation (offer no silent installation switches or installation arguments) they cannot be installed without user interaction. These apps need to be installed in Foreground installation mode as user interaction is required to complete installation. For applications where you have the silent installation arguments they can be set to Background installation and in such cases you would have to specify the silent install switches as installation arguments.
  4. Installation Arguments:You would need to find out if the application supports silent installation. Normally an application that supports silent installation provides the silent installation arguments. Typically they are /quiet, /S or /silent, but they vary from app to app, so it is important to get this information. Some examples are,
    1. Notepad++: /S
    2. Opera: /silent
  5. Uninstall Program & Uninstall Parameter: For EXEs to be uninstalled, Scalefusion agent needs to know the program that can uninstall the app and also the uninstall parameter. These are typically made available by the publisher/developer or can be found out once the app is installed on the test machine. Some examples are,
    1. Notepad++:
      1. Uninstall Program Path: C:\Program Files (x86)\VideoLAN\VLC\uninstall.exe
      2. Uninstall Argument: /S
    2. Opera:
      1. Uninstall Program Path: %Local%\Programs\Opera\Launcher.exe
      2. Uninstall Argument: /uninstall
  6. Detecting Installation: For Scalefusion to detect that the app has been installed or un-installed, you would have to let us know what are the indicators for the same. The indicators can be the presence of a file or a folder or a registry key. Foe example,
    1. Notepad++: The presence of the file C:\Program Files (x86)\Notepad++\notepad++.exe indicates that the app is installed.
    2. Opera: The presence of folder %Local%\Programs\Operaindicates that the app is installed.
The installation rules also act as a rule for detecting uninstallation of the app.

Uploading and Installing Executables (Exe)

Once you have collected all the information about the application to be remotely installed, the next step is to upload it to Dashboard. In this section we would see how to upload an executable that has the silent install switches available and can be installed silently. We would use Notepad++ for our example.

  1. Navigate to Application Management > Enterprise Store and select Upload New App > Upload Windows App
  2. App Type: Select Exe to upload the executable
  3. App Name, Version & Logo: In the first section, fill in the Name of the application, the version & logo. Logo is optional. Once done click Next
  4. App Upload: In this step upload EXE file of the application. Depending upon the app you may have a single installer for 32 & 64 bit architecture or separate installers. Click Next
    Enterprise Plan customers get the ability to upload EXEs from external storage links which helps in distributing files upto 1GB.
  5. Installation Mode, Installation & Uninstallation Arguments: In this section select the app installation mode, the installation arguments and the uninstall information. This is the information that you have collected by following developer/publisher documentation or installing this app on a test machine. Click Next once done
    1. App Installation Mode:
      1. Run As Background: Select only if the app can be installed silently in the background and you know the silent install arguments.
      2. Run As Foreground: Select this if you want to prompt the users to install the application or the application does not support silent installation.
    2. Installation Target: Basing on the app installation level select either Device Level or User Level.
    3. Installation Argument: This is mandatory if you have selected installation mode as Run As Background. Provide the silent installation switch and any other arguments that you want to pass to the installation process.
      You can add more than one argument if the app takes other configuration arguments.
    4. Uninstallation Path: Provide the path of the program that would help in the uninstallation.
      The Uninstallation path always should end with .exe
    5. Uninstallation Argument: Provide the silent uninstallation argument.
  6. App Detection Rules: Provide the app detection rules that would help Scalefusion agent detect when the app is installed or uninstalled. Click SAVE, to upload the application to Scalefusion.
  7. Select the Device Profiles, where you want to install this application and click PUBLISH
Once installed, the App Details (Installation Mode, Installation Target, Installation & Uninstallation Arguments) and App Detection Rules can also be edited later if Scalefusion MDM agent v2.0.2 or above is installed on devices. To edit, click on the pencil icon next to the exe file's app version that is displayed in the right side panel.

End user experience for Background Application Installation

Applications deployed with Run As Background installation mode would be silently installed and there would be no user notification.

End user experience for Foreground Application Installation

Applications deployed with Run As Foreground installation mode cannot be silently installed and the users would be shown a prompt to start the installation. Once the end users start the installation, the default install wizard of the application is launched. In the screenshot below we see a prompt for Opera online installer.

NOTE: If the device belongs to an Assigned Access (Allowed apps) Profile then the application that is installed irrespective of whether it was silent or otherwise, would not be visible on the desktop until the changes to the Device Profile are done.

Updating Assigned Access (Allowed Apps) Profile

If the devices where the application is being installed belong to a profile where the application policy is set to Assigned Access/Allowed apps then the application needs to be enabled and the path has to be provided before the users see it on their desktop. To do so, please edit the Device Profile and provide the path of the newly installed application.

The Application is shown in the Device Profile after it is installed on at-leat one device and the path of the installed app is updated after a periodic sync which happens at logoff/login or a restart.

Frequently Asked Questions

Question: How do we check the status of a published application?

Answer: Use the View Status option.The View Status option provides the status of installation.

The statuses are,

  • Downloading
  • Download Failed
  • Download Completed
  • Installing
  • Install Failed
  • Installed

Question: The application has been published but it is not yet installed?

Answer: Ensure that latest Scalefusion agent has been published and the device is connected to internet. Once installed the status some time may take around 3 hours or a logoff/login to be updated on dashboard.

Question: We see that a user-level installer gets installed to all the users when they login. Is this expected?

Answer: Yes, since we don't have a target user that can be specified, the applications are installed for every user on the device when they login even though they are user level installers.

Question: How do we update an existing application OR when we upload a new version of earlier uploaded app, why do we see a new entry in the Enterprise Store?

Answer: Updating the applications of type executables is a little different than UWP or MSI apps. To update an existing application please use the following option only to avoid duplicate entries being created.

Question: What is the difference between Delete and Delete and uninstall?

Answer: If you would just want to delete the file from Dashboard, but keep the instance of app installed and running on the devices then select Delete. If you would want to uninstall the application as well then select Delete & Uninstall.

Please note that if you select Delete & Uninstall then the Scalefusion agent would uninstall the application even if the you or end user locally install it again.

Was this article helpful?