From 8ad296a6f24084112d7acc903c9d5abce6647125 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Thu, 31 Jul 2014 13:42:12 -0400 Subject: [PATCH] Simply docs by providing the powershell setup script instead. Thanks Trond!!! --- docsite/rst/intro_windows.rst | 56 ++++------------------------------- 1 file changed, 5 insertions(+), 51 deletions(-) diff --git a/docsite/rst/intro_windows.rst b/docsite/rst/intro_windows.rst index 199700c155c..d3e2aae2e3e 100644 --- a/docsite/rst/intro_windows.rst +++ b/docsite/rst/intro_windows.rst @@ -69,65 +69,19 @@ You'll run this command again later though, to make sure everything is working. Windows System Prep ``````````````````` -In order for Ansible to manage your windows machines, you will have to enable Powershell remoting first, which also enables WinRM. +In order for Ansible to manage your windows machines, you will have to enable Powershell remoting configured. -From the Windows host, launch the Powershell Client. For information on Powershell, visit `Microsoft's Using Powershell article `_. +To automate setup of WinRM, you can run `this powershell script `_ on the remote machine. -In the powershell session, run the following to enable PS Remoting and set the execution policy - -.. code-block:: bash - - $ Enable-PSRemoting -Force - $ Set-ExecutionPolicy RemoteSigned - -If your Windows firewall is enabled, you must also run the following command to allow firewall access to the public firewall profile: - -.. code-block:: bash - - # Windows 2012 / 2012R2 - $ Set-NetFirewallRule -Name "WINRM-HTTP-In-TCP-PUBLIC" -RemoteAddress Any - - # Windows 2008 / 2008R2 - $ NetSH ADVFirewall Set AllProfiles Settings remotemanagement Enable - -By default, Powershell remoting enables an HTTP listener. The following commands enable an HTTPS listener, which secures communication between the Control Machine and windows. - -An SSL certificate for server authentication is required to create the HTTPS listener. The existence of an existing certificate in the computer account can be verified by using the MMC snap-in. - -A best practice for SSL certificates is generating them from an internal or external certificate authority. An existing certificate could be located in the computer account certificate store `using the following article `_. - -Alternatively, a self-signed SSL certificate can be generated in powershell using `the following technet article `_. At a minimum, the subject name should match the hostname, and Server Authentication is required. Once the self signed certificate is obtained, the certificate thumbprint can be identified using `How to: Retrieve the Thumbprint of a Certificate `_. - -.. code-block:: bash - - # Create the https listener - $ winrm create winrm/config/Listener?Address=*+Transport=HTTPS  @{Hostname="host_name";CertificateThumbprint="certificate_thumbprint"} - - # Delete the http listener - $ WinRM delete winrm/config/listener?Address=*+Transport=HTTP - -Again, if your Windows firewall is enabled, the following command to allow firewall access to the HTTPS listener: - -.. code-block:: bash - - # Windows 2008 / 2008R2 / 2012 / 2012R2 - $ netsh advfirewall firewall add rule Profile=public name="Allow WinRM HTTPS" dir=in localport=5986 protocol=TCP action=allow - -It's time to verify things are working:: - - ansible windows [-i inventory] -m win_ping --ask-vault-pass - -However, if you are still running Powershell 2.0 on remote systems, it's time to use Ansible to upgrade powershell -before proceeding further, as some of the Ansible modules will require Powershell 3.0. - -In the future, Ansible may provide a shortcut installer that automates these steps for prepping a Windows machine. +Admins may wish to modify this setup slightly, for instance to increase the timeframe of +the certificate. .. _getting_to_powershell_three_or_higher: Getting to Powershell 3.0 or higher ``````````````````````````````````` -Powershell 3.0 or higher is needed for most provided Ansible modules for Windows. +Powershell 3.0 or higher is needed for most provided Ansible modules for Windows, and is also required to run the above setup script. Looking at an ansible checkout, copy the `examples/scripts/upgrade_to_ps3.ps1 `_ script onto the remote host and run a powershell console as an administrator. You will now be running Powershell 3 and can try connectivity again using the win_ping technique referenced above.