TL;DR

Server 2003 has no OpenSSH. Bitvise SSH Server 7.x provides shell and SFTP in the lab.

Windows Server 2003 / 2003 R2 does not ship an SSH server. Microsoft never shipped OpenSSH for Windows for that generation either (that arrived much later on Windows 10 / Server 2019+). PowerShell Remoting / WinRM is not the answer on 2003 either: the usable remote stack is RDP, SMB, and Telnet if you enabled it.

If you need ssh user@2003-box from a modern jump host (scripts, scp, legacy Ansible, pull logs without RDP), install a third-party SSH server. In the lab I use Bitvise SSH Server; 7.x is the line validated on Server 2003.

Bitvise still lists XP SP3 and Server 2003 in its compatibility matrix. On a host unpatched since 2015, stick to an installer you have already validated (7.x if that is your golden image) or try current only on a clone — not blind on production.

Why not the alternatives

OptionOn Server 2003
OpenSSH (Win32-OpenSSH / Windows feature)No
Cygwin sshdPossible, brittle and heavy
FreeSSHd / abandoned forksAvoid (unmaintained, attack surface)
RDP onlyFine for GUI; useless for SSH automation
Bitvise SSH ServerYes — shell + SFTP on old Win32

Install (short)

  1. On a machine with a modern browser, download the installer from bitvise.com/ssh-server-download (or the 7.x package you keep for the lab).
  2. Check the digital signature on the .exe (Properties → Digital Signatures → Bitvise).
  3. Copy the installer to the 2003 box (USB, SMB, iLO virtual media). Do not fetch it with IE8 from a random mirror.
  4. Run the installer as Administrator.
  5. Reboot when Bitvise asks (recommended after first install, especially for key auth).
  6. Open the Bitvise SSH Server Control Panel and start the service if it is not set to Automatic.

Official install notes: Installing Bitvise SSH Server.

Minimum config you should not skip

  • Accounts: allow only the Windows user(s) you need (or Bitvise virtual accounts). Do not leave “any local account.”
  • Port: 22 by default. On a management VLAN that is fine; otherwise change it and restrict with the host firewall / switch ACL.
  • Windows 2003 firewall: open TCP/22 (or your chosen port) for the management network only.
  • Key auth: import the jump-host pubkey; turn off password auth once keys work.
  • SFTP root: mount only the path you need (e.g. D:\logs), not C:\.

From the client:

1
2
3

ssh Administrator@192.168.x.x
# or whichever account you enabled
scp logfile.log Administrator@192.168.x.x:D:/logs/

A modern OpenSSH client talks to Bitvise fine; you do not need the Bitvise client unless you want its GUI.

Security (legacy context)

The OS is still without Microsoft patches. Adding SSH improves operations; it increases network surface if the port is reachable beyond the jump host.

  • VLAN / firewall: bastion IP only.
  • Do not put the 2003 box on the Internet “because it has SSH now.”
  • Licensing: Personal Edition is free for non-commercial use; Standard is eval / paid. Respect that in lab vs work.
  • Real goal: migrate the workload. SSH is the bridge to pull data and retire the box.

To open a modern HTTPS portal from the same host (IE8 will not cut it): modern browser on XP/2003 with Supermium.

Vendor docs and downloads: Bitvise SSH Server.