Windows: Virtualbox & VMware
Supported Provisioners
- Virtualbox
- A licensed copy of VMware Workstation
- The VMWare Desktop Vagrant plugin is $79 and is required to use Vagrant with VMware.
- Install it with
vagrant plugin install vagrant-vmware-desktop. - License it with
vagrant plugin license vagrant-vmware-desktop <path_to_.lic>. - Additionally, the Vagrant VMware Utility must also be installed
If you have both Virtualbox and VMware installed, consider disabling the network adapters for the provider that you are not using. For example, if you want to build DetectionLab using Virtualbox, disable the VMware network adatpers (or vice-versa) to avoid a conflict. 
Instructions
- Ensure the prerequisites listed above are installed and that you meet the system requirements
- Clone the DetectionLab repo to your filesystem:
git clone https://github.com/clong/DetectionLab.git - Using a terminal, navigate to the DetectionLab/Vagrant repository and run .\prepare.ps1 to verify that your system has all of the prerequisites installed:
At this point in time, there are two ways to bring up DetectionLab. We can bring up the hosts one at a time using vagrant up --provider=<provider> command. The provider options are virtualbox or vmware_desktop. However, there is also a faster way explained below.
Speed Up Installation by Provisioning Hosts in Parallel
Alertatively, to speed up the provisioning process, we can bring up some hosts in parallel. To do this, I recommend opening 4 separate terminal windows open to the DetectionLab/Vagrant directory. In terminal windows 1 and 2, you can run vagrant up logger and vagrant up dc at the same time. Before we can bring up wef and win10, we have to wait for the dc host to finish creating the domain. Once it has passed that step of the provisioning process, you can run vagrant up wef and vagrant up win10 in terminal windows 3 and 4 at the same time.
When we run Vagrant up, here’s what happens:
- Vagrant will bring up one host at a time, starting with logger and followed by dc, wef, and win10.
- Three boxes will be downloaded from Vagrant cloud:
- Each box will go through provisioning, which configures the host and installs software.
After running vagrant up --provider=vmware_desktop or vagrant up --provider=virtualbox, you should see something like this:
PS C:\Users\build\DetectionLab\Vagrant> vagrant up --provider=virtualbox
Bringing machine 'logger' up with 'virtualbox' provider...
Bringing machine 'dc' up with 'virtualbox' provider...
Bringing machine 'wef' up with 'virtualbox' provider...
Bringing machine 'win10' up with 'virtualbox' provider...
==> logger: Importing base box 'bento/ubuntu-18.04'...
==> logger: Matching MAC address for NAT networking...
==> logger: Checking if box 'bento/ubuntu-18.04' version '202007.17.0' is up to date...
==> logger: Setting the name of the VM: logger
==> logger: Clearing any previously set network interfaces...
==> logger: Preparing network interfaces based on configuration...
logger: Adapter 1: nat
logger: Adapter 2: hostonly
==> logger: Forwarding ports...
logger: 22 (guest) => 2222 (host) (adapter 1)
==> logger: Running 'pre-boot' VM customizations...
==> logger: Booting VM...
==> logger: Waiting for machine to boot. This may take a few minutes...
logger: SSH address: 127.0.0.1:2222
logger: SSH username: vagrant
logger: SSH auth method: private key
logger:
logger: Vagrant insecure key detected. Vagrant will automatically replace
logger: this with a newly generated keypair for better security.
logger:
logger: Inserting generated public key within guest...
logger: Removing insecure key from the guest if it's present...
logger: Key inserted! Disconnecting and reconnecting using new SSH key...
==> logger: Machine booted and ready!
==> logger: Checking for guest additions in VM...
==> logger: Setting hostname...
==> logger: Configuring and enabling network interfaces...
==> logger: Mounting shared folders...
logger: /vagrant => C:/Users/user/DetectionLab/Vagrant
==> logger: Running provisioner: shell...
logger: Running: C:/Users/build/AppData/Local/Temp/vagrant-shell20200813-3372-yqjhma.sh
logger: [05:34:56]: Adding apt repositories...
logger: Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
logger: Hit:2 http://archive.ubuntu.com/ubuntu bionic InRelease
...
...
If all goes well, this process should continue for 1-2 hours depending on your computer and network speed. The boxes are very large, but only need to be downloaded once.
Once provisoning is finished, you can access the VMs through the GUI or SSH/RDP to them directly. You can also verify services are accessible by running .\post_build_checks.ps1:
If for some reason you encounter an error or any issues, checkout the troubleshooting page linked below. If you can’t find an answer to your question, please open an issue on the DetectionLab GitHub!
Troubleshooting
Visit the troubleshooting page.