Ansible Playbook

• And than you can launch the ansible provisioning with (note that the vms must be in a running state, so vagrant up must have been done before that)

• Or you can run playbooks one by one (mostly for debug or if you get trouble during install)

  • The main.yml playbook is build in multiples parts. each parts can be re-run independently but the play order must be keep in cas you want to play one by one :

ansible-playbook main.yml # this will configure the vms in order to play ansible when the vms are ready

ansible-playbook build.yml        # Install stuff and prepare vm
ansible-playbook ad-servers.yml   # create main domains, child domain and enroll servers
ansible-playbook ad-trusts.yml    # create the trust relationships
ansible-playbook ad-data.yml      # import the ad datas : users/groups...
ansible-playbook servers.yml      # Install IIS and MSSQL
ansible-playbook ad-relations.yml # set the rights and the group domains relations
ansible-playbook adcs.yml         # Install ADCS on essos
ansible-playbook ad-acl.yml       # set the ACE/ACL
ansible-playbook security.yml     # Configure some securities (adjust av enable/disable)
ansible-playbook vulns.yml        # Configure some vulnerabilities

• When you finish playing you could do :

vagrant halt # will stop all the vm

• To just relaunch the lab (no need to replay ansible as you already do that in the first place)

vagrant up   # will start the lab

• If you got some errors see the troubleshooting section at the end of the document, but in most case if you get errors during install, don't think and just replay the main playbook (most of the errors which could came up are due to windows latency during installation, wait few minutes and replay the main.yml playbook)

ansible-playbook main.yml