Workspace ONE UEM console includes different ways you can deploy Win32 applications. Select various installation combinations for software distribution or use product provisioning.

Product Provisioning Alternative

It is a best practice to deploy Win 32 applications from Apps & Books. However, if you have tried deploying the application with Apps & Books and you are not able to meet your needs, as an alternative method you can complete the deployment onto your devices using Product Provisioning.

Note: Users do not receive User Account Control (UAC) prompts for all the applications that only require standard permissions.

Win32 Application Installation Behavior Using Apps & Books

Refer the table to understand Win 32 Application Installation Behavior for all the apps that require admin privileges.

Configuring Win32 Application from Apps & Books Install Context Settings In the Workspace ONE UEM console User is an Admin User is a standard user
Navigate to Apps & Books > Applications > Native > Internal select Add Application Navigate to Deployment options > How To Install and set
  • Install Context = Device
  • Admin Privileges = Yes

The settings indicate that the app is configured for all the users on each of your devices and the user account has an elevated access token to install the application.

  • Install Context set to Device
  • Admin Privileges set to Yes
  • User is an admin
The installation completes without any prompt.
  • Install Context set to Device
  • Admin Privileges set to Yes
  • User is a standard user
The installation completes without any prompt.
Navigate to Apps & Books > Applications > Native > Internal select Add Application Navigate to Deployment options > How To Install and set
  • Install Context = Device
  • Admin Privileges = No

The settings indicate that the app is configured for all the users on each of your devices and the user account need not have an elevated access token to install the application.

  • Install Context set to Device
  • Admin Privileges set to No
  • User is an admin
The installation completes without any prompt.
  • Install Context set to Device
  • Admin Privileges set to No
  • User is a standard user
The installation completes without any prompt.
Navigate to Apps & Books > Applications > Native > Internal select Add Application Navigate to Deployment options > How To Install and set
  • Install Context = User
  • Admin Privileges = Yes

The settings indicate that the app is configured for all the users on each of your devices and the user account has an elevated access token to install the application.

  • Install Context set to User
  • Admin Privileges set to Yes
  • User is an admin
The installation completes without any prompt.
  • Install Context set to User
  • Admin Privileges set to Yes
  • User is a standard user
The installation fails.
Navigate to Apps & Books > Applications > Native > Internal select Add Application Navigate to Deployment options > How To Install and set
  • Install Context = User
  • Admin Privileges = No

The settings indicate that the app is configured for all the users on each of your devices and the user account need not have an elevated access token to install the application.

  • Install Context set to User
  • Admin Privileges set to No
  • User is an admin
The installation completes with prompt.
  • Install Context set to User
  • Admin Privileges set to No
  • User is a standard user
The installation fails.

Win32 Application Installation Behavior Using Product Provisioning

It is a best practice to deploy Win 32 applications from Apps & Books. However, if you have tried deploying the application with Apps & Books and you are not able to meet your needs, as an alternative method you can complete the deployment onto your devices using Product Provisioning.

If you are configuring Win32 applications using product provisioning, you can use the following table to understand the combinations of Install and Run manifest and the context of the command. You can select install or run at the system level, user level, or admin account level. Based on the selections made, your installation can vary.

Refer the table to understand the Win32 Application Installation Behavior Using Product Provisioning

Table 1. Win32 Application Installation Behavior Using Product Provisioning
Configuring Win32 Application Install/ Run Settings in the Products Provisioning in the UEM console User is an Admin User is a standard user

Navigate to Devices > Provisioning > Components > Files/Actions and select Add Files/Actions.

Navigate toManifest tab and set
  • Action(s) To Perform = Install/ Run
  • Execution Context = System
  • Action(s) To Perform = Install/ Run
  • Execution Context = System
  • User is an admin
The installation completes without any prompt.
  • Action(s) To Perform = Install/ Run
  • Execution Context = System
  • User is a standard user
The installation completes without any prompt.
Navigate to Devices > Provisioning > Components > Files/Actions and select Add Files/Actions Navigate to Manifest tab and set
  • Action(s) To Perform = Install/ Run
  • Execution Context = Admin
  • Action(s) To Perform = Install/ Run
  • Execution Context = Admin
  • The user is an admin
The installation completes without any prompt.
  • Action(s) To Perform = Install/ Run
  • Execution Context = Admin
  • User is a standard user
The installation completes with prompt.
Navigate to Devices > Provisioning > Components > Files/Actions and select Add Files/Actions Navigate to Manifest tab and set
  • Action(s) To Perform = Install/ Run
  • Execution Context = User
  • Action(s) To Perform = Install/ Run
  • Execution Context = User
  • User is an admin
The installation completes without any prompt.
  • Action(s) To Perform = Install/ Run
  • Execution Context = User
  • User is a standard user
The installation fails.