Forum Discussion
Personal Desktops
No issue scaling up/down. The main thing you want to watch for is if you are using the ds series and provision premium ssd disks, you won't be able to scale to a size that doesn't support premium disks (aka sku's without the s).
I provisioned a WVD initially on an E sku then swapped it for a B (bursting) sku as it was a better price/performance for my clients work habits.
In some cases to see all available sku's you need to shutdown the vm, resize then boot it back up.
As for mixing sku's in a pool. The main issue you might find is how it load balances. They just have a basic breadth/depth load balancing option. If you have one machine larger, to my knowledge there isn't a way to say machine A gets 70% of logins while machine B (smaller) gets 30% (assuming multi-session). If these are assigned vm's then basically ignore what I've posted above.
https://docs.microsoft.com/en-us/azure/virtual-desktop/host-pool-load-balancing
No error for either. It was more a question around supportability of the two scenarios
i.e.
Are there any support concerns with changing the SKU size of a single session host within a host pool?
Are there any support concerns with changing the SKU size of session hosts of a subsequent ARM deployment into an existing Host pool. i.e. existing session host SKU is D2s v3 and new session hosts will be D4s v3. So in effect, a mix of SKU's in same Host pool.
No issue scaling up/down. The main thing you want to watch for is if you are using the ds series and provision premium ssd disks, you won't be able to scale to a size that doesn't support premium disks (aka sku's without the s).
I provisioned a WVD initially on an E sku then swapped it for a B (bursting) sku as it was a better price/performance for my clients work habits.
In some cases to see all available sku's you need to shutdown the vm, resize then boot it back up.
As for mixing sku's in a pool. The main issue you might find is how it load balances. They just have a basic breadth/depth load balancing option. If you have one machine larger, to my knowledge there isn't a way to say machine A gets 70% of logins while machine B (smaller) gets 30% (assuming multi-session). If these are assigned vm's then basically ignore what I've posted above.
https://docs.microsoft.com/en-us/azure/virtual-desktop/host-pool-load-balancing
mattplan8Thanks. Pretty much what I thought. My infrastructure is more simplified with respect to load balancing as I'm predominantly using personal desktops with direct assignment. But your point about available SKU's with SSD's is a good one.
- You should evaluate/consider the bursting skus if they are dedicated desktops (because its more likely they only get used for 8-10hrs a day).
On reserved instance the discount is good and the burst performance is quite good as well. Just my 2 cents!