WVD v2 Add New Session Hosts to Existing Host Pool | Registration Key

Let’s learn today, how to add new session hosts to the existing host pool. This post is applicable only for the Windows Virtual Desktop spring 2020 release (a.k.a WVD v2). The Spring 2020 update uses the Azure Resource Manager (ARM) Windows Virtual Desktop objects.

Host sessions are nothing but virtual machines part of the host pool. I’m planning to add new two session hosts to host pools using Windows Virtual Desktop new experience (a.k.a WVD v2).

NOTE! – Learn more about WVD v2 ARM model architecture.

Add New Session Host

• Login to portal.azure.com
• Search with “Windows Virtual Desktop“.
• Click on Windows Virtual Desktop icon as shown in the below screenshot.

• Click on Session Host node 👉 Select Host Pool.
• Click on the button Session Host.
• Click +Add.

• Use a registration key to add additional virtual machines to this host pool. More details here.
  • Expiration date
  • No registration key has been generated for this host pool

Create Registration key for Host Pool

• You can use the Generate new registration key from the Azure portal WVD application itself.
• Select the Expiration Date 👉 07/07/2020.
• Select the Time 👉 12:00:00 AM.
• Click on OK to generate the registration Key.

• If you want to save the registration key, click on the Download button.
• Click on + Add button to create a new session host VM.
• You don’t have the option to change Subscription, Resource Group, Host Pool Name, Location, and Host Pool Type. These options are already selected for the host pool.
• Click on the next button to continue.

Virtual Machine Configuration

• You don’t have the option to change:
  • Name Prefix (prefix name of the VM), Virtual Machine Size (Azure VM template), Image Type, Image, OS Disk Type, Use Managed Disks.
• You have the option to select and change:
  • Resource Group, Virtual Machine Location (Azure Region), and Number of VMs for new session hosts.

Network & Security Configurations

I normally keep all the following settings the same for all the VMs in the host pools. More details following in the following post 👉 WVD v2 Admin Experience Create New Host Pool | Workspace | Session Host.

• Select the already created Virtual Network 👉 WVD_PoC_VLAN1.
• Select the Subnet from the drop-down 👉 Default.
• Select Public IP 👉 NO.
• Select Network Security Group (NSG) as per your organization standard 👉 Basic.
• Select Public inbound ports option 👉 No
• Specify domain or unit to YES
  • Select yes to join virtual machines to a specific domain or organization unit (OU).
  • Select no to not join the virtual machines to an OU.
    • If you select no, the domain name will use the suffix of the Active Directory domain to join UPN by default. For example, the user “vmjoiner@contoso.com” would get the default domain name “contoso.com”.
• Enter the Domain name for Domain to join – HTMD.Local (where HTMD.local is my domain name).
• Enter the OU path 👉 OU=WVD,OU=AAA UK,OU=Org,DC=HTMD,DC=local
• Enter the AD Domain join UPN 👉 anoop@HTMD.Local.
• Enter the password 👉 ********
• Click on the NEXT Tags button.
• Click on the NEXT Review + Create.

• Click on the Create button after the validation passed banner message.

Deployment in Progress WVD v2 – Session Host

• Deployment in progress 👉 Additional session hosts are being added.

Results

• The new two Session hosts (VMs) are added to the host pool.

Personal Desktop Assignment

Update-AzWvdSessionHost -HostPoolName $hostpoolname -Name $sessionhostname -ResourceGroupName $resourcegroupname -AssignedUser $userupn

Resources

• WVD Architecture Changes for v2 | New Portal Admin Experience
• WVD Management Using Visual Studio Code Instead of PowerShell ISE
• Windows Virtual Desktop technical deployment (ARM-based model) walkthrough
• WVD Firewall Proxy Policies
• More WVD Guides – https://www.anoopcnair.com/wvd/