Skip to content
This repository has been archived by the owner on Jan 1, 2019. It is now read-only.

WinRM support #26

Closed
adpande opened this issue Jan 14, 2016 · 3 comments
Closed

WinRM support #26

adpande opened this issue Jan 14, 2016 · 3 comments

Comments

@adpande
Copy link

adpande commented Jan 14, 2016

Hi
It would be wonderful to see winrm support to execute command on Windows servers.

Regards,
Abhishek

@jeffpeiyt
Copy link
Contributor

Hi Abhishek,

Thanks very much for your interests and suggestion on Parallec.

not familiar with winrm. From https://github.com/bmoussaud/WinRM , it said The Windows Remote Management (WinRM) is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows hardware and operating systems, from different vendors, to interoperate.

Thus, it looks like a wrapper protocol based on SOAP, which is XML just based on HTTP(S). If you can intercept the actual message in XML. Wonder could you please trying to send the raw XML content (which is essentially SOAP) in HTTP?

@jeffpeiyt
Copy link
Contributor

it seems possible to integrate Parallec with the overthere WinRmClient : http://xebialabs.github.io/overthere/javadoc/com/xebialabs/overthere/cifs/winrm/WinRmClient.html

However this may not be the focus for Parallec now... however your contribution on this would be much appreciated! Feel free to fork it and submit a merge request after trying it out

From http://www.masterzen.fr/2014/01/11/bootstrapping-windows-servers-with-puppet/:

One component of WinRM is WinRS: Windows Remote Shell. This is the part that allows to run remote commands. Recent Windows version (at least since Server 2003) are shipped with WinRM installed (but not started by default).

this may be a good reference: https://github.com/rundeck-plugins/rundeck-winrm-plugin

https://github.com/rundeck-plugins/rundeck-winrm-plugin/blob/master/src/main/java/com/dtolabs/rundeck/plugin/overthere/OTWinRMNodeExecutor.java

WinRM is an HTTP/SOAP based protocol. By default, the payload is encrypted if the protocol is used in a Domain Controller environment (in this case, it uses Kerberos), which will not be our case on EC2.

@jeffpeiyt
Copy link
Contributor

Close the ticket as there is no further discussion.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants