SSH-based remoting (PowerShell 7+)

Introduction

SSH-based remoting lets you run PowerShell commands on another computer safely over the network. It helps you manage computers without sitting in front of them.

You want to fix or check a remote server without going there.

You need to run scripts on many computers from your own machine.

You want to automate tasks on remote computers securely.

You manage computers in different locations and want to connect easily.

You want to avoid complex setup and use a simple secure connection.

Syntax

PowerShell

Enter-PSSession -HostName <remote-computer> -UserName <user>
Invoke-Command -HostName <remote-computer> -UserName <user> -ScriptBlock { <commands> }

Use Enter-PSSession to start an interactive session on the remote computer.

Use Invoke-Command to run commands or scripts remotely without interactive mode.

Examples

Starts an interactive session on the remote computer named server01 as user adminuser.

PowerShell

Enter-PSSession -HostName server01 -UserName adminuser

Runs the Get-Process command on server01 and shows the result locally.

PowerShell

Invoke-Command -HostName server01 -UserName adminuser -ScriptBlock { Get-Process }

Runs the hostname command on the remote computer using its IP address.

PowerShell

Invoke-Command -HostName 192.168.1.10 -UserName adminuser -ScriptBlock { hostname }

Sample Program

This runs a simple command on your own computer using SSH remoting. It prints a greeting message from the remote session.

PowerShell

Invoke-Command -HostName localhost -UserName $env:USERNAME -ScriptBlock { "Hello from remote session!" }

Important Notes

Make sure SSH server is installed and running on the remote computer.

You need to have SSH keys set up or be ready to enter your password when connecting.

PowerShell 7 or newer is required for SSH-based remoting.

Summary

SSH-based remoting lets you control other computers securely using PowerShell.

Use Enter-PSSession for interactive work and Invoke-Command for running scripts remotely.

It works over SSH, so it is simple and safe to use across networks.

Practice

1. What is the main purpose of using SSH-based remoting in PowerShell 7+?

easy

A. To create graphical user interfaces in PowerShell scripts

B. To securely run commands on remote computers using PowerShell

C. To compile PowerShell scripts into executable files

D. To manage local files faster on your own computer

Solution

1. Step 1: Understand SSH-based remoting concept

   SSH-based remoting allows secure communication to run commands on other computers remotely.

2. Step 2: Identify the main use case in PowerShell 7+

   PowerShell 7+ uses SSH remoting to securely run commands or scripts on remote machines.

3. Final Answer:

   To securely run commands on remote computers using PowerShell -> Option B

4. Quick Check:

   SSH remoting = Secure remote command execution [OK]

Hint: SSH remoting = secure remote command running [OK]

Common Mistakes:

• Confusing remoting with local script execution
• Thinking SSH remoting creates GUIs
• Assuming it compiles scripts

2. Which of the following is the correct syntax to start an interactive SSH-based PowerShell session to a remote computer named Server01?

easy

A. Enter-PSSession -HostName Server01

B. Invoke-Command -Session Server01 -SSH

C. Enter-PSSession -ComputerName Server01 -UseSSH

D. New-PSSession -ComputerName Server01

Solution

1. Step 1: Recall Enter-PSSession syntax for SSH remoting

   PowerShell 7+ uses Enter-PSSession -HostName <name> to start SSH sessions.

2. Step 2: Compare options

   Enter-PSSession -HostName Server01 uses -HostName Server01, which is correct for SSH remoting. Enter-PSSession -ComputerName Server01 -UseSSH uses -ComputerName with -UseSSH which is invalid syntax. Invoke-Command -Session Server01 -SSH mixes parameters incorrectly. New-PSSession -ComputerName Server01 creates a session but does not specify SSH or hostname properly.

3. Final Answer:

   Enter-PSSession -HostName Server01 -> Option A

4. Quick Check:

   SSH session uses -HostName parameter [OK]

Hint: Use Enter-PSSession with -HostName for SSH [OK]

Common Mistakes:

• Using -ComputerName instead of -HostName for SSH
• Mixing Invoke-Command with session parameters
• Omitting SSH-specific parameters

3. What will be the output of this PowerShell command run locally if the remote computer Server01 is reachable and has PowerShell 7+ installed?

Invoke-Command -HostName Server01 -ScriptBlock { Get-Date }

medium

A. The current date and time from Server01

B. An error saying 'HostName parameter not recognized'

C. The current date and time from the local computer

D. No output, the command runs silently

Solution

1. Step 1: Understand Invoke-Command with -HostName

   This runs the script block on the remote computer specified by -HostName.

2. Step 2: Analyze the script block

   The script block calls Get-Date, which returns the current date/time on the remote machine.

3. Final Answer:

   The current date and time from Server01 -> Option A

4. Quick Check:

   Invoke-Command with -HostName runs remotely [OK]

Hint: Invoke-Command -HostName runs script remotely [OK]

Common Mistakes:

• Expecting local date/time output
• Confusing parameter names
• Assuming no output is shown

4. You run this command but get an error:

Enter-PSSession -HostName Server01

The error says: "The term 'Enter-PSSession' is not recognized." What is the most likely cause?

medium

A. SSH service is not running on Server01

B. The remote computer Server01 is offline

C. You forgot to specify the username

D. PowerShell version is older than 7 on the local machine

Solution

1. Step 1: Understand the error message

   The error says 'Enter-PSSession' is not recognized, meaning the command is missing locally.

2. Step 2: Identify cause related to PowerShell version

   Enter-PSSession with -HostName for SSH remoting is available only in PowerShell 7+. Older versions do not support it.

3. Final Answer:

   PowerShell version is older than 7 on the local machine -> Option D

4. Quick Check:

   Command not recognized = old PowerShell version [OK]

Hint: Check PowerShell version if command not recognized [OK]

Common Mistakes:

• Assuming remote offline causes local command error
• Blaming SSH service without checking local version
• Thinking username is mandatory for command recognition

5. You want to run a script on multiple remote computers Server01 and Server02 using SSH remoting in PowerShell 7+. Which command correctly runs Get-Process on both and collects results?

hard

A. Invoke-Command -Session (New-PSSession -ComputerName Server01), (New-PSSession -ComputerName Server02) -ScriptBlock { Get-Process }

B. Invoke-Command -ComputerName Server01,Server02 -UseSSH -ScriptBlock { Get-Process }

C. Invoke-Command -HostName Server01,Server02 -ScriptBlock { Get-Process }

D. Enter-PSSession -HostName Server01; Enter-PSSession -HostName Server02; Get-Process

Solution

1. Step 1: Understand running commands on multiple SSH hosts

   Invoke-Command -HostName accepts an array of multiple host names directly in PowerShell 7+.

2. Step 2: Analyze options

   Invoke-Command -HostName Server01,Server02 -ScriptBlock { Get-Process } runs Get-Process on both remote servers and collects the results.

3. Step 3: Why other options are incorrect

   A uses New-PSSession -ComputerName, which targets WinRM not SSH. B uses -ComputerName with invalid -UseSSH. C enters sessions sequentially but Get-Process runs locally after.

4. Final Answer:

   Invoke-Command -HostName Server01,Server02 -ScriptBlock { Get-Process } -> Option C

5. Quick Check:

   Multiple SSH hosts: -HostName Server01,Server02 [OK]

Hint: Invoke-Command -HostName Server01,Server02 for multiple SSH hosts [OK]

Common Mistakes:

• Using -ComputerName (WinRM) instead of -HostName for SSH
• Using invalid -UseSSH parameter
• Running commands locally after sequential Enter-PSSession