Move VMs between zones within the region

Avatar
Franklin Azogue

Good afternoon, Team! 

Due to multiple resource constraints, the operations have become a daily challenge.  

We request the implementation of an option that allows us to move our AVDs between zones (1/2/3) within the same host pool/region.  

We have enabled the deployment of VMs across availability zones at the host pool level. Consequently, some of these are located in zone 2, where Microsoft has encountered issues with the disk controller, resulting in the VMs experiencing multiple disconnections daily.  

As a remediation, we have had to assign a new VM within the same host pool, avoiding zone 2. The complication arises from the fact that the user is a developer with numerous projects. The specifications of his AVD are 8 cores/64 GB RAM with a Premium disk of 4 TB capacity, so the installation of his development tools and the transfer of his data require significant time, leading to a decline in productivity.  

The implementation of this requested option would be greatly appreciated.  

Regards,

Franklin Azogue

1

Comments (1 comment)

Sort by
0
Avatar
Paul Nicholls

Just as Franklin has requested - it would be an excellent addition to Nerdio to get this implemented.

We have a similar requirement and with bespoke, heavily customised personal desktop AVD machines, following the standard ‘destroy and redeploy’ suggestion from Microsoft is very disruptive and messes up naming, rejoining pools etc..

Even if Nerdio did this ‘behind the scenes’ (i.e. destroyed the VM, kept the OS disk and name, recreated the VM with the same name, re-added the user back in and reattached the disk) on the way to deploying the VM in a different availability zone, it would be an incredibly useful value-add above native AVD functionality.

We've had multiple capacity issues in UK South Zone 3 and I was flabbergasted this basic functionality isn't included in Azure natively already.

In my head when you deployed a session host using the ‘All Zones’ option, I was expecting that if the VM cannot be allocated a session that it would automatically transfer to another zone.

The reality is that it just does a ‘round robin’ type of allocation once at time of deployment and stays there indefinitely.

Please sign in to leave a comment.