Goku

Active Directory Domain Controller with a power-level that's OVER 9,000!

Goku will serve as the Capsulecorp domain controller. You'll want to dovagrant up this VM first and make sure everything is working before bringing up any other VMs

Bring up and provision this VM with the following command:

vagrant up goku

If you've already brought up the VM and need to reattempt the ansible provisioning simply run:

vagrant provision goku

Configuration Files

These files contain all of the configuration information for this VM. You should feel free to customise these files to your personal needs.

Primary ansible provisioning playbook

Replace these dc_address and dc_gateway values with IP addresses that make sense for your LAN.

capsulecorp-pentest/goku.yml at master · R3dy/capsulecorp-pentestGitHub

master/goku.yml

Install Active Directory and promote server to DC

This provisioning task causes the majority of problems users have reported simply due to the inconsistency with which Windows servers behave during the process of installing Active Directory and then promoting to a DC.

That is to say, you could run this provision script, destroy the VM, bring up a new one and provision it a dozen times and you'll notice it takes anywhere from 5-10 minutes longer/shorter each time.

Unfortunately the best I can offer you is if this fails, destroy the VM bring up a new one and try it again.

capsulecorp-pentest/roles/promotedc/tasks/main.yml at master · R3dy/capsulecorp-pentestGitHub

master/roles/promotedc/tasks/main.yml

Active Directory accounts

These accounts get provisioned to the Capsulecorp.local domain

capsulecorp-pentest/roles/promotedc/tasks/accounts.yml at master · R3dy/capsulecorp-pentestGitHub

master/roles/promotedc/tasks/accounts.yml