How to dynamically update session hosts in an existing host pool
Do you have an existing Windows Virtual Desktop where you want to replace the session host virtual machines with new images?
You could build a new host pool with the new session host VM's and present the new icon to users and get them to test and then switch them over. That's not ideal as users need to launch this new desktop which could lead to confusion.
However what you can now do is use an "update" ARM template to dynamically replace the VM's in the existing host pool with no other changes being made to it and no or very little user interaction.
This template actually builds any number of new session hosts into the same host pool, and then will either deallocate or delete the existing VM's. If you choose delete it will delete the VM's and related storage which means there will be no residual costs related to the VM's. It also deletes all other infrastructure components. It will also send a message to all conencted user sessions.
Have a look at this video which goes through the process:
I get asked all the time "how do I re-assign a personal session host in WVD"? The official answer is you don't. However, this can be easily achieved. The steps below are currently: the quickest way to achieve this. configured all in one place via the Azure portal, using a little used feature. does not require a reboot. These simple steps will get the registration token, remove the session host from the host pool, then update the registry with the required settings and force the re-registration of the session host with the WVD control plane, by restarting the specific responsible service. If you have done anything with WVD to this point, you will be aware there are two types of host pools: Pooled - designed for a multi-session OS and any user can login to any VM in the pool. Personal - designed for a single session OS and the Session hosts are assigned, either automatically as a user connects or they can be directly assigned ahead of time. Once assigned that VM is dedicat
On Wednesday July the 14th 2021 we announced the public preview of Azure Active Directory domain join for Azure Virtual Desktop. This post discusses how to set this up and troubleshooting tips. Let's, just start with some background. Azure Active Directory Join for the Azure Virtual Desktop session hosts has been the number one feature request from customers from day one of Windows Virtual Desktop as it was known at launch, followed very closely by Microsoft Endpoint Manager - specifically Intune managing those session host Virtual machines. This public preview brings both of those capabilities. Why are we doing this? Currently AVD requires both Azure Active Directory (AAD) as well as traditional Active Directory Domain Services (AD DS). AD DS can come in one of two formats: Traditional AD DS from Windows server. The AD DS domain controllers can either be located on-prem and accessed over a site-to-site VPN or ExpressRoute. Or they can be virtual machines located within Azu
If like me you have come from an infrastructure background and always built servers, virtual machines etc. manually, then the thought of doing all that hard work via code does not always come naturally. Building out a gold image was a time intensive process with lots of manual steps plus deploying that at scale needed tools like Citrix MCS, or tools within the Hypervisor or others. But if you have done anything in the public cloud you will have heard of “Infrastructure as Code! and if you have done anything in Azure then you will likely have heard of Azure DevOps, which provides people to have continuous integration, testing and delivery, the ability to deploy code, or whole applications with the press of a button. But how can this apply to a Virtual Desktop capability when you are deploying hundreds or thousands of Azure IaaS VM's as part of a Windows Virtual Desktop deployment? Well not coming from a development background, but working at Microsoft as a Windows Vir