When configuring a host pool to deploy session hosts to Availability Zones, the current behavior of deployment is that Nerdio will deploy session hosts to zones which the SKU is available. However, when a SKU is not available on a zone, Nerdio will retry the deployment 3 times to the same zone before ultimately failing and cleaning up the the VM resources (NIC / OS disk).
This needs to be fixed so when a SKU is not available in a zone, it moves to the next available zone. Here's a screenshot of what it looks like when it errors out on a zone. It then attempts to deploy it an additional 3 times. After the third time, it should then place the VM in the other zones that have the SKU available.
Note that this capacity problem is not related to quotas, it is a specific datacenter level problem that Microsoft is aware of and there's no getting around it but trying again or placing the VM into another zone.
Comments (1 comment)