On the back of their newly created cheat sheet, James Lewis and Filipe Lopes explain the importance of having the right information to hand for Hyper-V when using the task-based command-line shell and scripting language, PowerShell:
Back then (and now)
Since the rise of VMware in the early noughties, most personal labs/virtualization ran on VMWare workstation or ESX (GSX for those from that era), but Hyper-V is now built into Windows 10.
Handling of PowerShell today
You might be expecting a nice graphical interface to work with, but that’s not such the case now- the days of DOS-type long commands have now returned! System admins now need to know their stuff again, as opposed to just clicking around for the right option.
Adoption of Hyper-V technology
With the ability to turn on virtualisation technology on most desktop computers, more and more junior or trainee staff are using it to learn with. When things do go wrong, looking up a specific event log or being pointed to an underlying issue which isn’t directly related to Hyper-V (as opposed to searching forums which you mostly have to sign up or contribute to) can save hours of work.
Additionally, large style deployments can be implemented using pre written PowerShell scripts- this allows consistency (crucial when trying to pin point that darned issue) across all hypervisors or deployed services.