Pad Session host name with Leading Zeros
When adding session hosts to a pool you declare a prefix and the template will append an incrementing number to the end. but this number is not a consistent length due to the lack of leading zeros. and in large host pool, this causes the hosts to not sort properly Current Example of Bad Sort Desired Test-VM-1 Test-VM-1 Test-VM-001 Test-VM-2 Test-VM-10 Test-VM-002 Test-VM-3 Test-VM-11 Test-VM-003 Test-VM-4 Test-VM-12 Test-VM-004 Test-VM-5 Test-VM-2 Test-VM-005 Test-VM-6 Test-VM-3 Test-VM-006 Test-VM-7 Test-VM-4 Test-VM-007 Test-VM-8 Test-VM-5 Test-VM-008 Test-VM-9 Test-VM-6 Test-VM-009 Test-VM-10 Test-VM-7 Test-VM-010 Test-VM-11 Test-VM-8 Test-VM-011 Test-VM-12 Test-VM-9 Test-VM-012
Provision AVD VM's with requested drive size, rather than resizing/upsizing
When building new Azure Virtual Desktop hosts via the AVD portal, if you select an OS disk size for the host that is anything other than the default 128GB, the host is provisioned with a 128GB disk and then resized/upgraded as part of the VM's build process. The problem with this is that the OS volume is still the default 128GB and needs to be manually extended after the host has been built. This detracts from the otherwise impressively polished process of provisioning AVD hosts in the Azure portal, where it's clear a lot of automation already takes place as the VM is created and set up for AVD. I have not been able to find mention of the need to extend the OS Volume after provisioning in the Azure Virtual Desktop documentation, nor was it clear that this would be required when selecting 256GB OS Disk size during host creation. If the host were created with a 256GB OS Disk from the beginning (rather than upsizing) I anticipate this would solve the need to extend the OS volume manually afterward. Alternatively, if its possible to automate extending the OS volume to utilise the full disk size after it has been resized that would also address the problem
Save settings and RDP data locally or to the cloud
Have the ability to encrypt and save settings and RDP data (IP Address, optional credentials, etc.) locally or to the cloud so as to enable an easy and quick reprovisioning of the app on a new device. Imagine having to setup new RDP connection profiles for 50+ devices. It's time consuming.Can not connect toserver
I have tried to connect to the server and it give me error code 0x3000066 unable to connect. i have tried the connection other ways and it has worked fine. I was told the update broke the connection by my hosting techs. They said I need to download the old version in order for this to work. This has been problematic for me as I use this everyday at home to help my staff and I have been unable to do what I need to do.
