Unified Application Management: Supported Configurations

Unified Application Management: Supported Configurations

Unified Application Manager (UAM) in Nerdio Manager allows for applications to be deployed to Azure Virtual Desktop (AVD) hosts and host pools, as well as Intune-enrolled Windows devices, including Windows 365 Cloud PCs and physical desktops and laptops. This document details the supported configurations for the general availability in the Nerdio Manager 5.0 release.


In the current release, UAM supports the following types of application repositories:

  • Read-only

  • Read/Write

Repositories may be configured from the Settings > Nerdio Environment > Unified Application Management tile. See Unified Application Management: Manage Applications for details.

Read-only Repositories

Read-only applications sources allow customers to deploy applications from the source, but do not allow for the uploading of applications or the modification of installation properties.

The currently supported read-only repositories are:

  • Microsoft Intune: Applications may be deployed from Intune to supported UAM devices.

  • The Microsoft Winget Public Repository: Applications may be deployed from the Microsoft Winget public repository to supported UAM devices.

Read/Write Repositories

Read/Write repositories allow customers to upload, manage, and deploy applications. For read/write sources, applications may be imported from:

  • The local desktop or a network share

  • The Microsoft Winget public repository

  • An internet location (URL)

  • Microsoft System Center Configuration Manager (private preview)

The currently supported read/write repository is:

  • Customer-created Private Winget Repositories: Applications may be deployed from customer-created private Winget repositories to supported UAM devices. Custom installation commands may be created for applications in customer-created private Winget repositories. Versioning is supported, and multiple versions of an application may be imported and deployed.

Application Deployment

Application deployment is achieved through either one-time deployments or via the creation of a policy.

When deploying an application, the administrator should search for the required application from the Unified Catalog page, Filtering by repository or vendor is possible to help narrow down the search results.

When creating a policy, administrators have the option to specify a maintenance window. If configured, application management tasks are only be performed during the maintenance window. This enables administrators to prevent application tasks from running during working hours and potentially affecting the user experience.

Policy assessment is performed on new AVD devices every 15 minutes. If a required application task is detected, this is performed against the device. If a maintenance window is specified, this task is not performed until the maintenance window is reached.

Tip: As a best practice, we recommend to the use of a maintenance window.

If stopped, application management tasks automatically start in-scope AVD desktops to perform the required tasks. The desktop is then returned to its original state after the task has been completed.

Track Application Status

The deployment status of applications can be tracked by performing the following steps:

To track an application status:

  1. Navigate to Applications > Deployment Policies.

  2. Optionally, select the Deployment policies or One-time deployments tab.

  3. Optionally, select Last Run date to see additional information.

Application policies perform assessment and compliance tasks until the device is confirmed to be compliant. If a device fails in the deployment of one or more application tasks in a policy, this device is skipped for re-assessment for a period of 24 hours, allowing the administrator to investigate the issue. Re-assessment and deployment tasks can be forcibly started against devices.

Note: If another tool is used to add or remove an application, this is not be reflected in the UAM policies console. In this event, the issue may be worked around by forcing an application policy to run and selecting Ignore current device state. This forces the task to perform all policy actions and creates your desired state configuration.

Intune-Specific Notes

  • Maintenance windows and drain mode are not supported for Intune devices. Tasks for Intune devices are run in accordance with the Intune agent’s scripted action assessment schedule.

  • Winget applications are deployed to Intune devices via the use of Intune scripts. As a result, these applications are not listed on the Intune applications page. The status of the applications should be reviewed from the UAM deployment policies’ Details… page.

  • Intune devices support policy-based deployment only. One-time deployments are not supported.

  • The Intune repository type currently supports MSI (Line of Business) & EXE (Win32) application types configured to install in the Device/System context. Support for additional application types will be added in future.

Application Formats

UAM supports the deployment of applications with .EXE, .MSI, and .MSIX file extensions. Additionally, we support the deployment of packaged .ZIP applications with a single .MSI, .EXE, or MSIX installer file included. These files are automatically detected.

Note: We recommend using applications that can be installed in both the Machine (aka System) and User context. If supported, the Machine context should always be selected when importing an application.

Known Issues

In rare scenarios, uploaded or imported applications may be recorded with the Winget Community repository ID. This can lead to policy failure messages. However, the application is installed. This can be resolved by using the correct application product code on the Import Application > Installer page. To discover the correct product code, please contact the vendor or refer to the original application manifest in the Winget public repository.

Some applications do not support fully silent installations or removals. In these scenarios, the application tasks fail. The application task can be validated locally by running the command Winget [install/remove] --id [Application.ID] --silent. If a silent operation is not performed, please contact the application vendor for assistance.

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Please sign in to leave a comment.