From 5f13af97b8804ca40ee2f230cd29e732a92ccbcd Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Thu, 19 Jun 2014 16:57:03 -0500 Subject: [PATCH] Remove part about powershell upgrade (for now). --- docsite/rst/intro_windows.rst | 20 ++++++-------------- 1 file changed, 6 insertions(+), 14 deletions(-) diff --git a/docsite/rst/intro_windows.rst b/docsite/rst/intro_windows.rst index 7389e0a4fa1..cb66573bb02 100644 --- a/docsite/rst/intro_windows.rst +++ b/docsite/rst/intro_windows.rst @@ -120,23 +120,15 @@ bootstrapping! .. _getting_to_powershell_three_or_higher: -Getting to Powershell 3.0 or higher on Remote Systems -`````````````````````````````````````````````````````` +Getting to Powershell 3.0 or higher +``````````````````````````````````` -Additionally, Powershell 3.0 or higher is needed for most modules. You can actually use a minimal -ansible example playbook to upgrade your windows systems from Powershell 2.0 to 3.0 in order to take -advantage of the *other* ansible modules. +Powershell 3.0 or higher is needed for most modules. -Looking at an ansible checkout, copy the examples/scripts/upgrade_to_ps3.ps1 script from the repo into -your local directory, and run a playbook that looks like the following:: +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: - - hosts: windows - gather_facts: no - tasks: - - script: upgrade_to_ps3.ps1 - -The hosts in the above group will then be running a new enough version of Powershell to be managed -by the full compliment of Ansible modules. + ./upgrade_to_ps3.ps1 .. _what_windows_modules_are_available: