Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Prerequisites

1) WinRM set up to connect to your Windows host from Ansible

2) Ansible set up for Windows Remote Management

3) SSH access to the Ansible host

4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host

5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.

6) At least one Linux host running Ansible and one Windows Server host (I'm using Windows Server 2019 for this demonstration)

Let's first head over to /etc/ansible/hosts and confirm we have our setup in place. You may see some other commented out configs in there which are the typical defaults if you're using a new Ansible server.

[windows]                                                                                  winsrv29 ansible_host=YourWindowsServerIP


[windows:vars]
ansible_user=YourWindowsUsername
ansible_password=YourWindowsPassword
ansible_connection=winrm
ansible_winrm_transport=basic
ansible_port=5985

With our Ansible host up and our Windows Server allowing requests, let's do a quick confirmation that WinRM is doing it's job with a quick ping.

ansible windows -m win_ping

If you do not receive a successful ping, please confirm your firewall accepts ICMP requests (if you're in an organization there may be a reason why your org turned it off) and your Windows Server is accepting requests over port 5985.

Now that we have a successful connection, let's go ahead and run our first PowerShell cmdlet.

ansible windows -m win_shell -a "Get-Service -Name BITS"

Let's analyze the above. we're calling ansible then using windows to call the windows group in our hosts file. Then we use -m that calls a module name which in our case we're using the win_shell module. After that we use the -a to pass args which in our case is the Get-Service cmdlet.

After we run it we should get a response back if the service is running or not.

Running a PowerShell cmdlet is great but what if you have to run a script? Lucky for us we can do that too.

I've created a PowerShell script in /etc/ansible/scripts that simply gets the BITS service and turns it on.

Now let's go ahead and copy our script over to our server by using the win_copy module and running ansible windows -m win_copy -a "src=/etc/ansible/scripts/turnonbits.ps1 dest=C:\\" to copy our script to the C: drive.

Our script is copied over to our location and we're ready to run it!

ansible windows -m win_command -a "powershell.exe -File C:\turnonbits.ps1"

If we run our ansible windows -m win_shell -a "Get-Service -Name BITS" command again, we'll see that BITS is now started!