Tutorial: Create a host pool to validate service updates
This content applies to the Spring 2020 update with Azure Resource Manager Windows Virtual Desktop objects. If you're using the Windows Virtual Desktop Fall 2019 release without Azure Resource Manager objects, see this article.
Host pools are a collection of one or more identical virtual machines within Windows Virtual Desktop tenant environments. Before deploying host pools to your production environment, we highly recommend you create a validation host pool. Updates are applied first to validation host pools, letting you monitor service updates before rolling them out to your production environment. Without a validation host pool, you may not discover changes that introduce errors, which could result in downtime for users in your production environment.
To ensure your apps work with the latest updates, the validation host pool should be as similar to host pools in your production environment as possible. Users should connect as frequently to the validation host pool as they do to the production host pool. If you have automated testing on your host pool, you should include automated testing on the validation host pool.
We recommend that you leave the validation host pool in place to test all future updates.
The Windows Virtual Desktop Spring 2020 release currently has trouble enabling and disabling validation environment. We'll update this article when we've resolved the issue.
Before you begin, follow the instructions in Set up the Windows Virtual Desktop PowerShell module to set up your PowerShell module and sign in to Azure.
Create your host pool
You can create a host pool by following the instructions in any of these articles:
Define your host pool as a validation host pool
Run the following PowerShell cmdlets to define the new host pool as a validation host pool. Replace the values in brackets with the values relevant to your session:
Update-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -ValidationEnvironment:$true
Run the following PowerShell cmdlet to confirm that the validation property has been set. Replace the values in brackets with the values relevant to your session.
Get-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> | Format-List
The results from the cmdlet should look similar to this output:
HostPoolName : hostpoolname FriendlyName : Description : Persistent : False CustomRdpProperty : use multimon:i:0; MaxSessionLimit : 10 LoadBalancerType : BreadthFirst ValidationEnvironment : True
Service updates happen monthly. If there are major issues, critical updates will be provided at a more frequent pace.
If there are any service updates, make sure you have at least a small group of users signing in each day to validate the environment. We recommend you regularly visit our TechCommunity site and follow any posts with WVDUPdate to stay informed about service updates.
Now that you've created a validation host pool, you can learn how to use Azure Service Health to monitor your Windows Virtual Desktop deployment.