Connect Windows
Install the OpenSSH Server feature on Windows, start sshd, and add the machine to SwiftServer.
Windows 10, 11, and Windows Server include Microsoft's OpenSSH Server as an optional feature. Once it runs, SwiftServer connects to Windows like any other machine — including monitoring.
Install OpenSSH Server
With the Settings app: open Settings → System → Optional features → Add an optional feature, search for OpenSSH Server, and install it.
Or with PowerShell (run as Administrator):
Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0Start the service
In the same elevated PowerShell:
Start-Service sshd
Set-Service -Name sshd -StartupType 'Automatic'Installing the feature creates and enables a firewall rule
(OpenSSH-Server-In-TCP) for inbound port 22 automatically — verify it if
you use third-party firewall software.
Microsoft's reference: Get started with OpenSSH Server for Windows.
Add the machine in SwiftServer
Add a machine with the PC's address and a Windows account:
- Username — the local account name, or for Microsoft accounts the email
form usually works (
[email protected]). - Password — the account's password. Accounts without a password cannot log in over SSH.
The default SSH shell on Windows is cmd.exe; SwiftServer's monitoring and
terminal work with cmd, Windows PowerShell, or pwsh as the default shell.
Key login for administrators
Windows reads keys for members of the Administrators group from
C:\ProgramData\ssh\administrators_authorized_keys — not the usual
~/.ssh/authorized_keys. Create that file with your public key and
restrict its permissions:
icacls.exe "C:\ProgramData\ssh\administrators_authorized_keys" /inheritance:r /grant "Administrators:F" /grant "SYSTEM:F"Non-administrator accounts use C:\Users\<name>\.ssh\authorized_keys as
usual.
If the connection fails
- Connection refused —
sshdis not running (Start-Service sshd) or the firewall rule is disabled. - Password rejected — try
MicrosoftAccount\[email protected]as the username form, or use a local account. - Key rejected for an admin account — the
administrators_authorized_keyslocation and permissions above are almost always the reason.
More in Troubleshooting → Connections.