With all the issues of the Windows 10 it certainly goes in a very valid direction – and one of the interesting features introduced by the 1703 Fall Creators Update was the SSH client that is built into the Powershell.
Optional at that time, currently, for 1803 update it was even installed by default, so no more manual installation/activation through the Apps and Features panel.
I am a fan of the concept of keeping the system as low profile as possible. So even though I use the the MTPutty from time to time when I need a work with a fleet of robots, I still like that I could connect to a bot using just a stock Win laptop.
However, the Rpi part of the SSH setup proved to be not very obvious to some of my colleagues – which is the reason I am posting this note for future reference.
Here’s the list of what we have:
- RPi preloaded with Raspbian Lite
- Optional additional hardware to get started (Keyboard, Mouse, Monitor)
Raspbian imaged and loaded, logged as default pi:raspberry credentials and went straight for the normal routine:
sudo apt-get clean sudo apt-get update sudo apt-get upgrade -y sudo apt-get dist-upgrade -y sudo reboot
Afterwards you need to do the following to ensure you’re able to get rid of the keyboard, mouse and monitor connections as working wia ssh with Raspbian Lite is just more convenient:
sudo raspi-config
And enable the Interfacing options > SSH > Enable. Then you need the Raspberry IP to connect to:
hostname -IThen enter the Windows Powershell (since 1803 update in Windows it comes pre-pached with stock SSH client so no third-party tools unless you’re a fan) and connect to the Pi. The syntax is fairly straightforward –
ssh 10.225.14.190 -l pi
Enter your password to remotely connect and once the link is established, you can remove the stuff we do not longer need from the table.
Voila, you’re connected and can do whatever you want, i.e. proceed to the installation of the print server or whatever else.