overthere | Runs something | Automation library

To use the SFTP connection type, make sure SFTP is enabled in the SSH server. This is enabled by default in most SSH servers. To use the SFTP_CYGWIN connection type, install COPSSH on your Windows host. In the COPSSH control panel, add the users as which you want to connect and select Linux shell and Sftp in the shell dropdown box. Check Password authentication and/or Public key authentication depending on the authentication method you want to use.N.B.: Overthere will take care of the translation from Windows style paths, e.g. C:\Program Files\IBM\WebSphere\AppServer, to Cygwin-style paths, e.g. /cygdrive/C/Program Files/IBM/WebSphere/AppServer, so that your code can use Windows style paths. To use the SFTP_WINSSHD connection type, install WinSSHD on your Windows host. In the Easy WinSSHD Settings control panel, add the users as which you want to connect, check the Login allowed checkbox and select Allow full access in the Virtual filesystem layout dropdown box. Alternatively you can check the Allow login to any Windows account to allow access to all Windows accounts.N.B.: Overthere will take care of the translation from Windows style paths, e.g. C:\Program Files\IBM\WebSphere\AppServer, to WinSSHD-style paths, e.g. /C/Program Files/IBM/WebSphere/AppServer, so that your code can use Windows style paths. To use the SFTP_OpenSSHD connection type, install OpenSSHD on your Windows host and make sure the OpenSSH Server service is enabled.N.B.: Overthere will take care of the translation from Windows style paths, e.g. C:\Program Files\IBM\WebSphere\AppServer, to OpenSSHD-style paths, e.g. /C:/Program Files/IBM/WebSphere/AppServer, so that your code can use Windows style paths. To use the SUDO connection type, the /etc/sudoers configuration will have to be set up in such a way that the user configured with the connection option username can execute the commands below as the user configured with the connection option sudoUsername. The arguments passed to these commands depend on the exact usage of the Overthere connection. Check the INFO messages on the com.xebialabs.overthere.ssh.SshConnection category to see what commands get executed. The commands mentioned above must be configured with the NOPASSWD setting in the /etc/sudoers file. Otherwise you will have to use the INTERACTIVE_SUDO connection type. When the INTERACTIVE_SUDO connection type is used, every line of the output will be matched against the regular expression configured with the sudoPasswordPromptRegex connection option. If a match is found, the value of the password connection option is sent.
chmod
cp
ls
mkdir
mv
rm
rmdir
tar
Any other command that you want to execute.
To use the TELNET connection type, you'll need to enable and configure the Telnet Server according to these instructions:. When the Telnet server is enabled any user that is in the Administrators group or that is in the TelnetClients group and that has the Allow logon locally privilege can log in using Telnet. See the Microsoft Technet to learn how to grant a user or group the right to logon locally on Windows Server 2008 R2.
(Optional) If the Telnet Server is not already installed on the remote host, add it using the Add Features Wizard in the Server Manager console.
(Optional) If the remote host is running Windows Server 2003 SP1 or an x64-based version of Windows Server 2003, install the Telnet server according to these instructions from the Microsoft Support site.
Enable the Telnet Server Service on the remote host according to these instructions on the Microsoft Technet site.
After you have started the Telnet Server, open a command prompt as the Administrator user on the remote host and enter the command tlntadmn config mode=stream to enable stream mode.
If the remote host is running Windows Server 2003 SP1 or SP2, or Windows XP SP2, install the WS-Management v.1.1 package.
If the remote host is running Windows Server 2003 R2, go to the Add/Remove System Components feature in the Control Panel and add WinRM under the section Management and Monitoring Tools. Afterwards install the WS-Management v.1.1 package to upgrade the WinRM installation.
If the remote host is running Windows Vista or Windows 7, the Windows Remote Management (WS-Management) service is not started by default. Start the service and change its Startup type to Automatic (Delayed Start) before proceeding with the next steps.
On the remote host, open a Command Prompt (not a PowerShell prompt!) using the Run as Administrator option and paste in the following lines when using the WINRM_INTERNAL connection type: winrm quickconfig y winrm set winrm/config/service/Auth @{Basic="true"} winrm set winrm/config/service @{AllowUnencrypted="true"} winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"} Or the following lines when using the WINRM_NATIVE connection type: winrm quickconfig y winrm set winrm/config/service/Auth @{Basic="true"} winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"} Or keep reading for more detailed instructions. :-)
Run the quick config of WinRM to start the Windows Remote Management service, configure an HTTP listener and create exceptions in the Windows Firewall for the Windows Remote Mangement service: winrm quickconfig N.B.: The Windows Firewall needs to be running to run this command. See Microsoft Knowledge Base article #2004640.
(Optional) By default basic authentication is disabled in WinRM. Enable it if you are going to use local accounts to access the remote host: winrm set winrm/config/service/Auth @{Basic="true"}
(Optional) By default Kerberos authentication is enabled in WinRM. Disable it if you are not going to use domain accounts to access the remote host: winrm set winrm/config/service/Auth @{Kerberos="false"} N.B.: Do not disable Negotiate authentication as the winrm command itself uses that to configure the WinRM subsystem!
(Only required for WINRM_INTERNAL or when the connection option winrsUnencrypted is set to true) Configure WinRM to allow unencrypted SOAP messages: winrm set winrm/config/service @{AllowUnencrypted="true"}
Configure WinRM to provide enough memory to the commands that you are going to run, e.g. 1024 MB: winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"} N.B.: This is not supported by WinRM 3.0, included with the Windows Management Framework 3.0. This update has been temporarily removed from Windows Update because of numerous incompatiblity issues with other Microsoft products. However, if you have already installed WMF 3.0 and cannot downgrade, Microsoft Knowledge Base article #2842230 describes a hotfix that can be installed to re-enable the MaxMemoryPerShellMB setting.
To use the WINRM_INTERNAL or WINRM_NATIVE connection type with HTTPS, i.e. winrmEnableHttps set to true, follow the steps below: (Optional) Create a self signed certificate for the remote host by installing selfssl.exe from the IIS 6 resource kit and running the command below or by following the instructions in this blog by Hans Olav: C:\Program Files\IIS Resources\SelfSSL>selfssl.exe /T /N:cn=HOSTNAME /V:3650 Microsoft (R) SelfSSL Version 1.0 Copyright (C) 2003 Microsoft Corporation. All rights reserved. Do you want to replace the SSL settings for site 1 (Y/N)?Y The self signed certificate was successfully assigned to site 1. Open a PowerShell window and enter the command below to find the thumbprint for the certificate for the remote host: PS C:\Windows\system32> Get-childItem cert:\LocalMachine\Root\ | Select-String -pattern HOSTNAME [Subject] CN=HOSTNAME [Issuer] CN=HOSTNAME [Serial Number] 527E7AF9142D96AD49A10469A264E766 [Not Before] 5/23/2011 10:23:33 AM [Not After] 5/20/2021 10:23:33 AM [Thumbprint] 5C36B638BC31F505EF7F693D9A60C01551DD486F Create an HTTPS WinRM listener for the remote host with the thumbprint you've just found: winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="HOSTNAME"; CertificateThumbprint="THUMBPRINT"}
Do a quickconfig for WinRM with HTTPS: winrm quickconfig -transport:https
View the complete WinRM configuration: winrm get winrm/config
View the listeners that have been configured: winrm enumerate winrm/config/listener
Create an HTTP listener: winrm create winrm/config/listener?Address=*+Transport=HTTP (also done by winrm quickconfig)
Allow all hosts to connect to the WinRM listener: winrm set winrm/config/client @{TrustedHosts="*"}
Allow a fixed set of hosts to connect to the WinRM listener: winrm set winrm/config/client @{TrustedHosts="host1,host2..."}
Linux: /etc/krb5.conf
Solaris: /etc/krb5/krb5.conf
Windows: C:\Windows\krb5.ini
PROTOCOL is either WSMAN (default) or HTTP (if winrmKerberosUseHttpSpn has been set to true).
ADDRESS is the address used to connect to the remote host,
PORT (optional) is the port used to connect to the remote host (usually 5985 or 5986, only necessary if winrmKerberosAddPortToSpn has been set to true), and
WINDOWS-HOST is the short Windows hostname of the remote host.
List all service principal names configured for the domain: setspn -Q */*
List all service principal names configured for a specific host in the domain: setspn -L _WINDOWS-HOST_