Once Nerdio Manager is installed, the next step is to prepare the desktop images your host pools will be built from - whether you're importing existing images or letting Nerdio Manager manage new ones for you.
This section discusses topics related to desktop images. We will discuss the various import and lifecycle management options, as well as different ways to automate certain tasks in more advanced scenarios.
After creating a new Workspace, the next step in building out an AVD environment is to create one or multiple host pools housing your virtual machines (see Host Pools for more information). Virtual machines are created based on a desktop image, which holds the operating system, your applications, and anything else you might want to add. For this to work, we first need to create at least one desktop image.
Before we continue, it is important to understand that images can be created or imported in different ways. Even when there are no images imported into Nerdio Manager, the custom Azure images part of your subscription can be used to build new host pools and re-image existing host pools in exactly the same way as with imported images.
If you do choose to import your images into Nerdio Manager, you can take advantage of many different management features otherwise not available.
In addition, when images are imported into Nerdio Manager all of your management and lifecycle activities are done using a single management portal.
Once an image is created or imported, regardless of the type of image (we'll explain in more detail going forward), creating new host pools and re-imaging existing host pools is done in the same way. In the sections below we will walk you through it step by step.
No matter where your desktop images are imported from, their management and lifecycle tasks are the same.
The typical desktop image lifecycle is as follows:
-
Import the desktop image.
See any of the following for detailed information:
-
Power on the desktop image:
-
Navigate to Cloud Desktops > Desktop Images.
-
Locate the desktop image you wish to power on.
-
Select Power on.
-
-
Use the VM's IP address or name to connect to it using RDP and make all the desired changes.
-
Select Power off & set as image.
See Desktop Images Set as Image for details.
Note
An extensive automation process begins that commits the changes to an image object. This includes many tasks you would have had to do manually like Sysprep and sealing the image.
You can see the job's progress in the logs. See Desktop Images Change Log Feature for details about the logs.
-
Once the image is set, you can use it to build new host pools or re-image an existing host pool.
For details, see:
Nerdio Manager allows you to use the power of an endpoint management tool (for example, Microsoft's Endpoint Configuration Manager or Ivanti's Endpoint Manager) to leverage its power to work with Nerdio Manager.
Example of endpoint management software integration
Patch Tuesday, when Microsoft releases its monthly software updates, occurs on the second Tuesday of each month at about 10 AM Pacific Standard Time. You can use your endpoint management tool, along with Nerdio Manager, to fully automate applying the Windows Updates to the desktop image and re-imaging the host pools with the updated desktop image.
Note
This is just one example of the many things you can do using these built-in automation tools.
-
In Nerdio Manager, when you perform the Set as image function, be sure to select the Leave desktop image VM running option. This leaves the VM running after the Set as image task completes and the endpoint management tool can access the VM and change the image.
-
In the endpoint management tool, create a recurring scheduled job/runbook on Patch Tuesday to apply the Windows Updates.
-
In Nerdio Manager, configure the Set as image function for the desktop image to be a recurring job that starts shortly after the endpoint management tool's job completes. See Desktop Images Set as Image for details about configuring the job.
-
In Nerdio Manager, configure the Re-image Hosts function for the host pool to be recurring job that starts shortly after the Set as image process completes. See Resize/re-image a host pool for details about configuring the job.
So, by creating three recurring scheduled jobs you can apply the Windows Updates to the VM, set the VM image, and then update the host pool with the updated desktop image every month.
Nerdio Manager for Enterprise allows you to create a desktop image either from an existing image in the Azure library or by importing an existing Azure VM.
-
Navigate to Cloud Desktops > Desktop Images.
-
From the bottom-right of the page, select Create.
The Create Desktop Image dialog opens. It contains the following sections: VM, Join to AD, Settings, Clean up, Scripted Actions & Apps, Image, Replication, and Tags.
-
Refer to the table that matches the source of your desktop image, and enter the information listed.
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.
UI Element
Type
Description
Source
Drop-down list
From the drop-down list, select Azure library to create the image from an existing image in your library.
Name
Text field
Enter the desktop image's name.
Description
Text field
Enter the description.
Network
Drop-down list
Select the network to which the VM connects. The VM is created in the Azure region associated with the network.
Azure image
Drop-down list
Select the desired image based on your Windows OS requirements, as supported by AVD, for example Windows 11 EVD Multi-Session (EVD = Enterprise Virtual Desktop). Images labeled Microsoft 365 Apps include a pre-installed version of Microsoft 365 Apps for enterprise, activated when licensed users sign in to the desktop. The list contains all standard Azure Marketplace images as well as all custom managed images available inside your Azure subscription.
Use the "staged" image version
Toggle
If enabled, this desktop image will be created using the "staged" image version of the selected desktop image, if one is available. This setting is only available for desktop images with Geographic distribution & Azure compute gallery enabled.
VM size
Drop-down list
Select the size.
OS disk
Drop-down list
Select the disk. You can also select the performance tier.
Resource group
Drop-down list
Select the resource group to contain the network interface cards of the VM.
Optimize disk type when desktop image is stopped
Checkbox
Downgrades the OS disk type when the desktop image is stopped in order to save money. When the VM starts, the OS disk type is changed back to the selected one.
UI Element
Type
Description
Source
Drop-down list
From the drop-down list, select Azure VM to import an existing VM as the desktop image.
SAS URL
Text field
Paste the SAS URL generated from the Azure portal. Your VM needs to be based on a Managed Disk: in the Azure portal, stop the VM, go to its OS disk, and select Disk Export to generate the URL.
Name
Text field
Enter the desktop image's name.
Description
Text field
Enter the description.
Network
Drop-down list
Select the network to which the VM connects. The VM is created in the Azure region associated with the network.
OS
Drop-down list
Select the operating system of the VM. If the selected OS requires Hyper-V Generation 2 (for example, Windows 11) and Gen2 is not yet enabled, a message displays prompting you to enable Create image VM as Gen2 on the Settings step, or to choose a Gen1-compatible image instead.
VM size
Drop-down list
Select the size.
OS disk
Drop-down list
Select the disk. You can also select the performance tier.
Resource group
Drop-down list
Select the resource group to contain the network interface cards of the VM.
Optimize disk type when desktop image is stopped
Checkbox
Downgrades the OS disk type when the desktop image is stopped in order to save money. When the VM starts, the OS disk type is changed back to the selected one.
-
Select Next.
-
Configure the following:
-
Join to AD: Enabled by default. Deselecting this means the VM is not joined to AD during the creation process. This prevents AD GPOs from applying to the image before it is created. Be sure to specify local administrator credentials in the Custom credentials field on the Settings step, since the VM won't be a member of the AD domain.
-
From the drop-down list, select the Active Directory domain to join, for example denver.int (default).
-
-
Select Next.
-
Enter the following information:
UI Element
Type
Description
Hibernation supported
Checkbox
Select this option if you want to allow the VM to hibernate. Hibernation provides the ability to deallocate your virtual machine while persisting the memory contents, allowing you to resume from where you left off the next time you start your VM. Hibernation cannot be enabled or disabled after the image is created.
Specialized image
Checkbox
Select this option if the image is a specialized image. Generalized images have had machine and user-specific information removed by running a command on the VM. Specialized images retain this information and have not gone through the generalization process.
Run sysprep in
Drop-down list
Select the context in which Sysprep should run on the VM, for example System-context.
Create image VM as Gen2
Checkbox
Available only when Azure VM is selected as the source on the VM step. Select this option to create the VM as Gen2. By default, desktop image VMs are created as Gen1. If the selected OS requires Gen2 and this option is not selected, a message displays prompting you to choose a Gen1-compatible Azure image to continue. See Support for Generation 2 VMs on Azure for details.
Time zone redirection
Checkbox
Select this option to enable time zone redirection on the image. This allows each user to see their local device's time zone inside of their AVD desktop session.
Set time zone
Toggle
Toggle this option On to set the time zone of the VM, then, from the drop-down list, select the time zone.
Boot diagnostics
Toggle
Enabled by default. Collects and stores diagnostic logs and screenshots while the VM boots.
Boot diagnostic storage account
Drop-down list
Applies only if Boot diagnostics is enabled. Leave this field set to Managed Storage Account (recommended) to store boot diagnostic logs in an Azure-managed storage account, or select a user-managed storage account from the list.
Security type
Drop-down list
Select the security option that best suits your desktop image VM. Standard is set by default. Additional security options are only available for generation 2 VMs with Geographic distribution & Azure compute gallery enabled. Trusted launch and Confidential virtual machines improve security but have some limitations, such as lack of support for backup, managed disks, and ephemeral OS disks. See Trusted launch for Azure virtual machines and About Azure confidential VMs for details.
Secure Boot
Checkbox
Available only when Trusted launch virtual machines is selected as the Security type. Enables Secure Boot, which helps protect your VMs against boot kits, rootkits, and kernel-level malware.
vTPM
Checkbox
Available only when Trusted launch virtual machines is selected as the Security type. Enables Virtual Trusted Platform Module (vTPM), which is TPM 2.0 compliant and validates your VM boot integrity apart from securely storing keys and secrets.
Integrity Monitoring
Checkbox
Available only when Trusted launch virtual machines is selected as the Security type. Enables cryptographic attestation and verification of VM boot integrity along with monitoring alerts if the VM didn't boot because the attestation failed with the defined baseline.
Encryption at host
Toggle
Disabled by default. Provides end-to-end encryption for your VM data at rest and in transit, starting with the Azure hosts.
Custom credentials
Toggle
Disabled by default. Toggle On to enter the admin username and password for a local administrator user.
Install App Attach certificates
Checkbox
Select this option to install all the stored certificates on the VM, if applicable. To view the stored certificates, navigate to App Attach > Certificates.
Enable App-V client service
Checkbox
Select this option if the VM will use App Attach packages that contain App-V packages.
-
Select Next.
-
Refer to the table that matches the source of your desktop image, and enter the information listed.
UI Element
Type
Description
Skip removal of local profiles
Checkbox
Select this option to bypass this step and not remove local user profiles before running Sysprep. During the image creation process, Nerdio Manager removes all local user profiles. This increases the likelihood of Sysprep success. Selecting this option bypasses this step. If there are any partially installed APPX apps on the image VM, Sysprep will fail to remove them.
Uninstall legacy VDI agents
Checkbox
Select this option to attempt to remove Citrix and Omnissa VDI agents from the VM before capturing the image. Only detected agents are removed.
Remove FSLogix apps
Checkbox
Selected by default. Select this option to remove the FSLogix agent if it's found on the image. The FSLogix agent is not required on the desktop image: the latest FSLogix agent will be installed automatically on session hosts that are created from this desktop image.
UI Element
Type
Description
Skip removal of local profiles
Checkbox
Select this option to bypass this step and not remove local user profiles before running Sysprep. During the image creation process, Nerdio Manager removes all local user profiles. This increases the likelihood of Sysprep success. Selecting this option bypasses this step. If there are any partially installed APPX apps on the image VM, Sysprep will fail to remove them.
Uninstall legacy VDI agents
Checkbox
Select this option to attempt to remove Citrix and Omnissa VDI agents from the VM before capturing the image. Only detected agents are removed.
Uninstall FSLogix app
Checkbox
Selected by default. Use this option if FSLogix app is already installed in the base image and you want to remove it in order to allow Nerdio Manager to manage FSLogix.
Uninstall AVD agent
Checkbox
Use this option if you're creating an image from an existing AVD session host where the AVD agent has been previously installed. Be sure to uninstall the AVD agent before you set this imported VM as a desktop image. See Desktop Images Manually Uninstall AVD Agent for details.
-
Select Next.
-
Enter the following information:
-
Run the following scripted actions: Toggle this option On, then from the drop-down list, select the scripted action to run during creation.
Note
-
Windows scripts are executed via the Azure Custom Script extension and run in the context of LocalSystem account on the clone of the desktop image VM before it is sysprepped. These commands do not run on the image VM itself.
-
Azure runbooks are executed via the Azure automation account and run in the context of Nerdio Manager app service principal.
-
Several variables are passed to the script and can be used in the PowerShell commands.
-
If necessary, provide the required parameters.
-
-
Pass AD credentials: Select this option to pass AD credentials that are specified on the Settings > Integrations > Active Directory page to the scripts being executed. In the script, reference them as $ADUsername and $ADPassword.
-
Target VM: Select whether the scripted action runs against the Clone of the desktop image VM (default) or the Source VM.
-
Applications management: Toggle this option On to specify the applications to deploy during creation.
-
Applications: In the applications list, select Add new application, and then from the drop-down list, select the application to include in this policy.
Note
-
You may add as many applications as desired.
-
Drag and drop an application in the list to change its order on the list.
-
Select the "X" next to an application to remove it from the list.
-
-
Select one of the following for the added application or application group:
-
Install app: Installs the selected application.
-
Uninstall app: Uninstalls the selected application.
-
Install group: Installs the selected application group.
-
Uninstall group: Uninstalls the selected application group.
-
-
In the Search application field, select the app or application group to install or uninstall, based on the option selected above.
-
Show favorites only: Select this option to display only those applications that are marked as favorites. Otherwise, you may search the list of applications.
-
Reboot after installation: Select this option to reboot the clone of the desktop image VM after this application is installed. Subsequent application tasks will resume once the reboot is complete.
-
Target VM: Select whether the application action runs against the Clone of the desktop image VM (default) or the Source VM.
-
-
-
Select Next.
-
Enter the following information:
UI Element
Type
Description
Do not create image object
Checkbox
Select this option to create only a desktop image VM but not an image object. You need to create the image object: select Power off and set as image after the VM is created before this desktop image can be used for session host creation. If you skip image creation, you can make changes to the VM before it is converted to an image.
Geographic distribution & Azure compute gallery
Toggle
Enabled by default. Stores the image in an Azure Compute Gallery and automatically distributes it to the selected Azure regions.
Azure compute gallery
Text field / drop-down list
Type a name to select an existing Azure compute gallery or create a new one. Only one Azure Compute Gallery can be selected. The existing gallery must be in a linked resource group in the same Azure subscription as the image VM.
Azure regions
Multi-select
Automatically populates with the region associated with the selected gallery. You can remove or add regions where the Desktop Image version should be replicated. The current Azure region must be part of the selection.
Replica count (per region)
Text field
Specify the number of replicas per region. Azure Compute Gallery replicas support a maximum of 20 concurrent clone operations per replica. Up to 100 replicas per region are supported. Replicas can only be deployed within the same subscription.
-
Select Next.
-
Enter the following information:
-
Enable for Cloud PCs: Requires Windows 10/11 Enterprise. Not available for AVD, EVD, or CIS images.
-
Custom (Azure local) locations: From the drop-down list, select any custom Azure local locations to replicate the image to.
-
Nutanix cluster (AVD Hybrid on Nutanix AHV only): From the drop-down list, select the Nutanix cluster where the image should be synchronized.
Note
Only managed image versions (Active or Staged) are synchronized to Nutanix. Unmanaged (backup) versions are not synchronized. For more details, see Create a VM Template for Nutanix Host Pools.
-
-
Select Next.
-
Enter the following information:
Note
You can specify multiple tags. The specified tags are applied to image VM, OS disk, network interface, image object, and Azure Compute Gallery image. For details about using tags to organize your Azure resources, see Use tags to organize your Azure resources and management hierarchy.
-
Tag groups: Optionally, select a predefined tag group from the drop-down list to apply its tags automatically.
-
Name and Value: Optionally, enter a custom tag name and value.
-
-
Select Submit.
Nerdio Manager for Enterprise begins creating the desktop image. This may take up to an hour to complete. You can monitor progress on the Tasks tab of the Desktop Images page.
Nerdio Manager provides a powerful tool that performs an extensive automation process to commit the desktop image changes to an image object. This includes many tasks you would have had to do manually like Sysprep and sealing the image. This would normally be done after you have made the updates to your image. Once you perform Set as image, the image object is created and is ready to be used either to build new host pools or to re-image existing host pools.
To set a desktop image:
-
Navigate to Cloud Desktops > Desktop Images.
-
Locate the desktop image you wish to work with.
-
From the action menu, select Power off & set as image or Set as image (according to the power state of this desktop image).
-
Enter the following information:
-
Run the following scripted actions before set as image: Toggle this option On to run scripted action(s) before the set as image.
Note
For example, you can run scripts to optimize the image, install software, or install updates.
-
From the drop-down list, select the scripted action(s) you wish to run.
-
Pass AD credentials: Select this option if you want to use them to run the scripted actions.
-
-
Applications Management: Toggle this option On to specify the applications to deploy during creation.
-
Applications: In the applications list, select Add new application, and then from the drop-down list, select the application to include in this policy.
Note
-
You may add as many applications as you need.
-
Drag and drop an application in the list to change its order on the list.
-
Select the "X" next to an application to remove it from the list.
-
-
Install/Uninstall: Select whether the deployment policy should install or uninstall the selected applications.
-
Reboot after installation: Select this option to reboot the clone of the desktop image VM after this application is installed. Subsequent application tasks will resume once the reboot is complete.
-
Show favorites only: Select this option to display only those applications that are marked as favorites. Otherwise, you may search the list of applications.
-
-
Schedule: Toggle the Schedule option On to perform the operations at a selected time(s). See Manage Schedules for Tasks for details about creating a schedule.
-
Refresh image from Azure Marketplace: Toggle this option On to remove the existing image object and replace it with the latest version of the selected Azure Marketplace image.
Note
Enabling this option removes the existing desktop image VM and re-creates it from the latest version of the selected Azure Marketplace image.
-
Security type: This option is locked based on the selection made when the image was created or imported into Nerdio Manager.
Note
-
Standard is set by default. Additional security options are available only for generation 2 VMs with the Geographic distribution & Azure compute gallery option enabled.
-
The Trusted launch and Confidential virtual machines security options help improve the security of Azure generation 2 VMs. However, additional security features they provide also have some limitations, such as the lack of support for backup, managed disks, and ephemeral OS disks. To learn more, see:
-
-
Geographic distribution & Azure compute gallery: Select this option to store the image in Azure Compute Gallery and automatically distribute it to the selected Azure regions.
-
Azure Compute Gallery: This option is locked based on the selection made when the image was created or imported into Nerdio Manager.
Note
Only one Azure Computer Gallery can be selected. The existing Azure Compute Gallery must be in a linked resource group in the same Azure subscription as the image VM.
-
Azure Regions: From the drop-down list, select Azure regions where the desktop image version should be replicated.
Note
The current Azure region must be part of the selection.
-
Version Increment Type: From the drop-down list, select one of the following options:
-
Major
-
Minor
-
Revision
Note
Version numbers are in the format Major.Minor.Revision. For example, when updating version 1.4.3, the up-level version would be numbered as follows, depending on the option you choose in the Version Increment Type dropdown:
-
Major: 2.0.0
-
Minor: 1.5.0
-
Revision: 1.4.4.
-
-
-
Specialized image: Select this option if the image is a specialized image.
Note
Generalized images have had machine and user-specific information removed by running a command on the VM. Specialized images retain this information and have not gone through the generalization process.
-
Hibernation supported: Select this option if you want to allow the VM to hibernate.
Note
Hibernation provides the ability to deallocate your virtual machine while persisting the memory contents. This allows you to resume from where you left off the next time you start your VM. Note that hibernation cannot be enabled or disabled after the image is created.
-
Stage new image as inactive: Select this option to create the new image version without setting it as active.
Note
Any existing configurations continue to use the current version of the image. See Stage Desktop Images for details about activating staged desktop images.
-
Activate staged image after: Select this option to automatically activate the image a number of days after staging. Any linked pools will have their associated image updated.
-
Current image action: Select one of the following:
-
Keep current version as backup: This option retains the current image version as a standalone object. This image version is not visible or manageable via Nerdio Manager, so be sure to delete it manually when no longer needed to avoid unnecessary Azure storage costs. You can still use prior versions of Azure Compute Gallery images in the Desktop image (template) menu, under Unmanaged ACG image versions.
-
Remove current version after activation: This option removes the current image version automatically after activation.
-
-
-
Replica Count (Per Region): Specify the number of replicas per region.
Note
-
Azure Compute Gallery replicas support a maximum of 20 concurrent clone operations per replica.
-
Ensure that the number of replicas specified meets your deployment requirements. Up to 100 replicas per region are supported.
-
Replicas can only be deployed within the same subscription.
-
-
Backup Version Limit: Specify the maximum number of backup image versions that can be retained.
Note
When a new image version is created, and the old one is saved as a backup, the system automatically manages and limits the number of these backups according to the specified limit. If the limit is reached, the oldest versions are deleted. You can configure this setting in the desktop image settings, Manage versions option.
-
Save current image as a backup: Select this image to retain the existing image as a standalone object and not overwrite it with the new one.
Note
-
This image is not visible or manageable via Nerdio Manager, so be sure to delete it manually when it is no longer needed to avoid unnecessary Azure storage costs.
-
If the current image is stored in Azure Compute Gallery, it is retained with an older version number. If the image is not stored in Azure Compute Gallery, you can find it in the Azure portal > Images. In Nerdio Manager's image selector lists, it is listed under Custom images.
-
-
Install App Attach certificates: Select this option to install all stored certificates on the image VM, if any.
-
Enable App-V client service: Select this option if the VM will use App Attach packages that contain App-V packages.
-
Skip removal of local profiles: Select this option to bypass removing all local user profiles.
Note
During the image creation process, Nerdio Manager removes all local user profiles. This increases the likelihood of Sysprep success. Selecting this option bypasses this step. If there are any partially installed APPX apps on the image VM, Sysprep does to remove them.
-
Enable for Cloud PCs: Select this option to make this image available in Windows 365 Cloud PC service.
Note
The image will be uploaded and tested for compatibility with Cloud PCs. This process can take a long time. There is a limit of 20 images that can be uploaded to Windows 365.
-
Leave desktop image VM running: Select this option to leave the VM running after the Set as image task completes.
Note
This is useful if you want to push OS and application updates to the running VM.
-
Change log: Type the list of changes made to the image.
-
Apply tags: Optionally, enter the Name and Value of the Azure tag.
Note
You can specify multiple tags. The specified tags are applied to image VM, OS disk, network interface, image object, and Azure Compute Gallery image. For details about using tags to organize your Azure resources, see Use tags to organize your Azure resources and management hierarchy.
-
-
Once you have entered all the desired information, select Run now (not scheduled) or Save & close (scheduled).
You can see the job's progress in the logs. For details about the logs, see Desktop Images Change Log Feature.
Nerdio Manager enables you to execute scripts on desktop images.
Note
You can execute a scripted action immediately or run it on a schedule.
To execute a scripted action:
-
From the main menu, select Desktop Images.
-
From the action menu, select Run script.
-
Enter the following information:
-
Schedule: Toggle to turn the scheduler On/Off. See Manage Schedules for Tasks for details about creating a schedule.
-
Scripted Actions: From the drop-down list, select the script you wish to run.
Note
-
Windows scripts are executed via the Azure Custom Script extension and run in the context of the LocalSystem account.
-
Azure runbooks are executed via the Azure automation account and run in the context of the Nerdio Manager app service principal.
-
The following variables are passed to the script and can be used in the PowerShell commands:
-
$AzureSubscriptionId
-
$AzureSubscriptionName
-
$AzureResourceGroupName
-
$AzureRegionName
-
$AzureVMName
-
$ADUsername (if passing AD credentials)
-
$ADPassword (if passing AD credentials)
-
$SATrigger = "RunOnce"
-
$SATriggerMode = "Manual" | "Schedule"
-
$DesktopImageVmName
-
$DesktopImageActiveVersion
-
$DesktopImageStagedVersion
-
-
-
Scripted actions input parameters: If necessary, provide the required parameters.
-
Pass AD credentials: Select to pass your AD credentials to the script being executed.
-
Restart VM after script execution: Select to restart the VM after script execution.
Note
It is preferable to select this option instead of restarting the VM in your PowerShell commands because the Custom Script extension fails if the script restarts the VM.
-
-
Once you have entered all the desired information, select either Run now to execute immediately or Save & close to save the script and execute as per the schedule.
Comments (0 comments)