Skip to content

Commit bd0960f

Browse files
joaocgreisStefanStojanovic
authored andcommitted
ansible,doc: update Windows manual steps
PR-URL: #3211 Reviewed-By: Richard Lau <rlau@redhat.com>
1 parent b36beec commit bd0960f

File tree

1 file changed

+33
-4
lines changed

1 file changed

+33
-4
lines changed

ansible/MANUAL_STEPS.md

Lines changed: 33 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -617,9 +617,35 @@ Install the `pywinrm` pip module: `pip install pywinrm`
617617
The preparation script needs to be run in PowerShell (run as Administrator):
618618
619619
```powershell
620-
iwr -useb https://raw.githubusercontent.com/ansible/ansible/devel/examples/scripts/ConfigureRemotingForAnsible.ps1 | iex
620+
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
621+
Invoke-WebRequest "https://raw.githubusercontent.com/ansible/ansible/devel/examples/scripts/ConfigureRemotingForAnsible.ps1" -OutFile "ConfigureRemotingForAnsible.ps1"
622+
.\ConfigureRemotingForAnsible.ps1 -ForceNewSSLCert true -CertValidityDays 3650
621623
```
622624

625+
#### Port Configuration
626+
627+
Delete the unencrypted WinRM endpoint:
628+
629+
```powershell
630+
winrm delete winrm/config/Listener?Address=*+Transport=HTTP
631+
```
632+
633+
On Rackspace hosts, it is necessary to change the port to match the value found in secrets (change 12345):
634+
635+
```powershell
636+
winrm set winrm/config/Listener?Address=*+Transport=HTTPS '@{Port="12345"}'
637+
```
638+
639+
On Azure, changing the ports is done in the Load Balancer configuration using the Azure Portal.
640+
641+
To see the status of running listeners:
642+
643+
```powershell
644+
winrm enumerate winrm/config/listener
645+
```
646+
647+
#### Test
648+
623649
Test the connection to the target machine with `ansible HOST -m win_ping -vvvv`. If there is any issue, please refer to the official Ansible documentation in [Setting up a Windows Host][].
624650

625651
## jenkins-workspace
@@ -734,9 +760,6 @@ NFS_BOOT_SERVER_IP:PATH_TO_TFTP_BOOT_EXPORT /boot nfs4 nfsvers=3,rw,noexec,async
734760

735761
After these steps are performed and the Pi's are running, Ansible can be run to finish setup. A reboot is recommended after initial setup to ensure the environment is configured correctly (locale and other settings that are changed).
736762

737-
[Setting up a Windows Host]: https://docs.ansible.com/ansible/latest/user_guide/windows_setup.html
738-
[newer Ansible configuration]: https://github.com/nodejs/build/tree/main/ansible
739-
[stand-alone]: https://github.com/nodejs/build/tree/main/setup/windows
740763

741764
## IBM i
742765

@@ -800,3 +823,9 @@ mkdir -p /u/unix1/java
800823
cd /u/unix1/java
801824
pax -rf /u/unix1/SDK8_64bit_SR6_FP10.PAX.Z -ppx
802825
```
826+
827+
828+
829+
[Setting up a Windows Host]: https://docs.ansible.com/ansible/latest/user_guide/windows_setup.html
830+
[newer Ansible configuration]: https://github.com/nodejs/build/tree/main/ansible
831+
[stand-alone]: https://github.com/nodejs/build/tree/main/setup/windows

0 commit comments

Comments
 (0)