In my previous post I’ve created a Ubuntu template into VMware vSphere using Packer. Time to build now a Microsoft Windows template.
Raise your hand if you love to rebuild everytime your home lab manually! Noone, right? you either end up trying to not breaking it, thus defeating the purpose of the lab, or you spend insame amount of hours to fix it everytime, or to rebuilding it from scratch. So, automation in our home labs has always been a huge topic, and there are around many posts in these regards. So, why my own version? Because I found around some posts that I used to create my own automation, but none of them was perfect for my needs. I love beers, so let me use this example: like an home brewer (which I’m not, by the way) during this year I made my own recipe. It may not be the best one around, but it’s my own personal recipe. If you find it useful too, be my guest!
In the previous posts I’ve started to show you some of the possible uses of Ansible, in particular some example for managing Windows machines. As I’ve explained in the first post about Ansible, the software can login into any Windows machine using both local or domain users. In the latter case,…
After I configured my Ansible server to manage my windows machines in the previous article, one of the first tasks I planned to automate was patching. Patching is one of those extremely boring but needed activities, and in any environment, even with a small amount of server, automated patching may be a savior. As long as proper data protection is in place, like a daily backup of the involved virtual machines, we can safely plan automatic updates, and if anything goes wrong, we just need to revert the virtual machine to the previous state.
As I’m studying Ansible, one of my goal is to manage my several Windows machines with it. I know it sounds strange as Ansible was first designed to deal with Linux systems, but this powerful configuration management platform supports Windows since version 1.7, and is completely agentless: it relies on SSH for linux/unix machines, and Windows Remote Management (WinRM) for Windows machines. Through WinRM, Ansible can connect to Windows machines ard run PowerShell scripts. The idea of using Powershell as the main code to execute tasks in Windows systems, together with the agentless approach, made me be even more curious in learning more about the Windows support.