-
Notifications
You must be signed in to change notification settings - Fork 5
2. Design
This project uses Vagrant and a collection of powershell\bash scripts to provision and configure VMs.
Windows base images are from DetectionLab. Many thanks to them ♥.
| VM Name | OS |
|---|---|
| WINSRV01 | Windows Server 2016 |
| WINSRV02 | Windows Server 2016 |
| WIN01 | Windows 10 |
| NIX01 | Ubuntu 20.04 |
Resource Utilization:
Note that you can decrease\increase the specs below (it's really easy) based on your needs.
| VM | CPU | RAM |
|---|---|---|
| NIX01 | 1 | 1GB |
| WIN01 | 2 | 4GB |
| WINSRV01 | 1 | 2GB |
| WINSRV02 | 1 | 2GB |
I would set the WIN01 VM to 1 cpu core if I am not running Visual Studio or analyzing malware:
I rarely run all VMs at the same time. If you want to, you can.
Utilization based on setups (quick maths):
- AD + WIN setup = 3 cores, 6GB ram
- NIX + WIN setup = 3 cores, 5GB ram
- AD + NIX setup = 3 cores, 3GB ram
- IIS + NIX setup = 3 cores, 3GB ram
- AD + IIS + NIX setup = 3 cores, 5GB ram
When running all VMs: 5 cores, 9GB ram.
| VM | AD Server | Join to Domain | IIS Web Server | Standalone |
|---|---|---|---|---|
| WINSRV01 | ✅ | ❌ | ❌ | ✅ |
| WINSRV02 | ❌ | ✅ | ✅ | ✅ |
| WIN01 | ❌ | ✅ | ❌ | ✅ |
| NIX01 | ❌ | ❌ | ❌ | ✅ |
✅ = You can enable this setup for the VM. ❌ = Setup not available.
AD Server: VM can be promoted to a Domain Controller.
Join to Domain: VM can be joined to domain. Requires a machine with setup "AD Server" to be available.
IIS Web Server: IIS Web Server can be installed on the VM.
Standalone: VM can be created and used without requiring any other VM to exist. Note that "Join to Domain" feature can not be used when using a VM in standalone setup.