Microsoft
Dear Davanna-White after some testing of the 2311 release I am quite happy with the improvements.
In addition to my / customer feedback above I would like to raise that the next release really needs to focus to make Hyper-V and Failover Clustering consoles obsolete. Customers are still unsatisfied to manage their Azure Stack HCI or S2D clusters using WAC.
This is mainly because of performance and frequent fallbacks required to the legacy tools, which greatly reduce the adoption of WAC a prime tool for VM & Cluster Management.
- speed of listing VMs is still not up to par with 2311, despite announcements of improvements in this regards.
I would personally plea to implement a database for WAC. Just in case the PG plans to replace the on-prem WAC gateway with an Azure cloud based model, this could be fully serviced.
- general performance can be sluggish all over the place (Gateway has 4 vCPU, 8 GB dynamic, 2,5 GB used, running on NVMe Storage Spaces
- /tools/hciservers - the ability to resume a node and fall back roles is still absent. This was included some versions ago. Means currently users have to fall back to PowerShell or MMC to resume a paused node and use the feature to failback roles
> https://feedback.azure.com/d365community/idea/77e80631-0bab-ee11-92bc-000d3a037f01
- In previous versions we had a "reminder / popup" in WAC that showed a warning when storage jobs were still running / pending
I can nowhere find the status of running storage jobs.
> https://feedback.azure.com/d365community/idea/2aa82c79-0cab-ee11-92bc-000d3a037f01
- /tools/hciservers the state of servers "down", "maintenance / paused", takes much longer as in MMC, including disks and CSV states. Is this due pending Storage Jobs?
> https://feedback.azure.com/d365community/idea/2aa82c79-0cab-ee11-92bc-000d3a037f01
- tools/virtualmachines/inventory - there is no ability to add VMs of a host to clustered VMs, or remove them from cluster (add-/remove-ClusterRole)
> https://feedback.azure.com/d365community/idea/f9744bef-06ab-ee11-92bc-000d3a037f01
- Remote Desktop still does not work correctly in WAC for VMs and local server management. I believe to understand the root cause of this, as we had the same issue with Dell IDRAC. The keyboard language of the OS is not the issue here but the translation of the keystrokes into the OS. Means if you have a physical keyboard with german language, regardless the OS language and keyboard settings, you will end up with wrong keyboard layout.
Dell fixed this in IDRAC 7.0.30.0 or later by introducing an option to select the language of the physical keyboard the user is using.
The keyboard language issue is about 2 years old now and has been marked solved by Jeff-Woolsey in the previous uservoice portal, but others kept reporting it is not fixed.
I hope this will help to remediate the issue, as it did for Dell.
> https://feedback.azure.com/d365community/idea/2ae44662-0dab-ee11-92bc-000d3a037f01
- Remote Desktop misses the ability using the clipboard in basic session and it seems there is no advanced session, not matter it is enabled on Hyper-V host or not.
> https://feedback.azure.com/d365community/idea/5b7960b8-9d2f-ed11-9db0-000d3a1f4287
- /tools/virtualmachines in many occassions running VMS do not show any information about virtual hard disks. You cannot configure them, create snapshots etc.
> https://feedback.azure.com/d365community/idea/334c81ba-d95b-ee11-a81c-000d3ae5ae95