How do I enable OpenSSH on Windows Server?
Use of SLC Link depends on SSH being configured on the computer that is running Altair SLC, so that a connection can be established from Altair Analytics Workbench.
OpenSSH may be already installed and available but it may need to be installed and/or enabled and/or configured on your server host computer.
SSH communication is usually via port 22 which therefore needs to be open in the firewall settings on the server machine.
In Windows Server 2016 and higher versions, the OpenSSH is part of Windows but it needs to be enabled.
Note that OpenSSH appears as a Service on the Windows Services utility, and there is an additional service called OpenSSH authentication agent which also needs to be active.
SSH client/server connection can be tested and verified without using Altair Workbench and without Altair SLC using the Windows command line or using the Putty utility on the client side.
Here is a useful web page on configuring OpenSSH on Windows Server:
https://computingforgeeks.com/install-and-configure-openssh-server-on-windows-server/
n.b. In Windows Server 2012 SSH connectivity was supplied by a third party "BitVise" but this is not a requirement for the more recent versions of Windows Server.
n.b. For enterprise customers using Altair SLC Hub the use of OpenSSH is not a requirement, since the Altair Analytics Workbench can communicate with Altair SLC Hub via HTTP/S protocol.
OpenSSH on Windows Server 2016 - Step by Step Guide
Locate and download OpenSSH-Win32.zip. (You can probably use OpenSSH-Win64.zip just as well.) Unzip the file and put it into C:\OpenSSH.
Use PowerShell to run these commands:
cd C:\OpenSSH
.\install-sshd.ps1
.\FixHostFilePermissions.ps1 (answer Y to the questions)
From Windows menu type “Services”, see the OpenSSH and OpenSSH authentication services … set them both to start automatically. Start them both.
From Windows firewall settings > Inbound Rules > New Rule create a new rule called SSH PORT 22 … Choose Port > 22 and take the defaults.