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 Resources. However, if you have tried deploying the application with Resources and you are not able to meet your needs, as an alternative method you can complete the deployment onto your devices using Product Provisioning.
Win32 Application Installation Behavior Using Resources
Refer the table to understand Win 32 Application Installation Behavior for all the apps that require admin privileges.
| Configuring Win32 Application from Resources | Install Context Settings In the Workspace ONE UEM console | User is an Admin | User is a standard user |
|---|---|---|---|
| Navigate to select Add Application | Navigate to and set
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. |
|
|
| Navigate to select Add Application | Navigate to and set
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. |
|
|
| Navigate to select Add Application | Navigate to and set
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. |
|
|
| Navigate to select Add Application | Navigate to and set
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. |
|
|
Win32 Application Installation Behavior Using Product Provisioning
It is a best practice to deploy Win 32 applications from Resources. However, if you have tried deploying the application with Resources 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
| 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 . |
Navigate toManifest tab and set
|
|
|
| Navigate to | Navigate to Manifest tab and set
|
|
|
| Navigate to | Navigate to Manifest tab and set
|
|
|
Considerations for Retry Count, Retry Interval, Install Timeout and Device Restart for your Win32 Applications
The values for Retry Count, Retry Interval, and Install Timeout options for Win32 applications affect the length the system takes to report a failed installation process. You can change the default values to decrease deployment times.
The default values for the options
- Retry Count - three times
- Retry Interval - five minutes
- Install Timeout - 60 minutes
work in the following sequence for a single failed installation process.
| 60 minutes (one hour) |
65 minutes (one hour and five min) |
125 minutes (two hours and five min) |
130 minutes (two hours and 10 min) |
190 minutes (three hours and 10 min) |
195 minutes (three hours 15 min) |
|---|---|---|---|---|---|
| Win32 app fails to install and reaches install the timeout of 60 minutes. |
System retries the installation (retry count #1) at a retry interval of 5 minutes. |
Win32 app fails to install and reaches install timeout of 60 minutes. | System retries the installation (retry count #2) at a retry interval of 5 minutes. |
Win32 app fails to install and reaches install the timeout of 60 minutes. | System retries the installation (retry count #3) at a retry interval of 5 minutes. |
After 3 hours and 15 minutes, the system reports a single application installation as failed. Then, the system installs the next application.
Configure Options Depending on the Application
Configure values that compliment the application.
Fast Installation Example
A browser application installs on a device in four minutes. Consider setting these values for this application.
- Retry Count - two times
- Retry Interval - five minutes
- Install Timeout - five minutes
The system reports the failure of this application within 20 minutes. Then, it installs the next application.
Slow Installation Example
A large productivity application installs on a device in 30 minutes. Consider these values for these applications.
- Retry Count - three times
- Retry Interval - five minutes
- Install Timeout - 35 minutes
The system might report the failure of this application within 120 minutes. Then, it installs the next application.
Considerations for Device Restart for your Win32 Applications
The values for Device Restart for Win32 applications allow the user to defer the device reboot and associate a deadline time up to which the user can defer the reboot. The values allow admins and end users to have more control over restarts to prevent a user from losing work. Admins can choose to force restart a PC after application installation or allow the user to postpone the restart for a more convenient time.
Device restart helps you configure the following settings:
- Prompt the user before the device restart so that they can save their file and close applications.
- Prompt the user when a device restart is required.
- Allows the user to snooze the device restart as per their convenience.
- Allows administrators to force the device restart.
- Allows administrators to set a deferral deadline after which the users cannot snooze the restart.
The Workspace ONE Intelligent Hub shows notifications regarding device reboots at various stages. The deferral notification allows the user to restart or snooze. Workspace ONE Intelligent Hub updates the reboot data for snooze or restart and shows that notification according to the time selected by the user.
| System Alert | Description |
|---|---|
| During the application installation | Notifies the user to save the files and close the application. |
| After application installation | Displays the first alert and notifies the user about the system restart. |
| 48 Hours before the restart deadline | Displays the second alert and warns the user about the force restart. |
| 15 minutes before the restart deadline | Displays the third alert and warns the user about the force restart. |
| 5 minutes before the restart deadline | Clear system prompts that indicate the date and time of the planned force restart. |
