While configuring the Win32 applications in the Workspace ONE UEM console, you have different combinations that you can select while setting the Install Context and Admin Privileges under the Deployment tab. Your installation process can vary based on the settings.

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. For more information, see Win32_Application_Installation_Behavior_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 toApps & Books > Applications > Native > Internal and 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.

With the

Install Context set to Device, and the

Admin Privileges set to Yes and if the user is an admin. The installation completes without any prompt.

With the

Install Context set to Device, and the

Admin Privileges set to Yes and if the user is a standard user, installation completes without any prompt.

Navigate toApps & Books > Applications > Native > Internal and 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.

With the

Install Context set to Device, and the

Admin Privileges set to No and the user is an admin. The installation completes without any prompt.

With the

Install Context set to Device, and the

Admin Privileges set to No and the user is a standard user, installation completes without any prompt.

Navigate toApps & Books > Applications > Native > Internal and 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.

With the

Install Context set to User, and the

Admin Privileges set to Yes and the user is an admin. The installation completes without any prompt.

With the

Install Context set to User, and the

Admin Privileges set to Yes and the user is a standard user, installation fails.

Navigate toApps & Books > Applications > Native > Internal and 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.

With the

Install Context set to User, and the

Admin Privileges set to No and the user is an admin. The installation completes with prompt.

With the

Install Context set to User, and the

Admin Privileges set to No and the user is a standard user, 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. To review the Win32 Application Installation Behavior using Apps & Books, see Win32_Application_Installation_Behavior_using_Apps_&_Books.

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

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 > Staging & Provisioning > Components > Files/Actions and select Add Files/Actions.

Navigate to Manifest tab and set Action(s) To Perform = Install/ Run

Execution Context = System

With the

Action(s) To Perform = Install/ Run and Execution Context = System and the user is an admin. The installation completes without any prompt.

With the

Action(s) To Perform = Install/ Run Execution Context = System and the user is a standard user, installation completes without any prompt.

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

Navigate to Manifest tab and set Action(s) To Perform = Install/ Run

Execution Context = Admin

With the

Action(s) To Perform = Install/ Run, Execution Context = Admin and the user is an admin. The installation completes without any prompt.

With the

Action(s) To Perform = Install/ Run, Execution Context = Admin and the user is a standard user, installation completes with prompt.

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

Navigate to Manifest tab and set

Action(s) To Perform = Install/ Run

Execution Context = User

With the

Install Context Action(s) To Perform = Install/ Run, Execution Context = User and the user is an admin. The installation completes without any prompt.

With the

Action(s) To Perform = Install/ Run, Execution Context = User and the user is a standard user, installation fails.