In many of the articles I write for this blog on using PowerShell to manage Hyper-V, I almost always am running commands locally. The implication is that I am logged on to a Windows Server 2012 system running the latest version of Hyper-V. But in actuality, that is actually not a recommended practice. Instead, we should be leveraging the remote management capabilities of the Hyper-V PowerShell module. Let me demonstrate.
↧