On the back of their newly created PowerShell cheat sheet, James Lewis and Filipe Lopes explain the importance of having the right information to hand when using Hyper-V VM technology.
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.
PowerShell commands are no longer the same
You might expect a nice graphical interface to work with, but that’s not the case now- the days of long DOS-type commands have returned! System admins now need to know their stuff again, as opposed to 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 training with it. 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.