SOLVED

Why Un-identical VMs Can be part of a Hostpool

Copper Contributor

Team, 

 

I have few questions which I observed. I know recommendations indeed as using identical VMs as part of a hostpool. But Still trying to understand that why AVD is allowing non identical VM's as part of same hostpool. Any specific use cases which I am missing for this non-identical configuration? 

2 Replies
best response confirmed by Narender_Singh (Copper Contributor)
Solution
Interesting question. What if the business is a 24-hour shop. They have one size/version of Session Hosts that users are working on and a new size that you're working on moving users over to without interrupting their work. One option is to add the new Session Hosts to the Host Pool, gradually configure drain mode on the old size/version, and remove it.

In general, having different Session Hosts in the same Host Pool is not recommended, as load balancing will either overprovision users to the smaller Hosts or under-provision, the larger hosts, depending on how you have it configured.

This is also an unsupported configuration per Microsoft.
@Orion - Thanks for the response and agreed with you. Cheers!!!
1 best response

Accepted Solutions
best response confirmed by Narender_Singh (Copper Contributor)
Solution
Interesting question. What if the business is a 24-hour shop. They have one size/version of Session Hosts that users are working on and a new size that you're working on moving users over to without interrupting their work. One option is to add the new Session Hosts to the Host Pool, gradually configure drain mode on the old size/version, and remove it.

In general, having different Session Hosts in the same Host Pool is not recommended, as load balancing will either overprovision users to the smaller Hosts or under-provision, the larger hosts, depending on how you have it configured.

This is also an unsupported configuration per Microsoft.

View solution in original post