From 7724c958e149e1b9dc1021936b31956792013e38 Mon Sep 17 00:00:00 2001
From: Ming Qian <bruceharbin@gmail.com>
Date: Tue, 1 Dec 2015 11:24:17 -0800
Subject: [PATCH] Update intro_windows.rst

first pull. thanks.
---
 docsite/rst/intro_windows.rst | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docsite/rst/intro_windows.rst b/docsite/rst/intro_windows.rst
index e5cbb94faf..316d1eca1a 100644
--- a/docsite/rst/intro_windows.rst
+++ b/docsite/rst/intro_windows.rst
@@ -166,6 +166,8 @@ In group_vars/windows.yml, define the following inventory variables::
     ansible_port: 5986
     ansible_connection: winrm
 
+Attention for the older style variables (``ansible_ssh_*``): ansible_ssh_password doesn't exist, should be ansible_ssh_pass.
+
 Although Ansible is mostly an SSH-oriented system, Windows management will not happen over SSH (`yet <http://blogs.msdn.com/b/powershell/archive/2015/06/03/looking-forward-microsoft-support-for-secure-shell-ssh.aspx>`).
 
 If you have installed the ``kerberos`` module and ``ansible_user`` contains ``@`` (e.g. ``username@realm``), Ansible will first attempt Kerberos authentication. *This method uses the principal you are authenticated to Kerberos with on the control machine and not ``ansible_user``*. If that fails, either because you are not signed into Kerberos on the control machine or because the corresponding domain account on the remote host is not available, then Ansible will fall back to "plain" username/password authentication.