How to configure Bitvise SSH Server as a SovLabs Microsoft Endpoint.
- Have configured the permissions in the SSH Server of your choice
- Defined the account to be used to access SSH
- Have the appropriate ports opened on the server / firewall (default port is TCP 22)
- Recommend having a Domain account configured for use.
User Account prerequisites on your Windows Server
User account permissions and rights are covered in the VMware Tools account setup guide
Bitvise SSH Server can be configured to automatically configure the Windows Firewall, this is recommended as it ensures that the Firewall is configured correctly for the SSH port defined (default 22).
Access in Bitvise SSH Server
When you install and configure your SSH on windows, you will need to define an account for access.
In Bitvise Server options. Go down to Access Control and Windows Accounts
- Click on Add
- In here you can define if it is a local account, domain account or microsoft account. We recommend using a Domain Account (1). Enter the domain of the account (2) and the account name (3). You can do a look up to find the account.
- Place a check in Specify Group and select the group required. If all defaults are in place, select everyone
- Under login allowed, leave the defaults of Use group Default if using Everyone, or if your group has a defined allowed login. Else, select Yes
- Click OK.. You have now defined a user account that has access to your SSH application.
SovLabs Microsoft End Point Configuration
- Ensure you select winsshd from the connection type for your endpoint
- Choose whether you are using a Jump server or not (1) (This example we are using a Jump Server) , Define the Jump Server (2) and the remote server (3)
- If using the default port of 22, you can leave the Uses non-standard port? unchecked, else you can check this and define the port you wish to use
- Define the account you have configured to have access to your server and your SSH Application. You can choose to use an SSH key here which will be available in your SSH Application.
- Define your location for your temporary working files. We recommend not using the default c:\windows\temp but something more along the lines of c:\sovlabs so that you can easily check the script when required for troubleshooting.
- Submit your request, you have now created a Microsoft endpoint using winsshd.
When you do access the server using SSH you should see logs showing log on, ports etc much like the below
- Now you can setup your Microsoft AD/DNS/IPAM modules to use this connection. See the additional information section on setting up accounts permissions and the modules.
MS DNS Account Setup : https://support.sovlabs.com/a/solutions/articles/6000223780-microsoft-dns-account-setup
MS Active Directory Account Setup : https://support.sovlabs.com/a/solutions/articles/6000224740-active-directory-account-setup
MS AD Endpoint configuration (Jump Server / Win RM) : https://support.sovlabs.com/a/solutions/articles/6000223576-microsoft-ad-endpoint-configuration-jump-host-winrm-
RSAT Setup : https://support.sovlabs.com/a/solutions/articles/6000186846-setting-up-rsat-tools-for-remote-management-of-microsoft-ipam-dns-and-ad-using-vmware-tools
SovLabs MS DNS Accounts Setup : https://support.sovlabs.com/a/solutions/articles/6000223780-microsoft-dns-account-setup
SovLabs Active Directory Account Setup : https://support.sovlabs.com/a/solutions/articles/6000224740-active-directory-account-setup
SovLabs MS IPAM Account Setup : https://support.sovlabs.com/a/solutions/articles/6000224741-microsoft-ipam-account-setup
SovLabs Microsoft EndPoint Configuration (Jump Host / WinRM) : https://support.sovlabs.com/a/solutions/articles/6000223576-microsoft-ad-endpoint-configuration-jump-host-winrm-