ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Remove part about powershell upgrade (for now).

Browse source
This commit is contained in:
Michael DeHaan 2014-06-19 16:57:03 -05:00
parent e6cd216ade
commit 5f13af97b8
1 changed files with 6 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docsite/rst/intro_windows.rst
View file

@ -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: