設置Windows遠端管理（WS-Management，WinRM）
winrm service 默認都是未啓用的狀態，先查看狀態；如無返回信息，則是沒有啓動；
winrm enumerate winrm/config/listener
#
#
#
#
#
#
針對winrm service 進行基礎配置：
winrm quickconfig
#
#
#
#
#
#
#
#
#
#
#
#
需要把需要ansible管理的window機器調成專有網絡
#
#
#
#
#
查看winrm service listener:
winrm e winrm/config/listener
#
#
#
#
#
#
#
#
執行後查看window上5985端口是否開啓
#
#
爲winrm service 配置auth:
winrm set winrm/config/service/auth @{Basic="true"}
#
#
#
#
#
#
爲winrm service 配置加密方式爲允許非加密：
winrm set winrm/config/service @{AllowUnencrypted="true"}
#
#
#
#
#
福利
#
#
好了，遠程Windows主機配置到此結束，我們驗證配置的是否有問題。
配置ansible server段host配置
#
#
#
#
192.168.0.57 ansible_ssh_user=dell ansible_ssh_pass="xxxxx" ansible_ssh_port=5985 ansible_connection="winrm"
#
#
#
#
Windows下可用模塊測試
win_ping —Windows系統下的ping模塊，常用來測試主機是否存活
ansible host -m win_ping
#
#
#
#
#
#
TASK [setup] ***
fatal: [192.168.0.57]: UNREACHABLE! => {"changed": false, "msg": "plaintext: HTTPConnectionPool(host='192.168.0.57', port=5985): Max retries exceeded with url: /wsman (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x341fa90>: Failed to establish a new connection: [Errno 111] Connection refused',))", "unreachable": true}
#
當出現這種情況說明你的window服務器winrm沒有開啓
#
#
#
#
fatal: [192.168.0.57]: UNREACHABLE! => {
"changed": false,
"msg": "plaintext: the specified credentials were rejected by the server",
"unreachable": true
}
#
#
當出現這種情況是你網絡模式不是專有網絡或者window用戶權限的問題
#
#
樓鎮圖