Now that I have OpenSSH installed, the next step(s) is(are) to Configure OpenSSH SFTP on Windows 2019. <\/p>\n\n\n\n
In my case, I had errors during the install<\/a>, but I now have it installed and I am following the default configuration commands from Microsoft’s documentation<\/a>.<\/p>\n\n\n\n First up I confirmed the OpenSSH Client and Server are installed:<\/p>\n\n\n\n and then I start \/ install the server as a service:<\/p>\n\n\n\n Ok, so that is the first couple of steps, done via copy\/paste from the MS instructions. Although I do want to come back to the use of Port 22 as the default. I’ll also need to adjust the ports on the hardware firewall to allow for external SFTP access, but that can come later. <\/p>\n\n\n\n A quick test using PowerShell on my local Windows 10 machine shows that a connection to the server will complete as described, so far success!<\/p>\n\n\n\nPS C:\\windows\\system32> Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*'\n\nName : OpenSSH.Client~~~~0.0.1.0\nState : Installed\n\nName : OpenSSH.Server~~~~0.0.1.0\nState : Installed<\/pre>\n\n\n\n
PS C:\\windows\\system32> Start-Service sshd\nPS C:\\windows\\system32> Set-Service -Name sshd -StartupType 'Automatic'\nPS C:\\windows\\system32> Set-Service -Name sshd -StartupType 'Automatic'\nPS C:\\windows\\system32> if (!(Get-NetFirewallRule -Name \"OpenSSH-Server-In-TCP\" -ErrorAction SilentlyContinue | Select-Object Name, Enabled)) {\n>> Write-Output \"Firewall Rule 'OpenSSH-Server-In-TCP' does not exist, creating it...\"\n>> New-NetFirewallRule -Name 'OpenSSH-Server-In-TCP' -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22\n>> } else {\n>> Write-Output \"Firewall rule 'OpenSSH-Server-In-TCP' has been created and exists.\"\n>> }\nFirewall rule 'OpenSSH-Server-In-TCP' has been created and exists.\nPS C:\\windows\\system32><\/pre>\n\n\n\n