Forum Discussion
How often should AVD host pools be replaced?
It sounds like you may be just updating the actual session hosts themselves, which is never a good thing. The only exception to this rule is if you are managing the session hosts individually, which brings its own problems.
If I were you, I would try to work with that team to create a new image that is the proper Windows 11 Mult-Session image and re-deploy that image on a monthly basis with the required application and security updates; that's how most people do it.
virtualmanc My understanding is that the host pool resource doesn't need to be torn down with a new host pool created each time a new image is deployed. It can remain in place for as long as it is needed.
What I mean by deploying a new image is that the existing session hosts are deleted and new session hosts are created in their place. I don't mean writing the new image to the existing VMs.
Let's say I have HostPool01. It contains SessionHost01 and SessionHost02. I have a new image to deploy.
Do I delete SessionHost01 and SessionHost02 from HostPool01 then deploy the new image to SessionHost03 and SessionHost04 within HostPool01?
Or...
Do I delete SessionHost01, SessionHost02, and HostPool01. Then create HostPool02 and deploy the new image to SessionHost03 and SessionHost04 within it?
In the first scenario, will the host pool, as a separate entity (not the session hosts), degrade?