The issue is related to the user in the windows.yml file. The user is on the Domain, it's not yet implemented by Ansible so we have to use a windows user with a domain set on the machine.
If you need domain account. See : http://docs.ansible.com/intro_windows.html#installing-on-the-control-machine Le mardi 24 février 2015 09:08:17 UTC+1, yosser bf a écrit : > > Hi, > > I'm facing an issue trying to launch a simple command "win_ping" to a > windows node. > I follow the documentation from the Ansible website. > > *Windows machine:* > - Windows Server 2012 Standard > - PowerShell 3.0 > > > *The errror I got:* > > # ansible windows -m win_ping -vvvv > <fgr-wgcitmp201> ESTABLISH WINRM CONNECTION FOR USER: devci on PORT 5986 > TO fgr-wgcitmp201 > <fgr-wgcitmp201> WINRM CONNECT: transport=plaintext endpoint= > https://fgr-wgcitmp201:5986/wsman > <fgr-wgcitmp201> WINRM CONNECTION ERROR: 500 WinRMTransport. [Errno 8] > _ssl.c:492: EOF occurred in violation of protocol > <fgr-wgcitmp201> WINRM CONNECT: transport=plaintext endpoint= > http://fgr-wgcitmp201:5986/wsman > <fgr-wgcitmp201> WINRM CONNECTION ERROR: 500 WinRMTransport. Bad HTTP > response returned from server. Code 503, Service Unavailable > fgr-wgcitmp201 | FAILED => 500 WinRMTransport. Bad HTTP response returned > from server. Code 503, Service Unavailable > > Any idea ? > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9a63e2ef-021c-40c9-a603-a3e263a1753f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
