Migrate legacy VDI to AVD

Nerdio Manager provides administrators a straightforward method to migrate source VMs from their current VDI solution (for example, Omnissa or Citrix) to AVD. This guide outlines the steps, requirements, and considerations necessary to complete this process.

Prerequisites

      System and environment requirements

Ensure that the following system and environment requirements are met before starting a migration:

• Source VMs run in Azure infrastructure only.

• Source VMs originate from any legacy VDI platform.

• An Azure Virtual Desktop host pool exists.

• The AVD host pool supports single‑session.

• Source VMs meet Azure Virtual Desktop requirements for operating system and configuration.

      Role-based access control (RBAC) and permissions

            Nerdio Manager roles

This procedure requires the AdminNerdio Manager role to carry out the tasks outlined below.

            Azure built-in roles

No additional Azure built-in role assignment is required.

      Preparatory steps

            Resource groups

Before starting the migration, verify the following resource group conditions have been met:

• Source VMs reside in Azure resource groups linked in NME.
  

• Source VM resource groups do not have Azure resource locks that prevent modification.

• You can view and select the source VMs from NME within Migrate > Sources.

• Source VNET linked in NME.
  

If any of the source resource groups are not linked, follow the instructions at Azure Environment: linked networks and resource groups to link them.

Procedure

Migrate an individual source:

1. In Nerdio Manager, navigate to Migrate and select Sources from the menu.

2. Locate the source VM you wish to work with, then initiate the discovery script by selecting Discover from the more optionsmenu .

3. From there, initiate the migration using one of the following options:

   • Select the Migrate icon to start a migration for an individual VM.

     Note: Alternatively, select Migrate from the more options menu to start an individual VM migration.

   • To migrate multiple VMs, select two or more checkboxes next to the desired VMs and then select + New Migration in the bottom right-hand corner of the page.

4. In the Source & Target section of the Migrate VM wizard:

   • Select Azure Virtual Desktop (Personal Host) from the Migration target drop-down list.

   • To create a backup of the VM, check the Take snapshot of source VM(s) before migration checkbox.

     Caution: Nerdio strongly recommends administrators use the snapshot feature to prevent data loss. Snapshot storage costs may apply. Administrators can enable the Remove snapshot toggle and set a date to automatically delete the snapshot once the checkbox is selected.

   • Select Next.

5. In the User Assignments section:

   • The field next to the VM name displays the assigned user.

   • To change the user, select the cancel icon next to the user name, then select a different user from the drop-down list.

     Note: Each individual user can only be assigned to one VM.

   • Select Next.

6. On the Destination page, select a personal host pool from the Host pool destination drop-down list. This selection defines where Nerdio Manager registers the VM as a session host VM.

   • To move the VM, enable the Move VM toggle.

   • Designate the resource group and VM size using the associated drop-down lists.

   • Select Next.

7. In the Notifications section, configure emails to be sent to users once the migration is complete:

   • Enable the toggle next to Notify end user when migration is complete.

   • Select the mailbox you would like the emails sent from in the corresponding drop-down list.

   • In the Message to end user field, enter a message informing the user that the migration is complete and their desktop is ready for use.

8. On the Review step, ensure the migration details are configured as desired, then select Submit.

Need help?

Raise a support ticket for this item.