Today in Single User Desktop (Personal) host pools building a new session host sets the selected values for Image, VM Size, OS Disk and Resource group as default for all subsequent builds to follow unless it is manually changed during the following build. It will always default to whatever values the most recent build had selected. This poses a problem for customers like us who have many separate linked subscriptions, resource groups, VNets in several different regions. If an admin makes a mistake and builds an AVD in a resource group in one region, but accidentally selects a VNet that's in a completely separate region, then not only is their build incorrect, but all VMs built thereafter will be built incorrectly as well, if the admin was not careful to double check the selections.
I think a simple way to help prevent this is to allow admins to set default build values. (Maybe in the Host Pool properties>VM Deployment section?). This would keep the default selected values consistent, but still allow admins to manually change them during AVD builds if they really need to.
Set Default AVD Build Values in Pool Settings for Single User Desktop Host Pools
I completely agree—this issue has caused problems in our environment as well.
I was about to submit a similar feature request but decided to check if anyone else had already raised it, and I found your post.
The only adjustment I’d suggest is to place the default settings under Auto Scale, as that’s where similar settings are currently configured for a host pool, rather than in properties.
Hi Brian Kraemer Paul Ofoche - I'm not fully grasping the issue. Are we talking about manual creation of new hosts, automatic, or both? Is your vision that the defaults for build should be optional somehow, or that we should surface a UI element allowing admins to pick their options?
Please help me to understand the circumstances where this occurs and your desired outcomes. Thank you!
---
#Update - I think the post here has helped to clarify, but let me know if you have more info to share. Thank you.
Hi Toby Skerritt
I see that the two posts together have given a clearer idea of what's being asked for.
The request is for manually adding VMs to a host pool. When doing this, the majority of the time, the user will want the machine to conform to the pre-existing standards of the host pool. In exceptional cases the settings will be altered. Therefore, it would be preferable for the "add new session host" default properties to always revert the auto scale settings of the host pool.
This applies to both pooled and personal
Toby Skerritt and Paul Ofoche that is exactly correct. This is for manually adding VMs to host pools as Paul mentioned. We would like the default build values on manual adds to be something administratively set in settings or autoscale settings as opposed to simply defaulting to the values of the previous build. It helps prevent incorrect build configurations from snowballing into bigger issues. Thanks.
Please sign in to leave a comment.
Comments (4 comments)