[Forum FAQ] Introduce Windows Powershell Remoting

Question

This article will introduce three methods of Windows Powershell Remoting:
Method 1: WMI
Remoting Cmdlet: Get-WMIObject
Protocols: WMI/RPC/DCOM
Port: Random port
Data Encryption: Clear text
Note: No need of the WinRM’s installation and configuration
Method 2: PowerShell Remoting Commands
Remoting Cmdlet: Invoke-Command
Protocols: HTTP (wsman), MIME, SOAP, XML
Port: 5985
Data Encryption: Encrypted
Note: Support any cmdlets in the parameter scriptblock, however, need the computer install WinRM, and also need to configure the WinRM on the remote computer.
Method 3: PowerShell Remoting Interactively
Remoting Cmdlet: Enter-PSSession
Protocols: HTTP (wsman), MIME, SOAP, XML
Port: 5985
Data Encryption: Encrypted
Note: Support any cmdlets, all cmdlets you type are executed as if they were typed on the console of the remote computer. However, need the computer install WinRM, and also need
to configure the WinRM on the remote computer.

Answer 1

2. Powershell remote in the same domain with WinRM installed:  Invoke-Command, Enter-PSSession
2.1 PowerShell Remoting Commands: Invoke-Command
If you only have a couple of commands to execute on the remote computer in the same domain, you can use the
Invoke-Command cmdlet.
For example: Server1 want to remote manage Server2
1) Enable powershell remoting on Server2
Launch Windows Powershell as “Run as Administrator” on server2, and run:
Enable-PSRemoting –Force
Note:  
In Server 2012 (but not Windows 8), PowerShell remoting is enabled by default, so you don't need to do anything.
2) Run invoke-command on server1
Invoke-Command -ComputerName server2 -Credential domain\username -ScriptBlock {get-process}
If the user account run with Powershell has the admin permission, there is no need to specify the credential parameter.
The script above will run the cmdlet “get-process” on server2, and a temporary connection will be built, the result returned to server1, and the connection broken.
If you want to run powershell script .ps1 file on server2, however, this script is stored on server1, you can achieve as below:
Invoke-Command -ComputerName server2 -Credential domain\username -FilePath d:\1.ps1
2.2 PowerShell Remoting Interactively: Enter-PSSession
To work interactively, use
Enter-PSSession to connect to a remote session, all the cmdlets you typed in your local console is executed on the remote system until you leave the remote session by using
Exit-PSSession.
After configure the WinRM on server2, you can run
enter-pssession on server1 (Figure 3):
Figure 3:  remote with enter-pssession
2.3 Powershell remote with Pssession:  New-Pssession
Whenever you use Windows PowerShell Remoting with the ComputerName parameter, a temporary session is created for you and used only for this particular command. Once the command
completes, the session is automatically closed.
If you start to access remote systems more often or would like to keep the session state, a more efficient way is to create sessions yourself and keep them around until you no longer
need them. To achieve this, instead of specifying the parameter computername, you can also specify Pssession in the Session parameter of the cmdlets
invoke-command and enter-pssession (Figure 4).
Figure 4:  persistent session
If there is no need to use the Pssession, you can use the cmdlet
Remove-PSSession to close the session.