Speaking of managed nodes, that's the last little bit here.
How do we configure them?
Well, to prepare Windows hosts for Ansible management,
you're going to need to do, well, a number of things.
Just thinking of how Windows server behaves, none of this is out of the box.
It's all totally understandable.
First, making sure that WinRM service is enabled and configured,
that your endpoints are set up, and they are not by default.
This would be your 5985, 5986 listeners.
You also need to have PowerShell remoting enabled.
You'll need to have the PowerShell execution policy set to at least remote
signed so that Ansible can do remote script execution.
And that also, I'll just add parenthetically,
remote signed means that you're going to need to have I would
suggest Active Directory Certificate Services. So you've got a
free way to print certificates, and you know what I mean by print,
electronically.
In other words,
that's going to mean that your developers are going to
wanna digitally sign your PowerShell, which is frankly a great tip anyway.
Okay, Tim, back on track.
Depending on whether you're in a workgroup environment or not,
you may have to adjust the trusted host list.
So those are all things.
And then lastly, I guess, but wait.
There's more.
There is enabling CredSSP if that's required.
Now,
the bad news is that seems kind of fiddly. The good news is that you may
already have crossed this bridge because you're already using Windows
PowerShell remoting or just PowerShell remoting.
And number 2,
you don't have to worry because Ansible created a really nice script for us.
I gave you the latest version of it in the exercise files. And
you just run that digitally signed script on your Windows nodes,
and you're good to go. Easy as pie.