With your desktop images in place, the next step is to create host pools - the pools of session hosts your users will actually connect to - and configure how they're built, scaled, and assigned.
After you create the desktop images, the next step in the Nerdio Manager AVD deployment flow is to create host pools from the desktop images.
Host pools are groups of identical Azure VMs that host the Azure Virtual Desktops that end users sign in to. All VMs in the host pool share a set of configuration options: VM size, OS disk size, base image, AD domain, user profile storage location, and more.
You can configure two types of host pools:
-
Static: A static host pool contains a set number of session hosts that the administrator configures. That is, it does not have auto-scale enabled.
Note
When Nerdio Manager is first deployed to an existing environment, the host pools that are created are static host pools. They can be converted to dynamic host pools.
-
Dynamic: A dynamic host pool is a host pool whose configuration can be scaled in and out (auto-scale) as per the workload. That is, auto-scale can create the session hosts automatically based on the auto-scale configuration.
-
Hybrid: A hybrid host pool is configured for use with both session hosts in Azure and session hosts on-premises, connected via Azure Virtual Desktop for Azure Local.
See also
A workspace is a container for host pools and session hosts that provide desktops and RemoteApps to users. This topic discusses creating and managing workspaces.
A workspace must be created before you can create host pools and session hosts.
To create a workspace:
-
Navigate to Cloud Desktops > Azure Virtual Desktop > Workspaces.
-
Select Add Workspace.
-
Enter the following information:
-
Name: Type the workspace's name.
Note
The Name is assigned to the workspace during creation and cannot be changed later. By default, it is visible to the end-user. Specifying a Friendly Name overrides what is visible to the end-user.
-
Friendly Name: Type the Friendly Name.
-
Description: Type the description, which is only visible to admins.
-
Resource group: From the drop-down list, select the resource group to contain the workspace.
-
Location: From the drop-down list, select the Azure location for the workspace's objects and associated metadata.
-
Apply tags: Optionally, type the Name and Value of the Azure tag to apply to the Workspace.
Note
You may specify multiple tags. See this Microsoft article for details about using tags to organize your Azure resources.
-
-
Once you have entered all the desired information, select OK.
The workspace is created.
From the Workspaces table, you can do the following:
-
Host Pools: Manage the workspace's dynamic host pools.
-
Static host pools: Manage the workspace's static host pools.
-
Unassign: Unassign the workspace from Nerdio Manager.
-
Delete: Delete a Workspace.
Note
You may only delete a workspace that has no host pools.
-
User Sessions: Manage the workspace's user sessions.
The following procedure allows you to create a new dynamic host pool.
To create a new dynamic host pool:
Note
Many fields in this wizard have an info tooltip alongside the field label. Reference these tooltips for more information about each option.
-
Navigate to Cloud Desktops > Azure Virtual Desktop > Workspaces.
-
Select the workspace you wish to work with.
-
Select New host pool.
A dialog opens titled Add Host Pool. It contains the following sections: Basics, VM Template, Active Directory, FSLogix, RDP, Tags, Application policies.
Enter the following information:
Note
For several of the required parameters, you may filter the available choices by using the Resource Selection Rules. For example, you may filter the VM Size or OS Disk choices for Intel RAM-optimized VMs only. See Resource Selection Rules Management for details.
-
Name: Enter the name of the host pool.
-
Description: Enter the host pool's description.
Note
Optionally, select Generate using AI to have AI create the description. See Overview of AI-Powered Description Generation for details.
-
Resource Group: From the drop-down list, select the resource group for the host pool.
-
Host type: From the drop-down list, select the host type (Azure Cloud, Azure Local, or Nutanix).
-
Host pool type: Select Dynamic.
-
Desktop Experience: From the drop-down list, select the desktop experience.
-
AVD multi-session desktop (pooled): This is the full desktop experience. Users are not assigned to individual session hosts and are placed on a host based on its load. Multiple users are pooled together on a group of hosts.
-
AVD multi-session RemoteApp (pooled): This is only published applications, not a full desktop experience. Published RemoteApps are visible to users as native apps running on their local computer. The RemoteApps are provided by a collection (pool) of session hosts.
-
AVD single-session desktop (pooled): This is the full desktop experience. Users are placed on individual desktop VMs (one user per session host) and a preconfigured number of spare(available) desktops is maintained.
-
AVD single-session desktop (personal): This is a personal (persistent) full desktop experience. A dedicated session host VM is assigned to each user.
-
-
When you select AVD single-session desktop (personal) as the Desktop Experience, you need to configure the following additional features:
-
Assignment Type: Select how the desktop is assigned to the user.
Note
Before users can sign into a personal desktop, they need to be pre-assigned to the VM.
-
Optionally, select Assign multiple desktops to a single user.
Note
Selecting this option allows multiple desktops to be assigned to a single user for this host pool. This setting CANNOT be disabled after being enabled, and is only available for direct assignments. For more details, see Configure personal desktop assignment.
-
-
App group name: Optionally, enter the app group name of the host pool.
-
Validation environment: Select this option to receive service updates at a faster cadence than non-validation host pools, allowing you to test service changes before they are deployed broadly to production.
-
Quick Assign: From the drop-down list, select the users or groups to pre-assign to newly created desktops.
Select Next.
-
Name: Type the name of the newly added hosts for Prefix or the Prefix+Pattern.
-
Prefix/Pattern: From the drop-down list, select whether to use a Prefix or a Pattern.
-
Prefix can be used when creating multiple session hosts. The Prefix limit is 10 valid, Windows computer name characters. When using a Prefix, a unique suffix is automatically appended in the format "-xxxx", where xxxx are 4 random alphanumeric characters. For example: AVDHOST-s72h. Do not add a "-" to the Prefix.
-
Pattern can be used to specify an advanced naming convention for new hosts. Pattern characters must be enclosed in {} and can be # (for sequential numbers) and/or ? (for random alphanumeric characters). One # implies numbers from 0 to 9, two #s implies numbers of 0 to 99, etc.
-
Example 1: AVDHOST{###} (AVDHOST000..AVDHOST999).
-
Example 2: AVDHOST-{???} (AVDHOST-d83, AVDHOST-7sl, etc.).
-
-
-
-
Network: From the drop-down list, select the network. The network determines the Azure region of the VM.
Note
Nerdio Manager verifies that there is a sufficient number of available IP addresses on the selected network before deploying new host pool VMs. If there are insufficient available IP addresses, an error message is displayed and you may not add the new host pool.
-
Desktop Image: From the drop-down list, select the desktop image that is used as the golden image for newly created session hosts.
-
VM Size: From the drop-down, select the VM disk size and type for newly created session hosts.
Note
If any VM size is not available for a subscription or region, it doesn't appear in the list. At times, even if a VM size is available in a specific Azure region, it cannot be used due to the subscription having restrictions on a particular size. In such cases, we show the VM size in the drop-down list, but don't allow users to select it (the size is disabled).
-
OS Disk: From the drop-down list, select the OS Disk type and size for newly created session hosts.
Note
This must be equal to or larger than the size of the Desktop Image selected above. Using Standard HDD (S-type) is not recommended. Premium SSD provides best performance.
-
Resource Group: From the drop-down list, select the resource group to contain the VMs.
Select Next.
-
Directory profile: From the drop-down list, select Default, one of the Predefined global configurations, or Custom.
Note
Default always uses the application's global default AD configuration, so it stays in sync if that default is later changed. Selecting a Predefined configuration locks in that specific saved configuration, even if the global default changes afterward. Select Custom to provide a configuration specific to this host pool.
-
Directory type, Domain (FQDN), Service account (UPN), Service account password, and Organization unit: These fields are populated automatically from the selected directory profile and remain read-only unless Custom is selected for Directory profile, in which case they become editable. Specify the Organization unit as a Distinguished Name (DN) path if session hosts should be created in a specific OU; leave it blank to use the Computers container.
Select Next.
-
FSLogix: From the drop-down list, select the FSLogix configuration profile to be used when creating or re-imaging hosts in this host pool.
-
FSLogix Profiles: Select the toggle to enable FSLogix profiles.
Note
If this option is not enabled, Nerdio Manager does not install the FSLogix profile container application on newly created VMs when they are deployed in this host pool.
-
Configuration: From the drop-down list, select an existing profile, or select Custom to configure the settings below yourself.
Note
Selecting an existing profile automatically completes the configuration with that profile's settings, which cannot be edited here. Selecting Custom lets you configure the profile as required.
-
Version: From the drop-down list, select the FSLogix version.
-
Configure session hosts registry for Entra ID joined storage, Exclude the local admin accounts from FSLogix, and Exclude domain accounts from FSLogix: Select any of these options as needed, and enter applicable domain accounts in the Domain accounts field.
-
FSLogix profiles path (VHDLocation): Select Override to specify a custom profile storage location instead of the default.
-
Configure Office Container to redirect Microsoft Office user data (ODFC): Select this option to redirect Office container data, and specify the FSLogix Office Container path (VHDLocation) if overriding the default.
-
FSLogix cloud cache: Select the toggle to enable FSLogix Cloud Cache, which replicates profiles asynchronously across multiple storage locations for resiliency.
Tip
For performance reasons, it is strongly recommended that you use Premium SSD and Ephemeral OS disks when Cloud Cache is enabled.
-
Manage App Service settings and Manage Log settings: Select either option to edit the corresponding FSLogix registry settings.
-
FSLogix Registry Options: From the Edit mode drop-down list, select All settings or Advanced, then configure individual registry values across the Profile Settings, ODFC Settings, Cloud Cache Settings, App Service Settings, and Log Settings tabs. Use the Search settings by name box to filter.
Note
See FSLogix per-host pool customization for the full list of configurable registry settings.
Select Next.
-
RDP Profile: From the drop-down list, select the RDP profile.
Note
This step also includes RDP Shortpath network settings and, for a Custom profile, individual redirect and session options. See Host Pool Custom RDP Configuration for more information.
Select Next.
-
Tag groups: Optionally, from the drop-down list, select an existing tag group. Selecting a tag group auto-populates the Name and Value fields below with its predefined values.
-
Apply tags: Optionally, type the Name and Value of the Azure tag to apply to the host pool.
Note
You may specify multiple tags. See this Microsoft article for details about using tags to organize your Azure resources.
-
Add "cm-resource-parent" tag: Select this option to add the "cm-resource-parent" tag to the host pool.
-
Select Next.
-
Application policies: Optionally, select the application policies to assign to the host pool.
Note
This step displays a notice that host pool creation runs as a background task.
Once you have entered all the desired information, select Submit.
You are redirected to the new host pool's auto-scale settings page. If desired, configure the auto-scaling for the host pool. See Enable Dynamic Host Pool Auto-scaling for more information.
The process of host pool creation begins. If auto-scaling has been enabled, it may take some time to complete. Otherwise, the host pool is created immediately. This creates an "empty" host pool – there are no session hosts in that host pool. An end-user who attempts to connect to the empty host pool is informed that there are no resources (that is, session hosts) to serve up a desktop. You can monitor progress in the Host Pools Tasks section.
Related Topics
Host pool profiles simplify the creation of new host pools by letting you define reusable profiles for auto-scale settings, FSlogix settings, RDP settings, and directory settings. When configuring any of these for a host pool, you can select a predefined profile. This eliminates the need for manual configuration for each pool or schedule.
Note
Auto-scale profiles are available only in the Nerdio ManagerPremium edition.
Complete the following steps to create a new host pool profile.
To create a profile:
-
Navigate to Settings > Profiles Management.
-
In the Profiles area, select New profile.
-
Select the profile you wish to create:
-
Auto-scale: Enter the following information:
-
Auto-scale mode: From the drop-down list, select the auto-scale mode.
The following modes are available:
-
Shared: For all pooled dynamic hosts pools.
-
Schedule-based (Personal): For single user desktop personal host pools with auto-scaling that is performed as per the specified schedule.
-
User-driven (Personal): For single user desktop personal host pools with auto-scaling that is performed when there are no active or disconnected sessions.
-
-
Name: Enter the profile name.
-
Description: Enter the profile description.
-
For all the other parameters, see the relevant article:
-
For pooled dynamic host pools: Enable Dynamic Host Pool Auto-scaling.
-
For single user desktop personal host pools: Enable Personal Host Pool Auto-scaling.
-
-
-
Directory: Complete the steps as described in Configure the Host Pool's Active Directory Settings.
-
RDP: Complete the steps as described in Configure RDP Settings Profiles.
-
FSLogix: Complete the steps as described in FSLogix settings and configuration.
-
-
Once you have entered all the desired information, select Save.
Once you created a host pool profile, you can assign it to relevant host pools.
To assign a profile to a host pool:
-
Navigate to Settings > Profiles Management.
-
From the action menu, select Assignments, then New assignments.
-
Enter the following information:
-
Auto-scale profile: From the drop-down list, select the auto-scale profile.
-
Schedule type: From the drop-down list, select the schedule type.
-
RDP profile: From the drop-down list, select the RDP profile type.
-
FSLogix profile: From the drop-down list, select the FSLogix profile type.
-
AD profile: From the drop-down list, select the AD profile.
-
Host pools: From the drop-down list, select the host pool(s).
-
Stop on first failure: Each host pool is processed one at a time. Select this option to cancel the remaining operations on the first failure.
-
-
Once you have entered all the desired information, select Save.
Note
You can perform the following on auto-scale profile assignments:
-
Edit selected Alternative: Select this to edit an alternative schedule.
-
Remove selected: Select this option to remove selected assignments.
-
You can manage existing host pool profiles.
To manage profiles:
-
Navigate to Settings > Profiles Management.
-
Locate the host pool profile you wish to work with.
-
Select the from the following:
-
Select the pencil
icon to edit the profile.
-
Select the more actions
menu, for the following options:
-
Assignments: Edit the assignments.
-
Set default: Sets the profile as default.
-
Clone: Create a clone of the profile.
-
Delete: Delete the profile.
-
-
You can compare two existing host pool profiles.
To compare profiles:
-
Select the profiles you want to compare.
-
Select Compare.
-
Optionally, select Show only different to display only the properties that differ between the two profiles. Select Show all to return to showing all properties, including those that are identical between the two profiles.
The Auto-scaling feature ensures that only the number of session host VMs required to serve the current demand are running. When not in use, VMs are stopped or deleted. When demand rises, or at specific times of the day, additional VMs in the host pool are started or created. This allows for cost savings.
You can enable and configure Auto-scaling for dynamic host pools.
Note
By default, the Auto-scale option is disabled. When you enable Auto-scaling, you can configure the desktop image, VM size, and OS disk template, and also set the criteria for host pool sizing, scaling logic, and pre-stage hosts.
To enable dynamic host pool Auto-scaling:
-
Locate the dynamic host pool you wish to work with.
-
From the more options
menu, hover over Auto-scale , and select Configure.
-
Enter the following basic auto-scale information:
-
Auto-Scale: Toggle this option to Enabled.
-
Auto-scale Timezone: From the drop-down list, select the time zone for the auto-scale process.
-
Name: Type the name of the newly added hosts for Prefix or the Prefix+Pattern.
-
Prefix/Pattern: From the drop-down list, select whether to use a Prefix or a Pattern.
Note
-
Prefix can be used when creating multiple session hosts. The Prefix limit is 10 valid, Windows computer name characters. When using a Prefix, a unique suffix is automatically appended in the format "-xxxx", where xxxx are 4 random alphanumeric characters. For example: AVDHOST-s72h. Do not add a "-" to the Prefix.
-
Pattern can be used to specify an advanced naming convention for new hosts. Pattern characters must be enclosed in {} and can be # (for sequential numbers) and/or ? (for random alphanumeric characters). One # implies numbers from 0 to 9, two #s implies numbers of 0 to 99, etc.
-
Example 1: AVDHOST{###} (AVDHOST000..AVDHOST999).
-
Example 2: AVDHOST-{???} (AVDHOST-d83, AVDHOST-7sl, etc.).
-
-
-
-
Network: From the drop-down list, select the network the VM connects to.
Note
The VM that is created on the selected network is created in the Azure region associated with the network.
-
Additional subnets: From the drop-down list, select additional subnets within the same virtual network.
Note
If a particular subnet does not have enough IP addresses when scaling out,then the next subnet will be chosen automatically when creating additional session hosts.
-
Network distribution: From the drop-down list, select how the load is distributed across the network.
Note
Select Depth first to distribute the load to nodes one after another in a fixed order, or, for optimal distribution, select Breadth first to balance the load proportionally based on current resource usage.
-
Desktop Image (template): From the drop-down list, select a desktop image to be used as the golden image for new session hosts.
-
Use the "staged" image version: Select this option to use the staged image version, if available, when scaling the host pool.
-
VM Size (template): From the drop-down list, select the VM size for new session hosts.
-
Running OS Disk (template): From the drop-down list, select the OS disk type and size for new session hosts.
-
Stopped OS disk type: From the drop-down list, select the OS disk type when session host VMs are stopped.
Note
See Auto-Scale Cost Optimization OS Disk Storage for more information about OS disk auto-scale configuration.
-
Resource Group: From the drop-down list, select the resource group where VMs should be created.
-
VM Naming: From the drop-down list, select the VM naming to use.
Note
Host VMs that are created automatically by the scale out or auto-grow process use names based on the selected VM naming mode. See How Session Host VM Names are Generated for more information.
-
Re-use names: Always attempt to re-use names that were previously used in the pool, if available.
-
Standard names: Use the next available name.
-
Unique names: Always attempt to use a unique name for new hosts.
-
-
Automatically Re-image Used Hosts: Select one of the following options from the dropdown:
-
Disabled: No re-imaging takes place.
-
Always: Hosts that had at least one user signed in to them are re-imaged. For multi-session hosts, the hosts are re-imaged as soon as the last user signs out.
-
During scale-in restrictions only: Re-imaging occurs only within the configured scale-in restriction period, mitigating the risk of reduced session capacity on the host pool at other times.
-
-
Scaling interval: From the drop-down list, select the time interval.
-
Schedule type: Select the Default schedule or Alternative schedule.
-
Select the Default schedule or Alternative schedule.
Note
Nerdio Manager allows you to configure separate auto-scale settings for a default schedule (normal operations) and an alternative schedule (outside of normal operations). For example, you may want fewer session hosts available on weekends or bank holidays. Alternatively, you may want more session hosts available two weeks prior to Christmas when you have a large number of temporary customer support agents. In either case, you would use the Alternative schedule area to configure the auto-scale settings for those periods that are outside of normal operations.
-
To create an alternative schedule, select Alternative schedule, and enter the following information:
Note
The Estimated Monthly Costs shown at the top of this page only consider the Default Schedule's settings.
-
Schedule: Toggle this option to Enabled.
-
Days: From the drop-down list, select the off-peak day(s).
-
Dates: Select the specific off-peak date(s).
-
Select + or - to add or remove off-peak dates.
-
-
-
Select the Auto-scale profile (Premium only):
-
From the drop-down list, select the auto-scale profile to use. Alternatively, select Custom to create a custom auto-scale configuration.
Note
For more details, see Manage Auto-scale Profiles.
-
-
-
Enter the following Host Pool Properties information:
-
Session limit host: Type the maximum number of sessions per host. Once this session limit is reached, and there are no more available hosts, a new host is started automatically, if it exists.
-
Load Balancing: From the drop-down list, select the desired load balancing.
Note
-
Breadth First means that the load-balancing algorithm spreads the users evenly across all available session hosts.
-
Depth First means the load-balancing algorithm places all the users in the first session host until the host's session limit is reached. Only then, does it place the users in the next session host. If necessary, it powers on the VM and makes it available to the users.
-
-
Start VM on connect: Select this option to start the session host VMs on connect.
-
-
Enter the following Host Pool Sizing information:
-
Active Host Defined As: From the drop-down list, select the active host definition.
Note
When set to “VM started,” the system identifies a session host VM as active as long as the VM is running in Azure. There are very few instances when "VM started" should be selected.
When set to “AVD Agent Available,” the system identifies a session host VM as active only when the AVD back-end is receiving heartbeats and sees the session host as “Available.” In general, you should select "AVD Agent Available.”
-
Base Host Pool Capacity: Type the number of session host VMs to always be part of this host pool. These session hosts may be stopped or running.
-
Min Active Host Capacity: Type the minimum number of running session hosts that are always available. Typically, a session host must be running for users to sign in or the "Start on connect" feature is enabled. Other VMs can be either stopped or turned on, as configured by the user auto-scaling logic.
-
Burst Beyond Base Capacity: Type the capacity to burst above the standard number of session host VMs when there is user demand. The system automatically creates up to this number of new session host VMs above the Base Host Pool Capacity, when needed. These session hosts are the first ones to be removed when the system scales in after business hours.
-
-
Enter the following Scaling Logic information:
-
Use Multiple Auto-scale Triggers: Select this option to enable multiple usage triggers to be used for scaling out and scaling in. When enabled, you can configure the number of hosts in a group to scale out or scale in.
Note
The multiple auto-scale triggers feature is available only in the Nerdio Manager Premium edition.
Note
-
Auto-scale adds capacity when any of the scale out conditions are met. Capacity is removed only when all the scale in conditions are met.
-
Use the + and - buttons to add or remove scale out triggers. You may select up to 3 triggers.
-
-
Select Auto-scale Trigger: From the drop-down list, select the auto-scale trigger.
Note
The available triggers are:
-
CPU usage or RAM usage: This scales out when the average CPU or RAM usage across all running session hosts in the pool exceeds a predefined value for a predefined duration.
-
Average active sessions: This scales out when the average number of active sessions per host exceeds a predefined value.
-
Available sessions: This maintains the number of available hosts by scaling out and scaling in within the limits of the Host Pool Sizing and the maximum number of sessions per host.
-
User-driven: Hosts are started when users connect and are automatically stopped after a defined amount of time after all users sign out.
-
-
For CPU usage or RAM usage:
-
Start or Create (Scale Out) Up To: Scale out by starting (if there are stopped VMs) or creating (if there are no stopped VMs) session hosts if the trigger is exceeded.
-
Stop or Remove (Scale In) Up To: Scale in by stopping (if there are no burst VMs) or removing (if there are burst VMs) session hosts if scale in trigger is met.
-
-
For Average active sessions:
-
Start or Create (Scale Out) Up To: Scale out by starting (if there are stopped VMs) or creating (if there are no stopped VMs) session hosts if the average active sessions across all hosts is exceeded.
-
Stop or Remove (Scale In) Up To: Scale in by stopping (if there are no burst VMs) or removing (if there are burst VMs) session hosts if if the average active sessions across all hosts is below the number specified.
-
-
For Available sessions:
-
Maximum sessions per host: Type the maximum sessions per host.
-
Maintain up to X available sessions: Type the number of sessions that must be available either always or during work hours.
Note
This ensures that there are this many available sessions during work hours or at all times. Work hours start at Start of work hours specified in the Pre-Stage Hosts section and end at the beginning of scale in period specified in the Scale in restrictions section below.
-
Outside work hours: Type the number of sessions to maintain outside of work hours.
Note
This value cannot exceed the number of desktops available during work hours.
-
Working hours: From the drop-down lists, select the start and end times for working hours.
-
-
-
For User Driven:
-
When all users log off, scale in hosts after: From the drop-down list, select the number of minutes to scale in after all users have signed out.
Note
Desktops are automatically stopped only when there are no active or disconnected sessions. To automatically sign out disconnected users after a certain time, use the user session limits settings on the host pool properties.
-
-
Scale in Restrictions:
-
Stop or Remove (Scale In) Hosts Only From: From the drop-down list, select the time to perform the scale in operation. Select <any time> to allow scaling in to be performed at any time.
-
Scale In Aggressiveness: From the drop-down list, select the scale in aggressiveness.
Note
-
High Aggressiveness: Scale in aggressiveness is set to High by default, which means it is guaranteed that after business hours, hosts that have active or disconnected sessions running on them are automatically deleted or powered off to reduce capacity. After business hours, the auto-scale logic first removes the hosts that have no sessions running on them. The remaining hosts are sorted based on the least number of sessions running on them. The users with active sessions are then consolidated and moved to a single host and the other hosts are removed by auto-scale. A warning message is sent to the active session users before removing the session hosts.
-
Medium Aggressiveness: When scale in aggressiveness is set to Medium, after business hours, the scaling logic only removes the hosts that have disconnected sessions running on them. The session hosts with active sessions running on them won't be removed. In this case, the host pool is scaled in to some extent.
-
Low Aggressiveness: When scale in aggressiveness is set to Low, after business hours, the scaling logic only removes those session hosts that have absolutely no sessions running on them. The auto-scale logic does not remove any session host that have sessions, either active or disconnected, running on them. Though this option is less disruptive for the users, there is no guarantee that the host pool is ever scaled in.
-
-
Deactivate (drain mode) hosts: Optionally, you can tell the auto-scale engine to deactivate all hosts at the start of the scale in window. It does leave the minimum number of hosts as specified in the Min active host capacity in the Host Pooling Size section.
-
-
-
Enter the following Rolling Drain Mode information:
Note
-
You can create multiple drain windows and target a specific percentage of your hosts to drain mode, outside of the Scale-in Restriction window. This feature allows you to prevent new connections to a percentage of hosts and allows these hosts to be shut down more quickly, saving on resource costs.
-
Rolling drain mode selects hosts to scale in as follows:
-
First, it starts with lowest active sessions.
-
Then it scales in hosts that are already in drain mode,
-
Finally, it scales in hosts with the lowest number of total sessions (active + disconnected).
-
-
If a VM is using ephemeral storage, it will be deactivated rather than stopped when scaled in using Rolling Drain Mode.
-
Rolling Drain Mode: Toggle this option to Enabled.to enable rolling drain mode.
-
Window name: Type the name for this drain window.
-
Start time: From the drop-down lists, select the start time when this drain window comes into effect.
Note
The last drain window remains in effect until 11:59 PM.
-
% hosts in drain mode: Type the percentage of hosts in drain mode during this window.
Note
Use
to add or remove drain windows.
-
Load balancing: From the drop-down list, select the preferred load balancing algorithm.
Note
-
Depth First: The load balancing algorithm places users on a single host until the session limit is reached, at which point users start being placed on the next host until the session limit is reached again.
-
Breadth First: The load balancing algorithm spreads users evenly across available session hosts.
-
-
Scale in aggressiveness: From the drop-down list, select the scale in aggressiveness.
-
-
Enter the following Pre-Stage Hosts information:
Note
Configure the system to automatically pre-stage some hosts as available capacity with respect to the business hours. For example, you can pre-stage hosts at the beginning of the work day, so the system does not have to auto-scale in real time for users who all sign in at the same time when they start work.
-
Use Multiple Schedules: Select this option to enable multiple, non-overlapping pre-staging schedules to be used. Use
Note
This is not available for the Available Sessions trigger when During Work Hours option is specified.
-
Work Days: From the drop-down list, select the work days when pre-stage tasks should be run.
-
Start of Work Hours: From the drop-down select the starting hour when pre-stage tasks should be run.
-
Host to be Active by Start of Work Hours: Type the number of session hosts that should be ready to accept user connections by this time.
-
Scale In Delay: From the drop-down list, select a delay to restrict scale in operations after the start of work hours. Pre-staged hosts are not scaled in during this time even if they are unused.
-
-
Enter the following Messaging information:
Note
The system sends messages to any users connected to a session host that has been selected for scale in.
-
Send a Warning Message to Users on the host: From the drop-down list, select the number of minutes before scaling in that the message should be sent.
-
Message content: Enter the warning message text.
-
-
Enter the following Auto-Heal Broken Hosts information:
Note
Session hosts may get impaired due to domain trust issues or FSLogix configuration issues. The AVD agent reports the status of such hosts as unavailable. Admins then have to manually remove such hosts from the pool. However, Nerdio Manager allows you to configure a set of actions to repair these session hosts during the auto-scale process. Auto-scale can automatically attempt to repair "broken" session hosts by restarting and deleting/recreating them. It can make a few attempts to restart the host to try to get it back into an operational state and then either leave it alone or delete and recreate the host.
-
Auto-Heal Broken Hosts: Toggle this option to Enabled to enable auto-heal.
-
AVD agent status: From the drop-down lists, select the desired statuses along with the sessions status.
Note
The status is reported to the AVD service by the AVD agent installed on the session host VM. If something is wrong, the status is something other than "Available." Not every status other than "Available" means that there is a problem. See this Microsoft article for more details. Hosts with active sessions may still be somewhat functional and such hosts are not treated as broken. Only hosts that have either no sessions at all or no active session (that is, disconnected sessions only) are considered broken by auto-scale.
-
First action timeout: Enter the number of minutes to wait before running the first action.
-
Recovery actions: From the drop-down list, select the recovery action(s).
Note
-
You may select a VM action (for example, Restart VM or Remove VM), or a scripted action (for example, reinstall SxS, re-register host with AVD, etc.).
-
The recovery actions are run in the order shown. You can drag and drop any action to change its place in the list and, therefore, the order it is run.
-
-
Timeout between recovery actions: Type the number of minutes to wait after each restart attempt before moving on to next step (for example, Restart VM, then Remove VM, then etc.).
Note
If the Auto-heal operation requires deletion and re-creation of a broken host VM, a spare VM is powered on to replace the capacity, if available.
-
-
Once you have entered all the desired information, select Save.
Related topics:
Nerdio Manager allows you to perform auto-scaling on personal host pools. This enables you to do the following:
-
Personal desktops can be automatically powered on and off based on a schedule. Alternatively, personal desktops can be stopped when there are no active or disconnected sessions.
-
The host OS disk type can be changed to a lower priced storage type when the personal desktop is not running.
-
Auto-healing automatically attempts to repair "broken" session hosts. In addition, it allows scripted actions, such as SxS re-install or AVD host re-register, to be executed against them.
To configure the basic auto-scale information:
-
Locate the personal host pool you wish to work with.
-
From the more options
-
At the bottom of the page. toggle Auto-scale to Enabled.
-
Enter the following basic auto-scale information:
-
Auto-scale timezone: From the drop-down list, select the time zone for the auto-scale process.
-
Name: Type the name of the newly added hosts for Prefix or the Prefix+Pattern.
-
Prefix/Pattern: From the drop-down list, select whether to use a Prefix or a Pattern.
Note
-
Prefix can be used when creating multiple session hosts. The Prefix limit is 10 valid, Windows computer name characters. When using a Prefix, a unique suffix is automatically appended in the format "-xxxx", where xxxx are 4 random alphanumeric characters. For example: AVDHOST-s72h. Do not add a "-" to the Prefix.
-
Pattern can be used to specify an advanced naming convention for new hosts. Pattern characters must be enclosed in {} and can be # (for sequential numbers) and/or ? (for random alphanumeric characters). One # implies numbers from 0 to 9, two #s implies numbers of 0 to 99, etc.
-
Example 1: AVDHOST{###} (AVDHOST000..AVDHOST999).
-
Example 2: AVDHOST-{???} (AVDHOST-d83, AVDHOST-7sl, etc.).
-
-
-
-
Network: From the drop-down list, select the network the VM connects to.
Note
The VM that is created on the selected network is created in the Azure region associated with the network.
-
Additional subnets: From the drop-down list, select an additional subnet from the same virtual network.
Note
When scaling out, if a particular subnet does not have enough IP addresses, the next subnet will be chosen automatically when creating additional session hosts.
-
Network distribution: From the drop-down list, select how the network load should be distributed. Select either Depth first, or Breadth first.
Note
Select Depth first to distribute network load to nodes one after another in a fixed order, or select Breadth first to balance the network load proportionally based on current resource usage.
-
Desktop image (template): From the drop-down list, select a desktop image to be used as the golden image for new session hosts.
-
VM size (template): From the drop-down list, select the VM size for new session hosts.
-
Running OS disk (template): From the drop-down list, select the OS disk type and size for new session hosts.
-
Stopped OS disk type: From the drop-down list, select the OS disk type when session host VMs are stopped.
-
Resource group: From the drop-down list, select the resource group where VMs should be created.
-
VM naming: From the drop-down list, select the VM naming to use.
Note
Host VMs that are created automatically by the scale out or auto-grow process use names based on the selected VM naming mode. See How Session Host VM Names are Generated for more information.
-
Re-use names: Always attempt to re-use names that were previously used in the pool, if available.
-
Standard names: Use the next available name.
-
Unique names: Always attempt to use a unique name for new hosts.
-
-
-
Select Default schedule or Alternative schedule.
Note
Nerdio Manager allows you to configure separate auto-scale settings for a default schedule (normal operations) and an alternative schedule (outside of normal operations). For example, you may want fewer session hosts available on weekends or bank holidays. Alternatively, you may want more session hosts available two weeks prior to a holiday period when you have a large number of contingent users. In either case, you would use the Alternative schedule area to configure the auto-scale settings for those periods that are outside of normal operations.
-
To create an alternative schedule, select the Alternative schedule area and enter the following information:
-
Schedule: Select the toggle to enable the alternative schedule.
-
Days: From the drop-down list, select the off-peak day(s).
-
Dates: Select the date field, and from the calendar that is displayed, select the date..
-
Select the plus
icon to add another date, or select the minus
icon to remove dates.
-
-
-
Auto-scale mode: From the drop-down list, select the desired auto-scale mode.
Note
-
User-driven: The auto-scaling is performed when there are no active or disconnected sessions.
-
Schedule-based: The auto-scaling is performed as per the specified schedule.
-
-
Auto-scale profile: Optionally, from the drop-down list, select the auto-scale profile to use. Alternatively, select Custom to create a custom auto-scale configuration.
Note
See Manage Auto-scale Profiles for details about creating and working with auto-scale profiles.
-
Continue the configuration process with the relevant auto-scale mode:
-
User-driven: To enable user-driven personal host pool auto-scaling.
-
Schedule-based: To enable schedule-based personal host pool auto-scaling.
-
To enable user-driven personal host pool auto-scaling:
-
Auto-scale Mode: From the drop-down list, select the User-driven.
-
Enter the following Host pool properties information:
-
Start VM on connect: Select this option to start the desktop on connect.
-
-
Enter the following Desktop start and stop information:
-
Desktop start and stop: Toggle this option to enable desktop start and stop.
-
Desktops are stopped after: From the drop-down list, select the number of minutes or hours to scale in after all users have signed out.
Note
-
Desktops are automatically started when users connect.
-
Desktops are automatically stopped only when there are no active or disconnected sessions. To automatically sign out disconnected users after a certain time, use the user session limits settings on the host pool properties.
-
-
Bypass drain mode for desktops in this pool: Select this option so that desktops do not enter drain mode before shutdown.
-
-
Enter the following Pre-stage hosts information:
-
Pre-stagehosts: Toggle this option to enable pre-staging hosts.
Note
When pre-stage hosts is enabled it take precedence on other user-driven configuration. Stopped hosts will be started, hosts in drain mode will be activated, stopped disk types will be changed to running, and hosts will not be stopped or deactivated even if there are no user sessions.
-
Select the box to include hosts without assigned users.
-
Work days: From the drop-down list, select the workdays when large numbers of users log into their virtual desktops or applications at the same time.
-
Start of work hours: Select the time in the morning when users start logging into their virtual desktops or applications.
-
Scale in delay: Select a delay to restrict scale in operations after the start of work hours.
-
Note
Pre-staged hosts will not be scaled in during this time even if they are unused.
-
-
Enter the following Pre-stage Host OS Disks information:
Note
For more details and examples of intelligent disk pre-staging, see Intelligent disk pre-staging for personal host pools
-
Pre-stage host OS Disks: Toggle this option to enable pre-staging host OS disks.
-
From the drop-down lists, select the Days and Times the session host VMs' OS disks should be pre-staged.
-
Leave desktops that are not assigned to a user with STOPPED OS disk type: Select this option so that desktop VMs that are unassigned to a user do not have the OS disk converted from STOPPED to RUNNING.
-
Use intelligent disk pre-staging for users: Select this option to have intelligent disk pre-staging learn user behavior and automatically adjusts the disk pre-stage times.
Note
This feature requires AVD insights to be enabled and configured for the host pool.
-
Mode:When Use intelligent disk pre-staging for users is selected, from the Mode drop-down list, select the mode.
Note
-
Hybrid Mode: Disks are always be pre-staged based on the defined schedule. The behavior of users whose work patterns are learned, and additional staging activity are scheduled. This function is designed as "learning mode," with the benefits of both the standard pre-stage functionality and learned requirements.
-
Automated Mode: Disks are pre-staged for existing users only according to the learned schedule. New users respect the defined schedule until Intelligent pre-staging has enough data to automate this process. Disks are pre-staged 30 minutes before anticipated user log on events.
-
-
-
-
Enter the following Auto-Grow information:
Note
Automatically add desktops to the host pool when the number of unassigned desktops remaining falls below a specified threshold.
-
Auto-Grow: Toggle this option to enable auto-grow.
-
Add a new host when the number of available (not assigned to a user) falls below: Enter the threshold and from the drop-down list, select whether the threshold is a number of desktops or a percentage of total desktops.
-
-
Enter the following Auto-shrink information:
Note
The system automatically remove desktops that have not been used in a long time.
-
Auto-shrink: Toggle this option to enable auto-shrink.
-
Delete VM if the user hasn't logged in for: Type the number of days to wait before the system automatically deletes the VM.
Note
User activity on this session host VM is determined based on Nerdio Manager auto-scale history and AVD diagnostics data. Each time the desktop is processed by auto-scale, an Azure tag with date/time the desktop was last used is set. If the desktop hasn't been used for the number of days specified in this setting, the session host VM is shut down and a "pending deletion" tag is set.
-
Desktop will be set to “pending deletion” state and deleted after: From the drop-down list, select time duration before a desktop is deleted..
Note
The desktop is set to "Pending deletion" state by the auto-scale process by adding a tag to the VM. A task is logged during this process, which can be used for admin notification of a desktop entering the "Pending deletion" state. There also are notification banners in the Nerdio Manager UI indicating that a personal host pool has VMs that are pending deletion. After the "pending deletion" period expires (default: 24 hours), the VM is permanently deleted.
-
Exclude the following groups (or individual users): Enable this option, and then select the group(s) or individual user(s) to exclude from auto-shrink.
Note
Desktops assigned to users listed here are not automatically removed, even after a prolonged time of inactivity.
-
Exclude unassigned Desktops from Auto-shrink: Select this option to exclude desktops that have not been assigned to a user from the auto-shrink operations.
Note
Use this setting in combination with Auto-Grow to maintain a buffer of free unassigned desktops.
-
Scripted actions to run when a host is scheduled to shrink: From the drop-down list, select the scripted action(s) to run after the VM is marked to auto-shrink.
-
Notify users of scheduled deletion: Select this option to notify the user via email about deletion of their desktop when the inactivity period is exceeded.
Note
Notifications on the System > Settings > Nerdio page must be enabled for this feature to work.
-
Message Subject: Expand this option to type the subject line of the auto-shrink message.
-
Message Text: Expand this option to open the editor to create a custom auto-shrink message for users.
Note
The following variables are available for use in the message body:
-
%HOSTPOOL%: Returns the name of the affected host pool.
-
%HOSTNAME%: Returns the specific host name.
-
%HOST_IDLE_DAYS_THRESHOLD%: Returns the configured maximum idle days before auto shrink is started.
-
%SHRINK_TIME_UTC%: Returns the exact time in UTC when the auto-shrink task is set to occur.
-
%SHRINK_DATE%: Returns the exact date when the auto-shrink task is set to occur.
-
%SHRINK_DATE_EUR%: Returns the exact date when the auto-shrink task is set to occur in dd/MM/YYYY (European) format.
-
%IMAGE_NAME%: Returns the VM's image name.
-
%FRIENDLY_WORKSPACE_NAME%: Returns the workspace's friendly name.
-
%FRIENDLY_HOSTPOOL_NAME%: Returns the host pool's friendly name.
-
%VM_SIZE%: Returns the VM's size.
-
%DISK_SKU%: Returns the VM's disk SKU.
-
%USER_NAME%: Returns the name of the user logged in to the VM.
-
-
-
Notify an additional email recipient when desktops are scheduled to be deleted: Select this option to notify an additional email recipient when desktops are scheduled to be deleted.
-
Send notification emails to: Type the additional recipient's email address.
-
Send notification emails from: Type the sender's email address.
-
Notifications frequency: From the drop-down list, select how frequently the email reminders are sent to the user.
Note
A final email is always be sent 1 day before the scheduled deletion.
-
-
-
Enter the following Auto-heal broken hosts information:
Note
Session hosts may get impaired due to domain trust issues or FSLogix configuration issues. The AVD agent reports the status of such hosts as unavailable. Admins then have to manually remove such hosts from the pool. However, Nerdio Manager allows you to configure a set of actions to repair these session hosts during the auto-scale process. Auto-scale can automatically attempt to repair "broken" session hosts by restarting and deleting/recreating them. It can make a few attempts to restart the host to try to get it back into an operational state and then either leave it alone or delete and recreate the host.
-
Auto-heal broken hosts: Toggle this option to enable auto-heal.
-
In the Sign of a broken host box, enter the following information:
-
AVD agent status: From the drop-down list, select the AVD agent status, and then from the drop-down lost below, select the session status.
Note
The status is reported to the AVD service by the AVD agent installed on the session host VM. If something is wrong, the status is something other than "Available." Not every status other than "Available" means that there is a problem. See this Microsoft article for more details. Hosts with active sessions may still be somewhat functional and such hosts are not treated as broken. Only hosts that have either no sessions at all or no active session (that is, disconnected sessions only) are considered broken by auto-scale.
-
-
First action: Enter the number of minutes to wait before running the first action.
-
Recovery actions: From the drop-down list, select the recovery action(s).
Note
-
You may select a VM action (for example, Restart VM or Remove VM), or a scripted action (for example, reinstall SxS, re-register host with AVD, etc.).
-
The recovery actions are run in the order shown. You can drag and drop any action to change its place in the list and, therefore, the order it is run.
-
-
Timeout between recovery actions: Type the number of minutes to wait after each recovery action step before moving on to next step (for example, Restart VM, then Remove VM, then etc.).
Note
If the Auto-Heal operation requires deletion and re-creation of a broken host VM, a spare VM is powered on to replace the capacity, if available.
-
To add an addition Sign of a broken host, select the plus
-
-
Once you have entered all the desired information, select Save.
To enable schedule-based personal host pool auto-scaling:
-
From the Auto-scale mode drop-down list, select Schedule-based.
-
From the Auto-scale profile drop-down list, select the auto scale profile.
-
Enter the following Host pool properties information:
-
Start VM on connect: Select this option to start the desktop on connect.
-
-
Enter the following Working hours information:
-
From the drop-down lists, select the Work days and Working hours the session host VMs' OS disks should be pre-staged.
-
Power off aggressiveness: From the drop-down list, select the power off aggressiveness. (Schedule-based only)
Note
-
High: Power off all session host VMs, including those with active and disconnected sessions. Users with active sessions are sent a message, defined below, and given time to sign out before their session host VM is powered off.
-
Medium: Power off only those session host VMs that do not have an active user session, including those with disconnected sessions.
-
Low: Only power off those session host VMs that have no active or disconnected sessions.
-
-
Power on timing: From the drop-down list, select the power on timing. (Schedule-based only)
Note
-
Never: Do not power on session host VMs at the beginning of the working hours defined above. Users must manually power on their session host VMs.
-
Once: All sessions host VMs are only powered on once at the start of the working hours. If a session host VM is powered off after the start of the working hours, it is not automatically powered back on by auto-scale.
-
Continuously: All session host VMs are powered on at the start of the working hours. In addition, for the duration of the working hours, auto-scale automatically powers on any session host VMs that were manually powered off.
-
-
Power off timing: From the drop-down list, select the power off timing.
Note
-
Never: Do not power off session host VMs at the end of the working hours defined above.
-
Once: At the end of the working hours, all session host VMs are powered off, subject to the aggressiveness defined above. If any session host VMs are manually powered on outside of the working hours, auto-scale does not automatically power them off.
-
Continuously: At the end of the working hours, all session host VMs are powered off, subject to the aggressiveness defined above. If any session host VMs are manually powered on outside of the working hours, auto-scale automatically powers them off, subject to the aggressiveness defined above.
-
-
Include hosts without assigned user: Select this option to also start unassigned desktops during the auto-scale process.
Note
This may be useful for organizations wishing to perform scheduled tasks against desktops during the working day.
-
-
Enter the following Host OS disks information:
-
Set all hosts to running OS disk type during work hours: Select this option to convert all stopped host VM OS disks to running disk type during the working hours defined above.
Note
This is necessary to ensure that if a VM is started via Azure Start VM on Connect that it has the correct, high-performance disk type. When this setting is enabled, all "Disk type differs from policy" warnings are hidden for this pool.
-
Use intelligent disk pre-staging for users: Select this option to have intelligent disk pre-staging learn user behavior and automatically adjusts the disk pre-stage times.
Note
This feature requires AVD insights to be enabled and configured for the host pool.
-
Mode:If you have selected the Use intelligent desktop pre-staging for users option, then from the drop-down list, select the mode.
Note
-
Hybrid Mode: Disks are always be pre-staged based on the defined schedule. The behavior of users whose work patterns are learned, and additional staging activity are scheduled. This function is designed as "learning mode," with the benefits of both the standard pre-stage functionality and learned requirements.
-
Automated Mode: Disks are pre-staged for existing users only according to the learned schedule. New users respect the defined schedule until Intelligent pre-staging has enough data to automate this process. Disks are pre-staged 30 minutes before anticipated user log on events.
-
-
-
-
Enter the following Auto-grow information:
Note
Automatically add desktops to the host pool when the number of unassigned desktops remaining falls below a specified threshold.
-
Auto-grow: Toggle this option on to enable auto-grow.
-
Add a new host when the number of available (not assigned to a user) falls below: Type the threshold and from the drop-down list, select whether the threshold is a number of desktops or a percentage of total desktops.
-
-
Enter the following Auto-shrink information:
Note
The system automatically remove desktops that have not been used in a long time.
-
Auto-Shrink: Toggle this option on to enable auto-shrink.
-
Delete VM if the user hasn't logged in for: Type the number of days to wait before the system automatically deletes the VM.
Note
User activity on this session host VM is determined based on Nerdio Manager auto-scale history and AVD diagnostics data. Each time the desktop is processed by auto-scale, an Azure tag with date/time the desktop was last used is set. If the desktop hasn't been used for the number of days specified in this setting, the session host VM is shut down and a "pending deletion" tag is set.
-
Desktop will be set to “Pending deletion” state and deleted after: From the drop-down list, select the "Pending deletion" duration.
Note
The desktop is set to "Pending deletion" state by the auto-scale process by adding a tag to the VM. A task is logged during this process, which can be used for admin notification of a desktop entering the "Pending deletion" state. There also are notification banners in the Nerdio Manager UI indicating that a personal host pool has VMs that are pending deletion. After the "pending deletion" period expires (default: 24 hours), the VM is permanently deleted.
-
Exclude the following groups (or individual users): Enable this option, and then select the group(s) or individual user(s) to exclude from auto-shrink.
Note
Desktops assigned to users listed here are not automatically removed, even after a prolonged time of inactivity.
-
Notify user when their desktop is about to be deleted: Select this option to notify the user via email about deletion of their desktop when the inactivity period is exceeded.
Note
Notifications on the System > Settings > Nerdio page must be enabled for this feature to work.
-
Message Subject: Expand this option to type the subject line of the auto-shrink message.
-
Message Text: Expand this option to open the editor to create a custom auto-shrink message for users.
Note
The following variables are available for use in the message body:
-
%HOSTPOOL%: Returns the name of the affected host pool.
-
%HOSTNAME%: Returns the specific host name.
-
%HOST_IDLE_DAYS_THRESHOLD%: Returns the configured maximum idle days before auto shrink is started.
-
%SHRINK_TIME_UTC%: Returns the exact time in UTC when the auto-shrink task is set to occur.
-
%SHRINK_DATE%: Returns the exact date when the auto-shrink task is set to occur.
-
-
-
Notify an additional email recipient when desktops are scheduled to be deleted: Select this option to notify additional users about auto-shrink activity.
-
Send notification emails to: Type the additional email addresses.
-
-
Send notification emails from: From the drop-down list, select the "Send From" email address.
-
-
Enter the following Messaging information:
Note
The system sends messages to any users connected to a session host that has been selected for scale in.
-
Send a warning message to active users: From the drop-down list, select the number of minutes before scaling in that the message should be sent.
-
The message should say: Type the warning message text.
-
-
Enter the following Auto-heal broken hosts information:
Note
Session hosts may get impaired due to domain trust issues or FSLogix configuration issues. The AVD agent reports the status of such hosts as unavailable. Admins then have to manually remove such hosts from the pool. However, Nerdio Manager allows you to configure a set of actions to repair these session hosts during the auto-scale process. Auto-scale can automatically attempt to repair "broken" session hosts by restarting and deleting/recreating them. It can make a few attempts to restart the host to try to get it back into an operational state and then either leave it alone or delete and recreate the host.
-
Auto-heal broken hosts: Toggle this option to enable auto-heal.
-
AVD agent status: From the drop-down list, select the desired statuses along with the session status.
Note
The status is reported to the AVD service by the AVD agent installed on the session host VM. If something is wrong, the status is something other than "Available." Not every status other than "Available" means that there is a problem. See this Microsoft article for more details. Hosts with active sessions may still be somewhat functional and such hosts are not treated as broken. Only hosts that have either no sessions at all or no active session (that is, disconnected sessions only) are considered broken by auto-scale.
-
First action timeout: Type the number of minutes to wait before running the first action.
-
Recovery actions: From the drop-down list, select the recovery action(s).
Note
-
You may select a VM action (for example, Restart VM or Remove VM), or a scripted action (for example, reinstall SxS, re-register host with AVD, etc.).
-
The recovery actions are run in the order shown. You can drag and drop any action to change its place in the list and, therefore, the order it is run.
-
-
Timeout between recovery actions: Type the number of minutes to wait after each recovery action step before moving on to next step (for example, Restart VM, then Remove VM, then etc.).
Note
If the Auto-Heal operation requires deletion and re-creation of a broken host VM, a spare VM is powered on to replace the capacity, if available.
-
-
Once you have entered all the desired information, select Save.
Related Topics
There are two types of costs associated with a VM: compute costs and storage costs. Compute costs are incurred only when the VM is in use, while the storage costs are incurred even when the VM is stopped.
The Running OS disk size and Stopped OS disk type settings (along with other auto-scale settings) provide up to 75% storage cost savings. The auto-scale logic can automatically change the OS disk type of VMs in both pooled and personal host pools to a cheaper storage tier (from premium SSD to standard HDD) while the host VM is powered off, and back to the higher performance tier immediately before it is started.
To configure Running OS disk size and Stopped OS disk type settings on your session hosts:
-
Locate the host pool you wish to work with.
-
From the action menu, select Auto-Scale > Configure.
-
In the Auto-Scale section, configure the following:
-
Running OS Disk (Template): From the drop-down list, select the running disk type.
-
Stopped OS Disk Type: From the drop-down list, select the stopped disk type.
-
-
Once you have changed the parameters above, select Save & close.
Note
With Azure's Start VM on connect feature, VMs can be powered on outside of Nerdio Manager and may override Running OS disk size and Stopped OS disk type. That is, a VM powered on by the Start VM on connect feature is not able to change the disk performance. Instead, we recommend configuring Pre-stage to enable "Set all hosts to running os disk type" if Start VM on connect is enabled with storage scaling.
For a single-user host pool that has schedule-based auto-scaling, you can configure the Host OS Disks in and out of working hours. For example, you can specify Premium SSD when the VM is running and Standard SSD when the VM is stopped, thus saving on Azure storage costs
-
Navigate to Cloud Desktops > Azure Virtual Desktop > Workspaces > Host Pools.
-
Locate the single-user host pool you wish to change.
-
From the action menu, select Auto-scale> Configure.
-
In the Host OS Disks section, configure the following:
-
Running: From the drop-down list, select the disk type when the VM is running.
-
Stopped: From the drop-down list, select the disk type when the VM is stopped.
-
-
Once you have changed the parameters above, select Save & close.
For a multi-user host pool that has its Minimum Active Host Capacity set to 0, you can configure the system so that all stopped VM OS disks are automatically converted to Running OS Disk type during the pre-staging hours. This is necessary to ensure that if a VM is started via Azure Start VM on Connect that it has the proper high-performance disk type.
To configure the pre-staging OS disk type conversion:
-
Locate the single-user host pool you wish to work with.
-
From the action menu, select Auto-scale> Configure.
-
In the Pre-stage Hosts section, configure the following:
-
If necessary, enable Pre-stage hosts.
-
Set all host to running OS disk type: Select this option.
-
Set the pre-stage time as desired.
-
-
Once you have entered all the desired information, select Save & close.
-
Once a host pool is created, you can manually add session hosts.
Tip
When using Dynamic Host pools it is recommended that you create the hosts with auto-scaling configured. See Enable Dynamic Host Pool Auto-scaling for more information.
To add a session host to a dynamic host pool:
-
Locate the dynamic host pool you wish to work with.
-
Do the following:
From the more options
-
Enter the following information:
Note
For several of the required parameters, you may filter the available choices by using the Resource Selection Rules. For example, you may filter the VM Size or OS Disk choices for Intel RAM-optimized VMs only. See Resource Selection Rules Management for details.
-
Select Run now or Schedule.
-
The Schedule area allows you to perform the task during selected time frame(s). Otherwise, the task starts as soon as you select OK. See Manage Schedules for Tasks for details about creating a schedule. Select the schedule from the drop-down list, or create a new schedule.
-
-
Host Count: Type the number of session hosts to add to the host pool during creation.
-
Host Name: Type the name of the newly added hosts for the Exact name, a Prefix or the Prefix+Pattern.
-
Exact/Prefix/Pattern: From the drop-down list, select whether to use an Exact name, a Prefix, or a Pattern.
Note
-
Exact applies when adding a single host and specifying an exact name. For example, MYADVHOST.
-
Prefix can be used when creating multiple session hosts. The Prefix limit is 10 valid, Windows computer name characters. When using a Prefix, a unique suffix is automatically appended in the format "-xxxx", where xxxx are 4 random alphanumeric characters. For example: AVDHOST-s72h. Do not add a "-" to the Prefix.
-
Pattern can be used to specify an advanced naming convention for new hosts. Pattern characters must be enclosed in {} and can be # (for sequential numbers) and/or ? (for random alphanumeric characters). One # implies numbers from 0 to 9, two #s implies numbers of 0 to 99, etc.
-
Example 1: AVDHOST{###} (AVDHOST000..AVDHOST999).
-
Example 2: AVDHOST-{???} (AVDHOST-d83, AVDHOST-7sl, etc.).
-
-
-
-
Network: From the drop-down list, select the network. The network determines the Azure region of the VM.
-
Desktop Image: From the drop-down list, select the desktop image that is used as the golden image for newly created session hosts.
Note
The Unmanaged Azure Compute Gallery image versions section is at the bottom of the list. These are unmanaged, backup versions of images that were created while activating staged images. These images can be used to restore any changes made to session hosts.
-
VM Size: From the drop-down, select the VM type for newly created session hosts.
-
OS Disk: From the drop-down list, select the OS Disk type and size for newly created session hosts. Select optional filters if required to show specific OS disk types. For example, select All disks performance tiers to show the premium SSD disks.
Note
This must be equal to or larger than the size of the Desktop Image selected above. Using Standard HDD (S-type) is not recommended. Premium SSD provides best performance.
-
Resource Group: From the drop-down list, select the resource group to contain the VMs.
-
Apply tags: Optionally, type the Name and Value of the Azure tag to apply to the session host.
Note
You may specify multiple tags. See this Microsoft article for details about using tags to organize your Azure resources.
-
-
If you have entered a Host Count that is greater than 1, enter the following information:
-
Process Host in Groups Of: Type the number of concurrent operations when adding the new hosts.
-
Number of failures before aborting: Type the number of failed tasks before the process stops.
-
-
Once you have entered all the desired information, select Run now (not scheduled) or Save & close (scheduled).
Nerdio Manager enables you to customize the host pool's AVD settings.
To configure host pool AVD settings:
-
Locate the host pool you wish to work with.
-
From the action menu, select Properties > AVD.
-
Enter the following information:.
-
Friendly Name: Type the friendly name that is visible to the end users.
-
Description: Type the description that is visible to the administrators.
Note
Both the Friendly Name and Description can be changed at any time.
-
Load Balancing: Select the desired load balancing option.
Note
The load balancing algorithm is used by the AVD Management Service to determine how to route a particular user’s desktop or RemoteApp connection.
Breadth First means that the load-balancing algorithm spreads the users evenly across all available session hosts.
Depth First means the load-balancing algorithm places all the users in the first session host until the host's session limit is reached. Only then, does it place the users in the next session host. If necessary, it powers on the VM and makes it available to the users.
-
Session Limit: Type the number of sessions that a single host in the host pool can accept.
-
-
Validation environment: Select this option designate this host pool as a validation host pool.
Note
Validation host pools receive service updates at a faster cadence than non-validation host pools, allowing you to test service changes before they are deployed broadly to production.
-
Allow the users to manually start a session host when none are started: Select this option to allow a user to sign in to Nerdio Manager and perform service actions. For example, power on the session hosts within the host pool. Only specified users that have the permissions to sign in to Nerdio Manager can start the session host VM this way.
-
Start VM on connect: The VM is powered on automatically when the user connects. Any user can start the VM when they sign in.
-
Unassign user from host pool when removing host: For personal host pools, select this option to unassign the user from the host pool when the host is deleted.
-
Collect hosts CPU usage: Select this option to have the auto-scale process always collect CPU usage regardless of the host pool's auto-scale trigger.
-
Collect hosts RAM usage: Select this option to have the auto-scale process always collect RAM usage regardless of the host pool's auto-scale trigger.
-
Collect hosts average active sessions: Select this option to have the auto-scale process always collect average active sessions data regardless of the host pool auto-scale trigger..
-
Enable Scheduled AVD Agent Update: Toggle on this option to specify the day and time you want to update the AVD agent.
Note
Deploying updates at convenient times, or outside of peak business hours, ensures greater reliability and business continuity, while also enhancing the employee experience without interrupting business critical work.
-
Time Zone: From the drop-down list, select the time zone for the scheduled update.
Note
Setting the time zone ensures that updates to the session host VMs in the host pool take place at the same time according to the selected time zone, regardless of the session host VMs' local time zones. See this Microsoft article for details.
-
Use local session host time zone: Select this option to perform the agent update using the local time zone of each session host VM in the host pool.
Note
. Use this setting when all session host VMs in your host pool, or their assigned users, are in different time zones.
-
Maintenance window: From the drop-down lists, specify the day and time for the agent update.
Note
All maintenance windows are two hours long.
-
Set additional maintenance window: Optionally, select this option to specify a second maintenance window.
Note
Creating two maintenance windows gives the agent components an additional opportunity to update if the first update is unsuccessful.
-
Power on all hosts during window(s): Optionally, select this option to power on all hosts in a pool during maintenance window operations to ensure the installation of the latest AVD agent and other updates.
Note
Hosts that are started as part of this process are shut down after 2 hours. Hosts that were already running do not have their power state changed.
-
Exclude Drain mode hosts: Optionally, select this option to exclude drain mode hosts from the AVD agent maintenance window tasks configured in the host pool properties.
-
-
-
Once you have entered all the desired information, select Save or Save & close.
Nerdio Manager enables you to customize the way session host VMs are deployed in a host pool. This is a feature-rich facility that is detailed below.
To configure host pool VM deployment:
-
Locate the host pool you wish to work with.
-
From the action menu, select Settings > Virtual Machines.
-
Enter the following information:
-
Enter the following Operating System options:
-
Set time zone: Enable this option, and from the drop-down list select the time zone, to set the time zone on the VM when it is provisioned.
-
Time zone redirection: Enable this option to allow users to see their local device's time zone inside of their session.
-
Always prompt for password: Select this option to always prompt the user for a password.
Note
This policy setting specifies whether Remote Desktop Services always prompts the client for a password upon connection. You can use this setting to enforce a password prompt for users signing in to Remote Desktop Services, even if they already provided the password in the Remote Desktop Connection client.
By default, Remote Desktop Services allows users to automatically sign in by entering a password in the Remote Desktop Connection client.
-
If you select this option, users cannot automatically sign in to Remote Desktop Services by supplying their passwords in the Remote Desktop Connection client. They are prompted for a password to sign in.
-
If you do not select this option, users can always sign in to Remote Desktop Services automatically by supplying their passwords in the Remote Desktop Connection client.
-
-
Automatically deallocate powered-off VMs: Select this option to have a periodic task check if any session host VMs are in a powered off, but not deallocated, state and automatically deallocate them to save on Azure compute costs.
-
Boot diagnostics: Enable this option to apply the Boot Diagnostics feature to desktops in this pool.
Note
This setting only applies to newly created desktops.
-
Storage accounts for boot data: Optionality, from the drop-down list, select an available storage account to be used to store boot data.
Note
By default, Azure uses an automatic managed storage account for screen shots and other data. To use the default setting, leave this empty
-
-
Patch orchestration options: From the drop-down list, select the patch orchestration option, which allows you to control how patches are applied to your virtual machine.
Note
Nerdio Manager honors the Azure default setting, which is Automatic by OS (Windows Automatic Updates).
-
Accelerated networking (if supported): Enable this option to enable Accelerated Networking, if available.
Note
The Azure VM accelerated networking feature is available in some of the larger Azure VMs. This feature is useful for enterprise organizations and IT professionals who need to deploy, manage, and optimize large amounts of Azure Virtual Desktops. It speeds up networking performance of individual VMs.
If this feature is not supported on your Azure VM, it is not enabled. See this Microsoft document for more information.
-
NVMe (if supported): Enable this option to enable NVMe, if available.
Note
NVMe is a storage protocol that offers higher IOPs and throughput providing your workload with overall greater performance. See this Microsoft document for more information.
-
GPU drivers (if supported): Enable this option to install either NVidia or AMD drivers.
Note
GPU drivers can be installed on N-series VMs.
-
H.265 encoding (if supported): Enable this option to enable H.265 High Efficiency Video Coding hardware acceleration.
Note
H.265 hardware acceleration is available only on N-series VM sizes using NVidia GPUs.
-
Deploy VMs to Capacity reservation groups: Enable this option to place the VMs in a capacity reservation group.
Note
See Manage Capacity Reservations Groups for full details.
-
Capacity Reservation Groups: From the drop-down list, select the capacity reservation group(s).
-
-
Deploy VMs across availability zones: Enable this option to automatically distribute newly created or re-imaged session host VMs across Availability Zones in the selected Azure region.
Note
-
To ensure that Nerdio Manager considers all possible availability zones when reinstantiating VMs, ensure that Availability Zone Awareness is turned on in Host Pool Azure Capacity Extender Configuration.
-
See this Microsoft article for more details about Azure Regions and Availability Zones.
-
Availability zone: From the drop-down list, select the availability zone(s).
-
-
Deploy VMs on dedicated hosts: Enable this option to deploy the VMs to physical servers.
Note
See this Microsoft article for more details about Azure dedicated hosts.
-
Dedicated Host Group: From the drop-down list, select the dedicated host group.
-
Dedicated Host: From the drop-down list, select the dedicated host for the VMs.
Note
If Automatic assignment is selected, the VMs are automatically assigned to the appropriate hosts when powered on.
-
-
Deploy VMs in a proximity placement group: Enable this option to deploy VMs in a proximity placement group.
Note
VMs placed in a proximity group are located physically close to each other in an Azure data center, ensuring the lowest possible network latency between the VMs. See Learn Microsoft: Proximity placement groups for details.
-
Proximity placement group: From the drop-down list, select the proximity placement group.
-
Note
The selected group is automatically assigned to the VM at creation. If no suitable resource is found, VMs creation fails.
-
-
Restart VM after deployment: Select this option to restart the VM after it is created.
Note
If certain extensions are installed during deployment (FSLogix, Sepago, Virtual Desktop Optimizations, or User Sessions Time Limits), the VM is automatically rebooted even if this option is not selected.
-
Install App Attach certificates: Select this option to install all stored certificates if the App Attach packages are added to this host pool.
-
App-v client service: Enable this option to enabled the App-V client service, which is required if the VM uses App Attach packages containing an App-V package.
-
Install Applications: Enable this option to install applications configured by recurrent UAM policies before moving the host out of drain mode.
-
Entra ID group(s): From the drop-down list, select the default Entra ID group(s) to add the session hosts to.
-
Entra connect replication timeout (minutes): For hybrid enrollments, type a maximum delay for machine account replication from active directory via Entra Connect.
Note
By default, this is 30 minutes. A value up to 120 minutes can be specified.
-
Enforce Intune compliance : From the drop-down list, select this option to make hosts unavailable to users until the Intune compliance requirements are met.
Note
-
Optionally, select Compliance policies only or All policies. The All policies option also requires that Intune managed apps are installed successfully before the host is released from drain mode.
-
Intune integration must be enabled to make use of this feature, with the following options:
-
The Compliance polices only setting requires Intune managed devices read permissions.
-
The All policies setting additionally requires Device Policies & App policies read permissions.
-
-
Enabling either option may result in significant increase in provisioning time, depending on the configured Intune compliance requirements.
-
-
Allow non-admin users to shadow sessions: Enable this option to allow selected non-admin users or groups to shadow sessions.
Note
Session shadowing is only available with multi-session versions of Windows OS. This feature does not work with Windows 10 Enterprise (single session).
-
User or Group Name: From the drop-down list, select the users or groups to allow to shadow sessions.
-
-
Security Type: From the drop-down list, select the security type.
Note
Security type refers to the different security features available for a virtual machine. Security features like Trusted Launch and Confidential virtual machines improve the security of Gen2 VMs. However, additional security features have some limitations, which include not supporting back up, managed disks, and ephemeral OS disks.
-
Encryption at host: Select this option so that data stored on the session host VMs is encrypted at rest and flows encrypted to the Storage service.
Note
-
This setting only applies to newly created desktops.
-
Encryption sets are per subscription/region. You can create hosts in different subscriptions/regions, and based on the host's subscription/region we select the appropriate encryption set.
-
See this Microsoft article to learn more about the encryption at host feature.
-
-
Disk encryption sets: From the drop-down list, select the disk encryption sets to be used to provide customer-managed key functionality.
Note
By default, Nerdio Manager uses platform-managed keys. To use the default setting, leave the disk encryption sets blank. If disk encryption sets are required, create these from the Azure portal, in the same region as the desktop pool. Available disk encryption sets can be selected from the drop-down list. To learn more about key options, see Server-side encryption of Azure Disk Storage.
-
Application security group: From the drop-down list, select the Application Security Groups (ASGs) that enable you to configure network security as a natural extension of an application's structure.
Note
This allows you to group virtual machines and define network security policies based on those groups. This feature allows you to reuse your security policy at scale without manual maintenance of explicit IP addresses. VMs with network interfaces in different regions than the ASG are created without ASG support. The maximum number of supported ASGs is 10.
See Application Security Groups for more information.
-
Watermarking: Enable this option to enable watermarking.
Note
Watermarking helps prevent sensitive information from being captured on client endpoints. When you enable watermarking, QR code watermarks appear as part of the remote desktops. The QR code contains the connection ID of a remote session that admins can use to trace the session.
-
Scale: Select the scale, which is the size in pixels of each QR code dot. This value determines the number of squares per dot in the QR code.
-
Opacity: Select the opacity, which is how transparent the watermark is, in percent, where 0 is fully transparent.
-
Width factor: Select the width factor which determines the distance between the QR codes in percent. When combined with the height factor, a value of 0 would make the QR codes appear side-by-side and fill the entire screen.
-
Height factor: Select the scale, which determines the distance between the QR codes in percent. When combined with the width factor, a value of 0 would make the QR codes appear side-by-side and fill the entire screen.
-
-
Scripts signing: Enable this option to enable script signing.
Note
Nerdio Manager can automatically sign all PowerShell extensions and scripted actions running on session host VMs using a specified signing certificate. Please note that the selected certificate must be installed on the VMs for the scripts to work.
-
-
Once you have entered all the desired information, select Save or Save & close.
Nerdio Manager allows you to view users assigned to various host pools. In addition, you can assign or unassign users from the host pool.
To manage host pool user assignments:
-
Locate the host pool you wish to work with.
-
From the action menu, select Manage > Users and groups.
-
Alternatively, in the Status column, select the number next to Assigned users to view the users and groups.
-
In the Assignments window, you may search, sort, and filter the users and groups. For example, filter for all users not assigned to the host pool.
-
To unassign users from the host pool, select the
icon next to the user(s) you wish to unassign.
-
When you have selected all the users, select Unassign.
-
To assign users to the host pool, select the
-
When you have selected all the users, select Assign.
By default, every host pool uses the global default Active Directory configuration that was used when Nerdio Manager was installed. Nerdio Manager allows you to create multiple Active Directory profiles containing different service accounts and OUs, if required, We can then use these multiple profiles on different host pools.
To configure Active Directory for a host pool:
-
Locate the host pool you wish to work with.
-
From the action menu, select Properties > Directory.
-
Enter the following information:
-
AD Configuration: From the drop-down list, select the Active Directory configuration.
For a custom configuration, enter the following:
-
Directory: From the drop-down list, select the directory.
-
AD Domain: Type the domain for session host VMs to join in Fully Qualified Domain Name (FQDN) format.
-
AD Username: Type the username in FQDN format.
Note
This user must have permissions to create computer objects in the OU specified below and the ability to disable these AD computer objects when the VM leaves the AD domain.
-
AD Password: Type the password.
-
Organization Unit: Type the OU name in Distinguished Name (DN) format.
Note
This is the OU where all session host VMs and Desktop Images AD computer objects are created by default. Leaving this field blank places all the computer objects in the computer's AD container.
-
-
-
When you have entered all the desired information, select Save or Save & close.
Nerdio Manager allows you to take advantage of the "Start VM on connect" feature. This feature powers on a session host VM in a host pool where all the session host VMs currently powered off. Therefore, if the user signs in, a VM is powered on to give this user a session.
Note
End users can start a session host VM in more than one way. It depends on the user's permissions.
-
Allow the users to manually start a session host when none are started: This allows user to sign in to Nerdio Manager and perform service actions. For example, power on the session hosts within the host pool. Only specified users that have the permissions to sign in to Nerdio Manager can start the session host VM this way.
-
Start VM on connect: The VM is powered on automatically when the user connects. Any user can start the VM when they sign in.
To configure Start VM on connect for pooled host pools:
-
Locate the host pool you wish to work with.
-
From the menu, select Properties > AVD.
-
Select the Start VM on connect option.
-
Select Save or Save & close.
Nerdio Manager allows you to apply host session limits to individual host pools at the host pool level. This enables you to:
-
Optimize your AVD deployment and auto-scaling.
-
Conserve resources by signing out users who leave their sessions open or leave themselves in a disconnected state.
Note
-
By default, the session time limits option is disabled. Session time limits do not apply, and the system accepts any changes that users make to a single image or through the group policy.
-
Nerdio Manager applies session time limits through local policy changes on the session host VM. Session states are managed by the Windows OS rather than Nerdio Manager.
To set the user session time limits for full desktops:
-
Locate the host pool you want to work with.
-
From the action menu, select Properties > Session time limits.
-
Enter the following information:
-
Enable user session time limits: Toggle this option On.
-
Log off Disconnected sessions after: From the drop-down list, select the time to sign out disconnected users.
Note
By default, users can disconnect from an AVD session without signing out and ending the session. When a session is in a disconnected state, running programs are kept active even though the user is no longer actively connected. By default, these disconnected sessions are maintained for an unlimited time on the server.
If you enable this policy setting, disconnected sessions are deleted from the server after the specified amount of time. To enforce the default behavior that disconnected sessions are maintained for an unlimited time, select Never. If you have a console session, disconnected session time limits do not apply.
-
Disconnect Idle Session After:: From the drop-down list, select the maximum amount of time that an active session can be idle (without user input) before it is automatically disconnected.
Note
If you enable this policy setting, the idle session is disconnected after the specified amount of time. The user receives a warning two minutes before the session disconnects, which allows the user to press a key or move the mouse to keep the session active. If you have a console session, idle session time limits do not apply.
-
Disconnect Active session after: From the drop-down list, select the maximum amount of time that a session can be active before it is automatically disconnected. The recommended setting: Not configured.
Note
If you enable this policy setting, active sessions are automatically disconnected after the specified amount of time. The user receives a warning two minutes before the session disconnects, which allows the user to save open files and close programs. If you have a console session, active session time limits do not apply.
-
Log off Empty RemoteApp sessions after: From the drop-down list, select the amount of time a user's RemoteApp session remains in a disconnected state after closing all RemoteApp programs before the session is signed out.
Note
By default, if a user closes a RemoteApp program, the session is disconnected but it is not signed out. If you enable this policy setting, when a user closes the last running RemoteApp program associated with a session, the RemoteApp session remains in a disconnected state until the time limit that you specify is reached. When the time limit specified is reached, the RemoteApp session is signed out. If the user starts a RemoteApp program before the time limit is reached, the user reconnects to the disconnected session on the AVD session host VM.
If you disable or do not configure this policy setting, when a user closes the last RemoteApp program, the session is disconnected but it is not signed out.
-
Log off, instead of disconnecting, idle and active sessions: From the drop-down list, select the option to specify whether to end an active or idle session that has timed out instead of disconnecting it.
Note
You can use this setting to sign out a session after time limits for active or idle sessions are reached. By default, sessions are disconnected (not signed out) when they reach their time limits.
If you disable this policy setting, idle and active sessions that reach their time limit are disconnected even if specified otherwise by the server administrator.
This policy setting only applies to time-out limits that are explicitly set by the administrator. This policy setting does not apply to time-out events that occur due to connectivity or network conditions.
-
Apply to existing hosts: Select this option to apply the modified session time limits to existing hosts.
-
Restart VMs: Select this option to restart session host VMs after updating session timeouts.
-
Process Host in Groups Of: Type the number of concurrent operations when applying the change.
-
Number of failures before aborting: Type the number of failed tasks before the process stops.
-
Schedule: Toggle on the Schedule to apply the changes at a selected time.
-
Start Date: Type the date to start.
-
Time Zone: From the drop-down list, select the time zone for the Start time.
-
Start Time: From the drop-down lists, select the time to start.
-
Repeat: From the drop-down list, select the recurring schedule, if desired.
Note
The drop-down has the option After Patch Tuesday. This allows you to create a recurring schedule based on Patch Tuesday.
-
Days After: If you selected After Patch Tuesday, type the number of days after Patch Tuesday to run the scheduled task.
-
-
-
-
-
Once you have entered all the desired information, select Save or Save & close.
Users are often moved to a cloud environment because one application no longer runs locally. However, there are great cost savings to be had by simply running one or more applications remotely. This guide walks you through the how's and why’s of setting-up an AVD host Pool with remote applications.
You can use Nerdio Manager to easily publish applications (RemoteApps) within Azure Virtual Desktop. These applications may be restricted by application groups, if required, allowing administrators to publish different apps to different users from the same host pool.
Like the name suggests, RemoteApps are applications that are run remotely. However, despite what some people may think, remote apps require a multi-session AVD host to be able to utilize the application remotely. You install your applications just like you would with a traditional Remote Desktop solution. However, when you go to publish the application for remote users, you can choose which apps the user has access to. This is handled by Application Groups.
Note
If you have full-desktop experiences for users, instead of remote apps, you can limit the apps the users have access to with FSLogix App Masking.
RemoteApps are less resource-intensive than a full desktop experience, allowing you to have more users on a given host, thereby reducing costs.
In Azure Virtual Desktop (AVD), application groups define what users can access, either a full desktop or specific apps, within a host pool. Users can be assigned to multiple application groups across different host pools for flexible access.
There are the following types:
-
Desktop: Gives access to a full Windows desktop (pooled or personal host pools).
-
RemoteApp: Provides access to selected apps (pooled host pools only).
You can assign both types to the same pooled host pool, but only one Desktop group per pool. Multiple RemoteApp groups can be assigned, and users see all apps from those groups.
If a user is assigned both Desktop and RemoteApp in the same pool, they’ll only see the preferred application group type, based on the pool's settings.
As mentioned previously, you need a multi-user host pool to utilize Remote Applications. Ideally, you should create a new host pool. However, if you already have an existing host pool, you can easily add a RemoteApp Group and/or switch to a RemoteApp group.
Now that you have your host pool, you need to create or update your desktop image and then deploy it to your host pool. See Desktop images: set as image for details.
Application Groups allow the assignment of users and groups to desktops and RemoteApps. This helps simplify application management because applications can be managed by app groups instead of individual users.
Note
There must be at least one app group associated with a host pool.
To add an app group to a host pool:
-
Select the host pool you want to work with.
-
From the more options
-
Enter the following information:
-
RemoteApp app groups: Type the name(s) of the app groups for RemoteApps.
Note
A host pool may have multiple RemoteApp app groups.
-
Desktop app group: Type the name of the Desktop app group.
Note
A host pool may only have one Desktop app group.
-
-
Once you have entered the desired information, select OK.
RemoteApps gives the user the ability to launch a single application without having to launch the full desktop experience. For example, the user can launch Excel without having to sign in to a desktop. This saves on session host resources because the users do not have to use a full desktop. So, in our Excel example, you might be able to have 10 users working with Excel as a RemoteApp, but had the users connected as a full desktop, the session host might have been able to handle fewer users. That means you would have to deploy additional session hosts to handle all the Excel users.
You can publish RemoteApps using the following methods:
Nerdio Manager enables you to deliver applications installed on a host, to your users.
To publish a remote application installed on a host to users:-
Select the host pool you want to work with. This is a host pool configured for the RemoteApp (Pooled) desktop experience.
-
From the more options
-
Select New RemoteApp.
Note
-
When adding the RemoteApp, the host must be switched on and the applications that you want to publish must be already installed.
-
If the host pool has multiple RemoteApp app groups, a specific RemoteApp app group must be selected. By publishing different applications to different Application Groups, administrators can control access to these applications via group membership. This allows user groups to be served different applications from the same host pool.
-
-
In the Select App Group dialog box, enter the following information:
-
From the drop-down list, select the app group.
-
Select OK.
-
-
In the Publish Application dialog box, enter the following information:
-
Application Source: From the drop-down list, select Installed on host.
Note
Note
Note: You may select one of the following application source types:Installed on host: The apps are installed locally on the session host VM.App Attach Package: An MSIX App Attach package.File Path: You may select a specific file path to the target application. This can help in scenarios where the target application does not register itself with the Windows installer, or where portable applications are required.
-
Application: From the drop-down list, select the application.
-
Name: Type the name of the RemoteApp.
Note
The Name is visible to the user unless overridden by the Friendly Name.
-
Friendly Name: Optionally, type the friendly name that is visible to the user.
-
Description: Type the description that is visible to the admin.
-
File Path: Type the path to the application executable on the session host.
-
Icon Path: Optionally, type the path to an icon file to be used for this RemoteApp when it appears in the user's Remote Desktop feed.
-
Icon Index: Optionally, type the numeric icon index in the icon file.
-
Command Line Setting: Select this option to require a command line setting.
-
Command Line: Type the command line to pass to the executable when launching the RemoteApp.
-
-
Once you have entered the desired information, select OK.
The authorized host pool users now need to be assigned to the RemoteApp Group that contains the newly published RemoteApp.
Note
-
Host pool users are not automatically assigned to that host pool's RemoteApp Groups. Each user must be individually assigned to the appropriate RemoteApp Group.
-
From the action menu, you can Edit or Delete published apps.
Nerdio Manager enables you to deliver App Attach packaged applications to your users.
To publish a remote application from an App Attach package to users:-
Select the host pool you want to work with. This is a host pool configured for the RemoteApp (Pooled) desktop experience.
-
From the more options
-
Select New RemoteApp.
-
In the Select App Group dialog box, enter the following information:
-
From the drop-down list, select the app group.
-
Select OK.
-
-
In the Publish Application dialog box, enter the following information:
-
Application Source: From the drop-down list, select App Attach Package.
-
App Attach Package: From the drop-down list, select the App Attach package.
-
MSIX Applicatio n: From the drop-down list, select the MSIX application.
-
Friendly Name: Optionally, type the friendly name that is visible to the user.
-
Description: Type the description that is visible to the admin.
-
Icon Path: Optionally, type the path to an icon file to be used for this RemoteApp when it appears in the user's Remote Desktop feed.
-
Icon Index: Optionally, type the numeric icon index in the icon file.
-
-
Once you have entered the desired information, select OK.
Nerdio Manager enables you to deliver applications from a file path to your users.
To publish a remote application from a file path to users:-
Select the host pool you want to work with. This is a host pool configured for the RemoteApp (Pooled) desktop experience.
-
From the more options
-
Select New RemoteApp.
-
In the Select App Group dialog box, enter the following information:
-
From the drop-down list, select the app group.
-
Select OK.
-
-
In the Publish Application dialog box, enter the following information:
-
Friendly Name: Optionally, type the friendly name that is visible to the user.
-
Description: Type the description that is visible to the admin.
-
File Path: Type the path to the application executable on the session host
-
Icon Path: Optionally, type the path to an icon file to be used for this RemoteApp when it appears in the user's Remote Desktop feed.
-
Icon Index: Optionally, type the numeric icon index in the icon file.
-
Command Line Setting: Select this option to require a command line setting.
-
Command Line: Type the command line to pass to the executable when launching the RemoteApp
-
-
Once you have entered the desired information, select OK.
Related Topics
Comments (0 comments)