Windows 7 Ansible 2.0

Archives Ansible Project
1

I have a Windows 7 Enterprise VM that I cannot get to function with Ansible 2.0

Control Server: Centos 7
Ansible Version: ansible 2.0.1.0 and previously 1.9.4

I have followed the setup guide, run the Prep-Script on Windows, verified that WinRM is functional

When running: ansible windows -m setup -vvvv I get the following:

Loaded callback minimal of type stdout, v2.0
<192.168.2.191> ESTABLISH WINRM CONNECTION FOR USER: Administrator on PORT 5986 TO 192.168.2.191
<192.168.2.191> EXEC Set-StrictMode -Version Latest
(New-Item -Type Directory -Path $env:temp -Name “ansible-tmp-1456880843.77-137909747715611”).FullName | Write-Host -Separator ‘’;
192.168.2.191 | UNREACHABLE! => {
“changed”: false,
“msg”: “Authentication or permission failure. In some cases, you may have been able to authenticate and did not have permissions on the remote directory. Consider changing the remote temp path in ansible.cfg to a path rooted in "/tmp". Failed command was: PowerShell -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -EncodedCommand UwBlAHQALQBTAHQAcgBpAGMAdABNAG8AZABlACAALQBWAGUAcgBzAGkAbwBuACAATABhAHQAZQBzAHQACgAoAE4AZQB3AC0ASQB0AGUAbQAgAC0AVAB5AHAAZQAgAEQAaQByAGUAYwB0AG8AcgB5ACAALQBQAGEAdABoACAAJABlAG4AdgA6AHQAZQBtAHAAIAAtAE4AYQBtAGUAIAAiAGEAbgBzAGkAYgBsAGUALQB0AG0AcAAtADEANAA1ADYAOAA4ADAAOAA0ADMALgA3ADcALQAxADMANwA5ADAAOQA3ADQANwA3ADEANQA2ADEAMQAiACkALgBGAHUAbABsAE4AYQBtAGUAIAB8ACAAVwByAGkAdABlAC0ASABvAHMAdAAgAC0AUwBlAHAAYQByAGEAdABvAHIAIAAnACcAOwA=, exited with result 1”,
“unreachable”: true

However, I have run this on both 2008 R2 and Windows 2012 R2 and it works flawlessly.

Whatever it is it seems to be unique to Win 7

2

I think Windows 7 comes with powershell 2.0 - Ansible needs powershell 3.0 or later. Have you upgraded to powershell 3 or 4, (or Windows Management Framework 3.0 or 4.0)?

I suggest using the windows hostname rather than ip, just to rule that out too.

Hope this helps,

Jon