Windows powershell ssh copy id

At the moment, Windows 10’s implementation of the OpenSSH client does not have the ssh-copy-id command available. However, a PowerShell one-line command can mimic the ssh-copy-id command and allow you to copy an SSH public key generated by the ssh-keygen command to a remote Linux device for passwordless login.

Generate an SSH Key

Note: If you have already generated an SSH keypair that you would like to use, skip this section and proceed to the Copy SSH Key to Remote Linux Device section.

First, open a new PowerShell window (not a Command Prompt window!) and generate a new SSH keypair with the ssh-keygen command. By default, the public and private keys will be placed in the %USERPROFILE%/.ssh/ directory. The public key file we are interested in is named id_rsa.pub.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

PS C:\Users\Christopher> ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (C:\Users\Christopher/.ssh/id_rsa):
Created directory 'C:\Users\Christopher/.ssh'.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in C:\Users\Christopher/.ssh/id_rsa.
Your public key has been saved in C:\Users\Christopher/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:/mjkrJOQbRzCAwlSPYVBNcuxntm/Ms5/MMC15dCRrMc christopher@Christopher-Win10-VM-01
The key's randomart image is:
+---[RSA 2048]----+
|oo.+o==    o.o   |
|. o +. =  o =    |
|   o .+. . B     |
|    +..+o o E    |
|     *+.S. .     |
|    o +...o      |
|     o =. .o     |
|      o.*o ..    |
|      .=+++.     |
+----[SHA256]-----+
PS C:\Users\Christopher>

Copy SSH Key to Remote Linux Device

Next, we use the below PowerShell one-line command to copy the contents of the id_rsa.pub public key to a remote Linux device. Replace the {IP-ADDRESS-OR-FQDN} with the IP address or FQDN (Fully Qualified Domain Name) of the remote Linux device you would like to copy the public key to.

1

type $env:USERPROFILE\.ssh\id_rsa.pub | ssh {IP-ADDRESS-OR-FQDN} "cat >> .ssh/authorized_keys"

An example of this command is shown below. In this example, I am copying the contents of the id_rsa.pub public key to a remote Linux device at IP address 192.168.30.31.

1
2
3
4
5
6
7

PS C:\Users\Christopher> type $env:USERPROFILE\.ssh\id_rsa.pub | ssh 192.168.30.31 "cat >> .ssh/authorized_keys"
The authenticity of host '192.168.30.31 (192.168.30.31)' can't be established.
ECDSA key fingerprint is SHA256:mTD0/WNCVZ/p/PFSkNDmLJtzIGb5eD7qj6erOQkomjM.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.30.31' (ECDSA) to the list of known hosts.
ch[email protected]'s password:
PS C:\Users\Christopher>

Test Passwordless SSH Connectivity to Remote Linux Device

Finally, verify that you can SSH to the remote Linux device with the ssh command. An example to a remote Linux device at IP address 192.168.30.31 is shown below. Note how a password did not need to be entered in order for us to establish SSH connectivity to the remote Linux device.

1
2
3
4

PS C:\Users\Christopher> ssh 192.168.30.31
Last login: Sat May 23 12:44:51 2020 from 192.168.10.139
[christopher@linux ~]$ who
christopher pts/0        2020-05-24 19:35 (192.168.10.113)

References

The instructions for this blog post were heavily inspired by Scott Hanselman’s blog post on the subject.

This post is licensed under

CC BY 4.0

by the author.

This following steps would do:

STEP-1: Generate RSA Key Pair

C:\Users\user>ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/c/Users/user//.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /c/Users/user//.ssh/id_rsa.
Your public key has been saved in /c/Users/user//.ssh/id_rsa.pub.
The key fingerprint is:
20:16:9b:0d:00:92:c4:34:99:51:20:b7:ef:50:c4:0f user@localhost

STE2-2: ssh-copy-id equivalent in windows

C:\Users\user>ssh user@remote "umask 077; test -d .ssh || mkdir .ssh ; cat >> .s
sh/authorized_keys || exit 1" < "umask 077; test -d .ssh || mkdir .ssh ; cat >> .ssh/authorized_keys
 || exit 1" < C:\Users\user\.ssh\id_rsa.pub
The authenticity of host 'remote (xx.xx.xxx.xx)' can't be established.
RSA key fingerprint is 99:99:73:74:fe:14:bc:91:c8:3b:ac:f4:95:99:4d:06.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'remote,xx.xx.xxx.xx' (RSA) to the list of known hosts.
*************************************************************************
This computer system is the property of Sample Corporation and is to
be used for business purposes.  All information, messages, software and
hardware created, stored, accessed, received, or used by you through
this system is considered to be the sole property of Sample Corporation
and can and may be monitored, reviewed, and retained at any time.  You
should have no expectation that any such information, messages or
material will be private.  By accessing and using this computer, you
acknowledge and consent to such monitoring and information retrieval.
By accessing and using this computer, you also agree to comply with
all of Sample Company's policies and standards.
*************************************************************************
user@remote's password:[Enter Password for first time]

STEP-3: Passwordless authentication works!

C:\Users\user>ssh user@remote
*************************************************************************
This computer system is the property of Sample Corporation and is to
be used for business purposes.  All information, messages, software and
hardware created, stored, accessed, received, or used by you through
this system is considered to be the sole property of Sample Corporation
and can and may be monitored, reviewed, and retained at any time.  You
should have no expectation that any such information, messages or
material will be private.  By accessing and using this computer, you
acknowledge and consent to such monitoring and information retrieval.
By accessing and using this computer, you also agree to comply with
all of Sample Company's policies and standards.
*************************************************************************
Last login: Wed Oct 14 14:37:13 2015 from localhost

21 Feb 2023 |
Create ssh-copy-id script for Windows |

Those of us who use linux with keyless logins and ssh , usually find the utility ssh-copy-id as a convenient way to copy the ssh ke into the authorized keys files of the destination server. This works great on Linux systems, but windows (and also Mac) don’t have a native version fo ssh-copy-id, of course you could find scripts online that do this.. but many are overkill basically re-creating the entire ssh client in code just for the purpose of copying over a single key. Also since this is a securtity realted operation , you want to be confident those scripts are only doing what they say they’re doing.

With that said I hope to address these issues in this post and show you a quick, short and most importantly easy to modify powershell script that you can use in any modern version of Windows.

Security and Concerns

Finally there’s security concerns about using these scripts, unless you go over everly line of of code you’re never really sure what they’re doing with your key. Because of this the code velow is short, in native powershell and very easy to use, you litterally can read the code in this post and res-assured it’s only doing what it’s supposed to.

SSH-COPY-ID in Powershell

Windows Powershell is the defacto Widnows command line programming language replacing the traditional DOS batch files, and has been in available since around Windows 7 (circa 2007) . You can find a useful Powershell cheat sheet here:

param (
    [Parameter(Mandatory=$true)]
    [string]$connectionString,

    [Parameter(Mandatory=$true)]
    [string]$publicKeyFile
)

$connectionParts = $connectionString.Split('@')
if ($connectionParts.Length -ne 2) {
    throw "Invalid connection string format. Must be in the format 'user@hostname:port'"
}
$username = $connectionParts[0]
$hostParts = $connectionParts[1].Split(':')
$hostname = $hostParts[0]
if ($hostParts.Length -gt 1) {
    $port = $hostParts[1]
} else {
    $port = 22
}

$sshDir = "$env:USERPROFILE\.ssh"
if (!(Test-Path -Path $sshDir)) {
    New-Item -ItemType Directory -Path $sshDir | Out-Null
}

$sshPubKey = Get-Content $publicKeyFile
$sshPubKeyFileName = Split-Path $publicKeyFile -Leaf
$sshAuthorizedKeysFile = "$sshDir\authorized_keys"

$sshConnection = New-SSHSession -ComputerName $hostname -Credential $username -Port $port
$sshAuthorizedKeys = Invoke-SSHCommand -SessionId $sshConnection.SessionId -Command "cat $sshAuthorizedKeysFile" | Select-Object -ExpandProperty Output
if ($sshAuthorizedKeys -notcontains $sshPubKey) {
    Invoke-SSHCommand -SessionId $sshConnection.SessionId -Command "echo `"$sshPubKey`" >> $sshAuthorizedKeysFile"
}

Write-Output "Public key added to $hostname authorized_keys file"
?

This script requires the New-SSHSession and Invoke-SSHCommand cmdlets, which are available in the PowershellSSH module. You can install this module by running Install-Module -Name PowershellSSH.

How it works

The script takes three parameters: the username on the remote host, the hostname or IP address of the remote host, and the path to the public key file. The script then creates the ~/.ssh directory on the remote host if it doesn’t exist, reads the public key from the specified file, and adds it to the authorized_keys file on the remote host if it’s not already there. Finally, the script outputs a message indicating that the public key was added to the authorized_keys file.

To use this script, save it to a file with a .ps1 extension, and then run it with the required parameters. For example:

.\ssh-copy-id.ps1 user@remotehost:port -publicKeyFile C:\Users\myuser\.ssh\id_rsa.pub

# Power Up Your Workflow: 5 Advanced Ways to Use SSH With PowerShell

In the realm of software engineering, PowerShell stands tall as a versatile and powerful tool for administering systems, with many use cases involving scripting and automation. Using Secure Shell (SSH) with PowerShell opens up a whole new level of control and management of various systems, making your work more efficient and streamlined. But are you tapping into the full potential of this powerful combination?

In this article, we will dive deep into **how to use SSH with PowerShell** by showcasing five advanced techniques that will empower your workflow and elevate your expertise. Grab your terminal and let’s get started!

## 1. Establishing an SSH Session Using PowerShell

First things first, you need to establish an SSH session between your local machine and a remote system. To do this, we will use the **SSH** client built into PowerShell.

### Prerequisites:

– Ensure that Windows 10 build 1809 or later is installed on your machine.
– The OpenSSH Client feature should be enabled on your Windows 10 device. To do this, navigate to **Settings > Apps > Optional Features**, search for “OpenSSH Client,” and click “Install” if it’s not installed already.

### Connecting to a Remote System:

Once you have met the prerequisites, open PowerShell and run the following command to establish an SSH connection:

“`
ssh @
“`

Replace “ with the remote system’s username and “ with the remote system’s hostname or IP address.

## 2. Remotely Executing Commands with PowerShell and SSH

One advantage of using SSH with PowerShell is the ability to execute commands on remote systems without the need to log in manually. This section will demonstrate **how to use SSH with PowerShell** to execute commands remotely.

### Single Command Execution:

To execute a single command remotely, use the following command:

“`
ssh @ ”
“`

For example, to obtain a list of files in the “/tmp” directory on the remote system, you would run:

“`
ssh [email protected] ‘ls /tmp’
“`

### Multiple Command Execution:

To execute multiple commands remotely, use the following command:

“`
ssh @ ‘ ; ; ‘
“`

For example, to create a backup of a file and compress it, you would run:

“`
ssh [email protected] ‘cp /var/log/syslog /tmp/syslog.bak ; gzip /tmp/syslog.bak’
“`

Keep in mind that, in both cases, single and multiple command execution, the commands are enclosed within single quotes.

## 3. Transfer Files Securely Uploading and Downloading

Another advanced technique in using SSH with PowerShell is the ability to transfer files securely between local and remote systems. For this purpose, we will be using **SCP (Secure Copy Protocol)**, which is integrated into PowerShell’s OpenSSH client.

### Uploading Files:

To upload a file to a remote system, run the following command:

“`
scp @:
“`

For example, to upload the file “file.txt” from your Documents folder to the remote system’s /tmp directory, you would run:

“`
scp C:UsersYourUsernameDocumentsfile.txt [email protected]:/tmp
“`

### Downloading Files:

To download a file from a remote system, run the following command:

“`
scp @:
“`

For example, to download the file “file.txt” from the remote system’s /tmp directory to your Downloads folder, you would run:

“`
scp us[email protected]:/tmp/file.txt C:UsersYourUsernameDownloads
“`

## 4. Automating Tasks with PowerShell-SSH Scripts

By incorporating SSH into your PowerShell scripts, you can automate a variety of tasks that involve remote systems. Here’s an example script that checks disk usage on multiple remote systems and sends an email alert when the usage exceeds a specific threshold:

“`powershell
$servers = @( ‘server1.example.com’, ‘server2.example.com’, ‘server3.example.com’ )
$threshold = 90

foreach ($server in $servers) {
$diskUsage = ssh user@$server ‘df –output=pcent / | tail -1 | tr -dc “0-9″‘
if ([int]$diskUsage -gt $threshold) {
Send-MailMessage -From “[email protected]” -To “[email protected]” -Subject “Disk Usage Alert: $server” -Body “The disk usage on $server ($diskUsage%) has exceeded the threshold ($threshold%).” -SmtpServer “smtp.example.com”
}
}
“`

In this example, the script reads a list of server names from an array called `$servers`. It then iterates through each server, checking the disk usage by executing a remote `df` command. If the usage exceeds the specified threshold, an email alert is sent using the `Send-MailMessage` cmdlet.

## 5. Managing SSH Keys for Simplified Login and Enhanced Security

Managing SSH keys is crucial for both simplifying the login process and enhancing security. Here’s how you can generate, copy, and use SSH keys with PowerShell:

### Generating SSH Key Pair:

To generate a new SSH key pair, run the following command:

“`
ssh-keygen.exe
“`

This will create a public and private key pair in the default location, `%USERPROFILE%.sshid_rsa`.

### Copying the Public Key to a Remote System:

To copy the public key to a remote system’s authorized keys file, run the following command:

“`
ssh-copy-id @
“`

Once the public key is added to the remote system, you can authenticate without entering a password.

## Wrapping Up

By incorporating these advanced techniques into your arsenal, you can unlock the full potential of **how to use SSH with PowerShell**. From establishing SSH sessions to executing remote commands, transferring files securely, automating tasks, and managing SSH keys, these methods will empower your workflow and bolster your expertise in system administration and automation. With an open mind and a willingness to experiment, there’s no limit to what you can achieve using SSH with PowerShell.

How to set up PowerShell prompt with Oh My Posh on Windows 11

Learn PowerShell in Less Than 2 Hours

How can one utilize SSH within a PowerShell script?

Utilizing SSH within a PowerShell script can be done using the SSH.NET library or the built-in Windows OpenSSH client. Here’s how to use both methods:

1. Using SSH.NET Library:

First, you need to install the SSH.NET library by running the following command:

“`powershell
Install-Package -Name SSH.NET
“`

Once installed, you can use it in your PowerShell script as follows:

“`powershell
# Import the SSH.NET library
Import-Module -Name Renci.SshNet

# Set your SSH credentials and target host
$UserName = “”
$Password = ConvertTo-SecureString “” -AsPlainText -Force
$Credential = New-Object System.Management.Automation.PSCredential($UserName, $Password)
$Host = “”

# Create an SSH connection
$Connection = New-Object Renci.SshNet.SshClient($Host, $Credential.UserName, $Credential.Password)
$Connection.Connect()

# Execute a command on the remote host
$Command = “ls”
$Result = $Connection.RunCommand($Command)

# Display the command output
Write-Host $Result.Output

# Close the connection
$Connection.Disconnect()
“`

2. Using Windows OpenSSH Client:

The Windows OpenSSH client is available by default in Windows 10 (build 1809) and later. To use it in your PowerShell script, follow these steps:

“`powershell
# Set your SSH credentials and target host
$UserName = “”
$Password = “”
$Host = “”

# Create a PSCredential object
$SecurePassword = ConvertTo-SecureString $Password -AsPlainText -Force
$Credential = New-Object System.Management.Automation.PSCredential($UserName, $SecurePassword)

# Execute a command on the remote host using the ssh command
$Command = “ls”
$Result = Invoke-Command -ScriptBlock {
ssh $args[0]@$args[1] $args[2]
} -ArgumentList $Credential.UserName, $Host, $Command

# Display the command output
Write-Host $Result
“`

Remember to replace <your-username>, <your-password>, and <target-host> with your own information.

How can I initiate SSH within Windows 10 PowerShell?

To initiate **SSH** within **Windows 10 PowerShell**, you need to ensure that the OpenSSH client is installed on your system. Follow these steps:

1. **Enable the OpenSSH client**:
Open PowerShell with administrative privileges by right-clicking on the Start button and selecting “Windows PowerShell (Admin)” or by searching for “PowerShell” in the Start menu, right-clicking, and choosing “Run as administrator”.

Enter the following command to enable the OpenSSH client:

“`
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
“`

2. **Verify the installation**:
To confirm that the OpenSSH client is installed, type the following command in PowerShell:

“`
Get-WindowsCapability -Online | ? Name -like ‘OpenSSH*’
“`

If the installation was successful, you’ll see a list of OpenSSH features with their respective statuses. The OpenSSH client should be listed with a status of “Installed.”

3. **Initiate an SSH connection**:
Now that the OpenSSH client is installed, you can initiate an SSH connection within PowerShell by using the following command:

“`
ssh username@hostname
“`

Replace `username` with your remote user account and `hostname` with the IP address or domain name of the remote server. After entering this command, you’ll be prompted for your password.

By following these steps, you can successfully initiate an **SSH** connection within **Windows 10 PowerShell**.

How can one generate an SSH key with PowerShell?

To generate an SSH key with PowerShell, you can use the ssh-keygen command. The following steps will guide you through the process:

1. Open PowerShell as an administrator.

2. Run the following command to ensure that the OpenSSH module is installed:

“`
Get-WindowsCapability -Online | ? Name -like ‘OpenSSH*’
“`

3. If the module is not installed, you can install it using the following commands:

“`
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
“`

4. Once the OpenSSH module is installed, you can generate an SSH key by running the ssh-keygen command:

“`
ssh-keygen -t rsa -b 4096 -C “[email protected]”
“`

Replace “[email protected]” with your actual email address. The `-t` option specifies the type of key to be generated (in this case, RSA), the `-b` option sets the key length (4096 bits), and the `-C` option adds a comment for easier identification of the key.

5. The command will prompt you to enter a file path to save the private key. Press Enter to use the default location, or provide a custom path if preferred.

6. Next, you will be asked to enter a passphrase to secure the private key. You can either enter a passphrase or leave it empty for no passphrase.

The ssh-keygen command will generate a public and a private key. The public key will have a `.pub` extension and can be shared with others to allow access to resources. The private key should be kept secure and never shared.

How can one use SSH with Windows command in PowerShell?

Using SSH with Windows command in PowerShell is a great way to manage remote systems securely. Starting with Windows 10 and Windows Server 2019, OpenSSH is now included by default, making it easy to connect to remote hosts using the SSH protocol. Here’s how you can use SSH in PowerShell:

1. Install OpenSSH (Optional): If you’re using an older Windows version or it doesn’t have OpenSSH installed, you can install it by running the following command:

“`powershell
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
“`

2. Start the SSH Agent: Before using SSH keys for authentication, you’ll need to start the SSH agent service. Run the following command to set the service startup type to automatic and start it:

“`powershell
Set-Service -Name ssh-agent -StartupType Automatic; Start-Service ssh-agent
“`

3. Create an SSH Key (Optional): If you don’t already have an SSH key pair, you can create one using the following command:

“`powershell
ssh-keygen -t rsa -b 4096
“`

This will generate a new RSA key pair with a 4096-bit key size.

4. Copy the Public SSH Key to the Remote Host: To authenticate without a password, copy your public SSH key to the remote host using the following command:

“`powershell
ssh-copy-id username@remote-host
“`

Replace “username” with your actual username on the remote host and “remote-host” with the hostname or IP address of the remote system.

5. Connect to the Remote Host via SSH: Now you can connect to the remote host using the SSH command like this:

“`powershell
ssh username@remote-host
“`

Again, replace “username” and “remote-host” with the appropriate values.

Now you’re connected to the remote host via SSH using PowerShell. You can execute any command on the remote system, transfer files securely, and perform various tasks related to remote management.

How can I establish an SSH connection with a remote server using PowerShell command-line?

To establish an SSH connection with a remote server using PowerShell command-line, you can use the **`SSH`** command followed by the required parameters such as the username and the remote server’s IP address or hostname. Here’s a step-by-step guide on how to do this:

1. Open PowerShell by pressing **`Windows Key + X`** and selecting **PowerShell (Admin)**.

2. Install the **OpenSSH** package/module, if it’s not already installed. You can install it using the following command:

“`
Add-WindowsCapability -Online -Name OpenSSH.Client~~~~0.0.1.0
“`

3. Once the OpenSSH package is installed, you can use the **`ssh`** command to establish a connection with a remote server. The basic syntax is:

“`
ssh username@remote-server
“`

Replace **`username`** with your remote server’s username, and **`remote-server`** with the remote server’s IP address or hostname.

For example:

“`
ssh [email protected]
“`

4. When prompted, enter the password for the remote user account. Once the authentication is successful, you’ll be connected to the remote server, and you can start running commands on the remote system.

Remember that the remote server must have an SSH server running and listening for incoming connections.

What are the essential commands for managing SSH keys and configuring SSH connections in PowerShell?

In PowerShell, you can manage SSH keys and configure SSH connections using a combination of OpenSSH utilities and native PowerShell commands. Here are the essential commands:

1. ssh-keygen: This command is used to generate, manage, and convert authentication keys for SSH protocol. To create a new SSH key pair, run the following command:

“`
ssh-keygen -t rsa -b 4096 -C “[email protected]”
“`

2. Get-Content: This command is used to read the content of a file. You can use this command to display the public key that you need to add to the remote server’s `authorized_keys` file:

“`
Get-Content C:UsersYourUsername.sshid_rsa.pub
“`

3. ssh-copy-id: This command allows you to copy your public key to a remote server. It can be installed through the Windows Subsystem for Linux (WSL) or by using an alternative implementation like `scp`. Here’s how you can use it:

“`
ssh-copy-id user@remote_server
“`

If you don’t have `ssh-copy-id`, you can use `scp` as an alternative:

“`
scp C:UsersYourUsername.sshid_rsa.pub user@remote_server:~/temp.pub
“`

4. ssh: The command used to initiate an SSH connection to a remote server. After setting up your SSH key pair, you can connect to the remote server using the following command:

“`
ssh user@remote_server
“`

5. New-Item: This command creates a new item, such as a file or directory. You may need to create a `config` file for your SSH client in the `~/.ssh` directory. To create this file, use the following command:

“`
New-Item -Path C:UsersYourUsername.sshconfig -ItemType File
“`

6. Add-Content: This command is used to append content to a file. You can use this command to add specific settings to your SSH `config` file. For example, to configure an alias for a remote server, add the following lines to your `config` file:

“`
Add-Content -Path C:UsersYourUsername.sshconfig -Value “Host remote_alias`nHostName remote_server`nUser user`nIdentityFile ~/.ssh/id_rsa”
“`

With these PowerShell commands and OpenSSH utilities, you can effectively manage SSH keys and configure SSH connections.

Can you provide a step-by-step guide to automate SSH sessions in PowerShell for multiple remote servers?

In this guide, we will demonstrate how to automate SSH sessions in PowerShell for multiple remote servers using the **Pode** module. Pode is a cross-platform module for managing and automating SSH connections.

Step 1: Install Pode module

First, install the Pode module from the PowerShell Gallery by running the following command:

“`powershell
Install-Module -Name Pode
“`

Step 2: Import Pode module

Import the Pode module into your PowerShell session to make the functions available:

“`powershell
Import-Module Pode
“`

Step 3: Define remote servers and credentials

Create an array of remote server IPs or hostnames and their corresponding credentials. Make sure to replace the placeholders with your actual servers and credentials:

“`powershell
$RemoteServers = @(
@{
Host = ‘192.168.1.1’
Username = ‘User1’
Password = ‘Password1’
},
@{
Host = ‘192.168.1.2’
Username = ‘User2’
Password = ‘Password2’
}
)
“`

Step 4: Define the automation script

Create a script block with the commands you want to execute on each remote server:

“`powershell
$ScriptToExecute = {
Param($RemoteServer)

# Establish SSH session
$Session = New-PodeSshSession -HostName $RemoteServer.Host -UserName $RemoteServer.Username -Password $RemoteServer.Password

# Execute commands
$Result = Invoke-PodeSshCommand -Session $Session -Command ‘uname -a’

# Print results
Write-Host “Results from $($RemoteServer.Host):`n$($Result.Output)`n”

# Close SSH session
Close-PodeSshSession -Session $Session
}
“`

Step 5: Automate the SSH sessions

Loop through the remote servers, invoke the script block and execute it:

“`powershell
ForEach ($RemoteServer in $RemoteServers) {
Invoke-Command -ScriptBlock $ScriptToExecute -ArgumentList $RemoteServer
}
“`

Step 6: Save and run the script

Save the entire text into a PowerShell script file (e.g., “AutomateSSH.ps1”) and execute it in your PowerShell session:

“`powershell
.AutomateSSH.ps1
“`

This script will automate SSH sessions for your multiple remote servers and execute the defined commands on each of them. Make sure to modify the script according to your specific needs and requirements.