Unified Application Management: Manage Deployment Policies
Nerdio Manager allows you to manage Unified Application Management deployment policies.
Deployment of applications can be achieved via the deployment of an application policy, or via instant deployment from the host pool options menu. Support for individual host and image deployment will be added in future.
Policies may be created with multiple applications, and targeted to multiple host pools, both personal and pooled. A policy can include both install and uninstall tasks, however it is recommended that these are not mixed in a single policy.
Once a policy is created, it automatically begins the process of deploying the applications in the policy to the in-scope desktops. The status of individual desktops within the scope of the policy can be discovered from the detailed info menu option in the policy edit menu.
Note: Before you can create deployment policies, you must be sure that you have configured Nerdio Manager for Unified Application Management. See Configure Nerdio Manager for Unified Application Management for details.
Add a New Deployment Policy
Nerdio Manager allows you to add deployment policies.
To add a new deployment policy:
Navigate to Applications > Deployment policies.
Enter the following information:
Name: Type the policy's name.
Description: Type the policy's description.
Install/Uninstall: Select whether the deployment policy should install or uninstall the selected applications.
Applications: In the applications list, select Add new application, and then from the drop-down list, select the application to include in this policy.
You may add as many applications as desired.
Drag and drop an application in the list to change its order on the list.
Select the "X" next to an application to remove it from the list.
Reboot after installation: Select this option to place the host in drain mode and restart it when no sessions are present.
Note: This behavior applies to all targeted hosts. Ensure that this behavior does not conflict with your desktop capacity requirements.
Show favorites only: Select this option to only display applications marked as favorites. Otherwise, you may search the list of applications.
Select AVD or Intune.
In the deployment list, select Add new target, and then from the drop-down list, select the target type.
Personal: For personal host pools, optionally specify the user/group and host pool.
Pooled: For pooled host pools, optionally specify the host pool.
In the deployment list, select Add new target and specify the users/groups or device groups.
User or group: Optionally, specify the user(s) or group(s).
Device group: Optionally, specify the device group(s).
Concurrency balancer: From the drop-down list, select the desired concurrency balancer.
Maximum jobs: Type the maximum number of concurrent deployment jobs.
- Maintenance window: Optionally, toggle on this option configure a maintenance window.
Note: The maintenance window controls when application tasks are performed. If configured, no application tasks are performed outside of the specified window. This window allows tasks to be automatically performed only during specified hours, ensuring that the user experience is not disrupted.
Use pool maintenance window: Select this option to force the policy to run only during the configured maintenance window for the target pool(s).
Note: If no maintenance window is configured, the task respects the maintenance window set in this policy screen.
From the drop-down lists, configure the days and hours of the maintenance window.
Once you have entered all the desired information, select Save.
The new deployment policy is created.
Manage Deployment Policies
Nerdio Manager allows you to manage deployment policies. This includes editing, activating/deactivating, deleting, and more.
To manage deployment policies:
Navigate to Applications > Deployment policies.
Locate the deployment policy you wish to work with.
Optionally, perform any of the following:
Note: Detailed logging for the status of an application management task can be seen from the host, host pool, and policy details pages.
Select Edit to change the deployment policy.
From the action menu, select Deactivate to deactivate the deployment policy.
From the action menu, select Run now to request policy re-evaluation for in-scope desktops.
Ignore current device status: Optionally, select this option to force failed devices to re-attempt to apply the policy.
Note: By default, Nerdio Manager waits 24 hours before attempting to redeploy applications to allow administrators time to review the failure.
From the action menu, select Details... to view the deployment policy's detailed information. See Track Application Status below for details.
From the action menu, select Delete to delete the deployment policy.
In the Status column, select the button to toggle the activate (green) and deactivate(gray) status of the deployment policy.
The deployment status of applications can be tracked by performing the following steps:
To track an application status:
Navigate to Applications > Deployment Policies.
Locate the application you wish to work with.
From the action menu, select Details... to review the status of the individual devices in the scope of the policy.
Optionally, select Details to see additional information.
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.
In the Nerdio Manager 5.0 release, application policies perform assessment and compliance tasks until the device is confirmed to be compliant. Devices are not currently inventoried after a successful completion.
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 creating a new policy to perform the required action, or by editing the existing policy to match the current state of the device (for example, change an Install task to an Uninstall task), allowing the policy tasks to complete successfully, then converting the policy back to the actual desired state (for example, revert the uninstall task to an install task). This task then runs successfully and creates your desired state configuration.