0% found this document useful (0 votes)
12 views2 pages

PowerShell Direct for Hyper-V Management

This document discusses managing Windows virtual machines remotely using PowerShell Direct from a Windows 10 or Windows Server 2016 host. It describes how to create and exit PowerShell Direct sessions using PSSession cmdlets or run scripts and commands using Invoke-Command. PowerShell Direct allows managing virtual machines regardless of network configuration by creating remote PowerShell sessions.

Uploaded by

jj2473
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
12 views2 pages

PowerShell Direct for Hyper-V Management

This document discusses managing Windows virtual machines remotely using PowerShell Direct from a Windows 10 or Windows Server 2016 host. It describes how to create and exit PowerShell Direct sessions using PSSession cmdlets or run scripts and commands using Invoke-Command. PowerShell Direct allows managing virtual machines regardless of network configuration by creating remote PowerShell sessions.

Uploaded by

jj2473
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd

Manage Windows virtual machines with

PowerShell Direct
Catherine Watson|Last Updated: 7/1/2016
|
2 Contributors

IN THIS ARTICLE
Create and exit a PowerShell Direct session using PSSession cmdlets
Run script or command with Invoke-Command cmdlet
What's required to use PowerShell Direct?
See Also
Applies To: Windows 10, Windows Server Technical Preview

This is preliminary content and subject to change.


You can use PowerShell Direct to remotely manage a Windows 10 or Windows Server 2016
Technical Preview virtual machine from a Windows 10 or Windows Server 2016 Technical Preview
Hyper-V host. PowerShell Direct allows Windows PowerShell management inside a virtual
machine regardless of the network configuration or remote management settings on either the
Hyper-V host or the virtual machine. This makes it easier for Hyper-V Administrators to automate
and script virtual machine management and configuration.
There are two ways to run PowerShell Direct:
Create and exit a PowerShell Direct session using PSSession cmdlets
Run script or command with the Invoke-Command cmdlet
If you're managing older virtual machines, use Virtual Machine Connection (VMConnect) or
configure a virtual network for the virtual machine.

Create and exit a PowerShell Direct session using PSSession


cmdlets
1. On the Hyper-V host, open Windows PowerShell as Administrator.
2. Use the Enter-PSSession cmdlet to connect to the virtual machine. Run one of the following
commands to create a session by using the virtual machine name or GUID:
Enter-PSSession -VMName <VMName>
Enter-PSSession -VMGUID <VMGUID>

3. Type your credentials for the virtual machine.


4. Run whatever commands you need to. These commands run on the virtual machine that you
created the session with.

5. When you're done, use the Exit-PSSession to close the session.


Exit-PSSession

Run script or command with Invoke-Command cmdlet


You can use the Invoke-Command cmdlet to run a pre-determined set of commands on the virtual
machine. Here is an example of how you can use the Invoke-Command cmdlet where PSTest is the
virtual machine name and the script to run (foo.ps1) is in the script folder on the C:/ drive:
Invoke-Command -VMName PSTest

-FilePath C:\script\foo.ps1

To run a single command, use the -ScriptBlock parameter:


Invoke-Command -VMName PSTest

-ScriptBlock { cmdlet }

What's required to use PowerShell Direct?


To create a PowerShell Direct session on a virtual machine,
The virtual machine must be running locally on the host and booted.
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 Technical Preview,
or higher version.
The virtual machine must run Windows 10, Windows Server 2016 Technical Preview, or
higher version.
You can use the Get-VM cmdlet to check that the credentials you're using have the Hyper-V
administrator role and to see which VMs are running locally on the host and booted.

See Also
Enter-PSSession
Exit-PSSession
Invoke-Command

You might also like