When many Windows administrators think of installing applications even very basic ones it’s always… Next Next Next Finish. Ansible and configuration management tools like it don’t work like this, they can’t press Next. They require silent installers that run start to finish on their own. My recommendation for solving this...
This is the final part of a three part series. In the first entry of this series we configured Vagrant and built our basic inventory for Ansible. We then used Ansible to create a common role with basic tasks that we need to complete on all hosts. Now we will create specialized playbooks to create both our CONTOSO.com domain controller and create a basic member file server to the domain.
In the first entry of this series we configured Vagrant and VirtualBox to deploy a pair of basic Windows 2012 R2 virtual machines. We built our basic inventory for Ansible and verified we could connect to our newly created virtual machines. Now we can get onto the real work – developing Ansible playbooks.
This series of articles we will be setting up a local virtual environment for use in testing Ansible Playbooks. For our example test environment we will start with a simple configuration of two servers. One domain controller for the CONTOSO.com domain running Windows 2012 R2 and one member server that handles simple file shares.
While Ansible started life as a orchestration and configuration as code platform for Linux it’s ability to manage Windows systems has been steadily increasing. Working with Ansible and developing playbooks has been somewhat challenging on the Windows platform which likely holds back it’s use on that platform (look no farther than the lack of Windows playboks on Ansible Galaxy for evidence). However with the introduction of Windows Subsystem for Linux and expanded Windows support in last year things have become much better. I work in a mixed Windows/Linux environment hosted on an internal VSphere environment (we can’t all be cloud native unicorns). To support that environment and move us to a more sensible ‘infrastructure-as-code’ configuration, I now do Ansible playbook development for Windows and Linux on an almost daily basis from my Windows 10 workstation.