Windows Server VM
Last updated
Last updated
I usually go with a Windows Server 2019 VM with VMWare or Virtualbox. I have VMWare Workstation Pro but Player works just as well. You can go with either VMWare or Virtualbox, both work and it just comes down to personal preference on the application and what you're use to.
Obviously your setup may differ depending on your system specs. I typically go with 4GB(4096 MB) of RAM per VM, 2 processors and 2 cores per processor but I am running with 32GB of RAM and an Intel i7-10750H.
If you need to, you can start with 4 or 8GB of RAM and 2 processors and 2 core per processor, for the install so it goes faster then drop it down to 2 or 4GB of RAM and 2 processors and 1 core per processor for the victim machines.
Start with our Typical Configuration
Install the Operating System Later
Choose Windows and i'll be doing Server 2019 but you can go with whatever edition you're installing
Choose the path for it and the Name of the VM
Select the size of the VM. This will NOT the overall size, this is just the max size of the VMs HDD space and will fill up as we add more to the VM that takes up space.
If this VM will be on a PC and not be used from an external HDD or moved around you can store it as a single file but if you plan on using this VM on other PC or from an external HDD it's a better idea to split it into multiple files.
Depending on your space, you can edit how much you want. I usually go with the default personally.
Finally we can now customize our hardware. This is where we can customize the RAM, Processors, ISO files, Network Settings, etc. This is where we select our Windows Server ISO.
I usually increase the RAM for the install so it goes quicker then drop it down after.
Start our VM and be ready to push a button to boot to the ISO as the screen will say. This is a pretty standard install, mostly just clicking next.
Choose the "Windows Server 20XX Standard Evaluation (Desktop Experience)"
Go Custom Install
Click Next
Let it install
After install is done, the VM should reboot and bring you to a screen to set your Admin password.
After that you should be good to log in!
Now we install VMWare tools with VM > Tools > Install VMWare Tools
Now we can open File Explorer and go to "This PC" to run the Installer.
This is a typical install, just click next through it all. This will ask to restart the PC, but don't do that yet, we will have to restart anyway in the next parts of the setup.
Now is when you will want to shut down the VM and adjust RAM and Processors if needed. Drop it for 2GB or 4GB of RAM and 1 or 2 processors.
I HIGHLY recommend creating a snapshot after you have this done and setup so that way you can always revert back to that snapshot if needed if something breaks or you just need to clean things up.
Now I am going to take this tip from John Hammond. After you create the Snap Shot, I recommend going into the VMS options, changing the name to Some form of Template and Options and enabling Template mode. So clone the VM choosing the Snapshot when we want to make a VM using this one so we don't have to re-create the VM from scratch every time.
We have our Server Dashboard open
To set this up for our domain controller, in top right: Manage > Add Roles and Features
Most of this will be standard of clicking next
Role-based or feature-based Installation
Now is where we select "Active Directory Domain Services", with the popup, Select Add Features, then click next.
From here it'll be "Next" till the end
Click Install and let it install
Installed!
Now we should name our Domain Controller. Start Menu > Search for "Rename"
Click "Rename this PC"
Rename it to what you see fit
Restart the VM
Our Dashboard is showing us a "Warning" Dialog
Click Promote this server to a domain controller
We're going to add a new Forest and give it a name
Give the DSRM a password. I set it the same as the Admin password. (Not the most secure, but this is for a lab environment)
Then from here it'll be standard Next to Install
This screen may take a min to finish loading
Now we install it
Once done will automatically reboot. After reboot and login, we should now see
After we Setup user machine and connect them to the Domain, we will do more.
Now that we have the basics out of the way, lets add some users, groups, and policies.
From the Server Manager Dashboard > Tools (Top Right) > Active Directory Users and Computers
I'm going to make a separate Organizational Unit (OU) for Groups just for organization.
Right Click on the Domain.local > New > Organizational Unit
Then Select all the Groups and Drag them into the Groups Folder, so there should only be Administrator and Guest in the Users folder and all the groups in the Groups folder. Easy.
So let's add our Users. Right click in a blank area in Users > New > User
Add some users and choose the naming convention. For my example my user doesn't have a last name but if you choose to and want to have a naming convention of first.last or FLast or FirstL, this is where you do that.
Give the user a password, uncheck making the user change the password, and set the password to never expire. This is a VERY bad practice but for a lab environment things will setup a little different than in the real world, at least we hope.
Make another user BUT instead of creating it, right click on Administrator, copy it, and follow the same procedure. This will create a second Domain Admin account.
Create a second base normal user as well.
Now we're also going to setup a file share. From the Server Manager Dashboard > File and Storage Services (Left Hand Side) > Shares
From the top click on Tasks drop down and select new share > SMB Share - Quick > Next
Give the share a name
Then just click next till it asks you to create it, create the share.
Now we are done!
IF you want the other VMs that will join this Domain to have Windows Defender disabled, I recommend doing this for simplicity sake, IF you are pentesting against this and having another VM setup with Defender Enabled to test things against that.
Start Menu > Group Policy > Right Click and Run as Admin
Right click on out domain and Create a new Group Policy in this domain (Top option).
Name this "Disable Windows Defender"
Right click on newly added "Disable Windows Defender" GPO on the left and Edit it
Drill Down: Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Defender Antivirus
Double click on the "Turn off Windows Defender Antivirus" > Enabled > Apply > Ok
Close out of the Group Policy Management Editor and on the Group Policy Management Window, with the Disable Windows Defender selected, if 'Enforced' says no, right click on it, and enforce it
Now we are done!
Again, I HIGHLY recommend creating a snapshot after you have this done and setup so that way you can always revert back to that snapshot if needed if something breaks or you just need to clean things up.
Starting with typical setup
Install the Operating System later
Choose Windows Server 2019 as the the closest we can get at the current moment.
Choose the path for it and the Name of the VM
Select the size of the VM. This will NOT the overall size, this is just the max size of the VMs HDD space and will fill up as we add more to the VM that takes up space.
If this VM will be on a PC and not be used from an external HDD or moved around you can store it as a single file but if you plan on using this VM on other PC or from an external HDD it's a better idea to split it into multiple files.
Depending on your space, you can edit how much you want. I usually go with the default personally.
Finally we can now customize our hardware. This is where we can customize the RAM, Processors, ISO files, Network Settings, etc. This is where we select our Windows Server ISO.
I usually increase the RAM for the install so it goes quicker then drop it down after.
Start our VM and be ready to push a button to boot to the ISO as the screen will say. This is a pretty standard install, mostly just clicking next.
Once we get to this screen, we have some options. Typical it's with or without Desktop experience. I'm use to Desktop Experience with 2019 and previous, so i'm going to switch it up this time go with out the Desktop experience so it's just CLI(Command Line Interface).
Hit he checkbox to agree to terms, and next
Custom
Select the drive and click next and let it install, it will automatically reboot.
Once it reboots, follow the prompts, set your admin password. and you'll be brought to the SConfig menu.
I would start by going to 6, then 1 to update everything
Once updated are complete and a reboot is done, I recommend installing VMWare tools. First we need to shutdown the VM and remove the ISO file. Edit the VM Settings. I'm choosing physical drive simply because my machine does not have a CD Drive.
After you've powered back on the machine, from the VMWare menu > VM > Install VMWareTools. Then from the SConfig, type 15 to go to the powershell menu, go to the D: Drive and running setup64.exe
We may need to move the window to see the VMWare Tools window.
After this install and reboots, we can shut it down.
Now is when you will want to shut down the VM and adjust RAM and Processors if needed. Drop it for 2GB or 4GB of RAM and 1 or 2 processors.
I HIGHLY recommend creating a snapshot after you have this done and setup so that way you can always revert back to that snapshot if needed if something breaks or you just need to clean things up.
Now I am going to take this tip from John Hammond. After you create the Snap Shot, I recommend going into the VMS options, changing the name to Some form of Template and Options and enabling Template mode. So clone the VM choosing the Snapshot when we want to make a VM using this one so we don't have to re-create the VM from scratch every time.
We should first run SConfig to change the hostname and set a static IP.
After this we can run the following command to turn this into a DC.
Now once it has been restarted we can add computers to the domain. We can do this via GUI, or command line with
Add-Computer -DomainName web.local -Credential web\Administrator -Force -Restart - Changing the web.local and web\Administrator, to what you changed your DomainName to from the previous step.
