Microsoft
Amazed by this new release! Thanks for all your efforts. Still hope WAC is moved as public project on github. Code changes, issues, ideas and improvements could be requested by PRs from partners, users, OEM and fans of WAC.
I still hope most of the things are PowerShell under the hood, isn't it?
New features in 2306 that are not listed above:
+ ability to set S2D pool warning threshold
Feedback: the threshold should be a free integer, slider see also: https://www.thomas-krenn.com/de/wiki/Azure_Stack_HCI_Warnung_im_Windows_Admin_Center_-_Storage_Pool_is_running_out_of_capacity?xtxsearchselecthit=1
Usecase: setting the value manually, result into no visibility of the value set (empty dropdown in WAC).
+ ability to set Cluster-wide Live Migration settings: New Cluster-Wide Control For Virtual Machine Live Migrations In Windows Server and Azure Stack HCI - Microsoft Community Hub
+ Storage Migration for VMs now unlocked (unlike Failover Cluster / Hyper-V MMC require CredSSP)
"Check it, and let us know what you would like to see next on the virtual machine tool!"
Thanks for asking, here we go Theo_Tran 🙂 Generally speaking the improvements we received in the past 2 years already, are tremendously helpful. Context Menu, Domain Join, Cloning VMs (with a caveat, listed below)
Virtual Machine tool
- faster enumeration of (clustered) VMs. Currently this is my top priority demand from customers to leave failover cluster mmc alone.
- I have heard moving more than one VM (Live or quick migratrion) is not possible, is this true?
> https://feedback.azure.com/d365community/idea/08ea5c95-cf2f-ee11-a81c-000d3ae37d1e
- dynamic progress on VM migration (optional column for progress in %, per VM, fetched from Hyper-V MMC)
- ability to edit VM paths for disks, configuration files, smartpage, snapshots
usecase: it could happen that CSV or paths get renamed and it is quite hard to fix this as the Hyper-V config files aren't xml or json based
- when cloning VMs all paths should be respecting the structure and naming of the new VM. I have heard this is not the case.
basepath\vm name\virtual machine + basepath\vm name\virtual hard disks etc
> https://feedback.azure.com/d365community/idea/33a9fb51-06ab-ee11-92bc-000d3a037f01
- ability to add scsi controllers and attach virtual disks to a controller for better performance (disk queue)
> https://feedback.azure.com/d365community/idea/08c9fd7b-0eab-ee11-92bc-000d3a037f01
- force turn off (currently only doable via hcsdiag and vm id) - hypervisor competition offers this feature
> https://feedback.azure.com/d365community/idea/33a9fb51-06ab-ee11-92bc-000d3a037f01
Clustering
- ability to manage S2D disk and pool operations. some of these possible via Server Manager
remove volume
repair volume
clear metadata of removed / stale devices (Microsoft Script Clear-PhysicalDiskHealthData.ps1)
Add Disk / remove disk from S2D pool
Ability to specify Livemigration networks (as in Hyper-V MMC, at best cluster-wide, as with MaxLivemigration count since Sept. 2022)
> https://feedback.azure.com/d365community/idea/4c7960b8-9d2f-ed11-9db0-000d3a1f4287
Volumes / CSVs
- maintenance mode
- test failover
- repair / chkdsk for NTFS volumes (in maintenance mode)
- see / set description (label) of a volume
- add / remove disk from CSV
- (re)name CSV mounting points (with consequences) when turning a disk to a CSV
- consider formatting CSV volumes with 64k ReFS clustersize (better perf for VM, snapshots, SQL workloads etc)
- show CSV ReFS Version (column, details)
- (implemented in 2306) Adding a volume should mount the CSV with the same name in Clusterstorage, and also rename the NTFS / ReFS volume label accordingly
> https://feedback.azure.com/d365community/idea/4c7960b8-9d2f-ed11-9db0-000d3a1f4287
Some of these might be already addressed, as I am currently evaluating the changes of 2306.
Happy clustering / Azure Stacking 😉 (like your term cblackuk1)