PowerShell Direct lets you remotely connect to a Virtual Machine running on a Hyper-V host, without any network connection inside the Virtual Machine. PowerShell Direct uses the Hyper-V VMBus to connect inside the Virtual Machine. This feature is convenient if you need it for automation and configuration for Virtual Machines or if you, for example, messed up network configuration inside the virtual machine, and you don’t have console access.
Right now, there are two ways to use PowerShell Direct:
Create and exit a PowerShell Direct session using PSSession cmdlets
Run script or command with the Invoke-Command cmdlet
Use the PowerShell Direct session to copy files using the copy-item cmdlet.
The virtual machine must be running locally on the Hyper-V host and must be started.
You must be logged into the host computer as a Hyper-V administrator.
You must supply valid user credentials for the virtual machine.
The host operating system must run Windows 10, Windows Server 2016, or a higher version.
The virtual machine must run Windows 10, Windows Server 2016, or a higher version.
PowerShell Direct examples
You can open a new interactive PowerShell Direct Session:
Remember it, this is not the same as PowerShell Remoting, even if it uses the same cmdlets. With that, not everything is working using PowerShell Direct, for some scenarios, PowerShell Remoting works differently. If you want to do this with Linux virtual machines, there is a tool calledhvc.exe, which allows you to do the same.
If you want to know more about PowerShell Direct, check out theMicrosoft Docspages.