Unified Application Management: Shell Apps Overview and Usage

The versatile Shell Apps feature offers the ability to create complex scripted deployment for Unified Application Management (UAM) deployment. Administrators can deploy multiple components via PowerShell and use the detection script feature to report success or failure information back to the UAM policy console for review.

This feature is intended for use with large or complex applications, or where deployment via Winget is not practical or desirable. Because the feature makes use of native PowerShell scripts, Winget can be called as part of an installation script if required.

Applications deployed using the Shell Apps feature are deployed exclusively in the device system context, avoiding the need for any service account.

This feature functions in a similar way to Nerdio Manager Scripted actions. If you are making use of scripted actions, there should be no complications when adopting the Shell Apps feature.

Prerequisites

PowerShell remoting (WSMan) must be enabled for the target devices.

Limitations

The Shell Apps feature is currently supported for global images, desktop images, AVD hosts, and server VMs.

Getting Started

First, you must link a Shell Apps repository. Then once you have linked a Shell Apps repository, navigate to Applications > Shell Apps, from the MSP level or the Account level, to work with the Shell Apps feature. See Unified Application Management: Manage Shell Apps for full details.

• Microsoft 365 apps and QuickBooks are included when you get started.

• Deployments are split into the following script areas: Detection, Install, and Uninstall. All components are required to form a valid application package.

• Each application package contains a switch labeled Public. This controls the application’s visibility within the UAM unified catalog page. It is recommended that this switch remains Off until you have completed your scripts, to avoid any potential deployment issues.

• From the MSP level, Shell Apps can be published to specific customer accounts. From the customer account level, they can be included in Deployment Policies.

• For customers who require a private repository, you can also create Shell Apps repositories at the customer level.