Home Lab Active Directory Setup
Type: #Homelab
Software: Oracle VM VirtualBox Manager
This walkthrough involves setting up and configuring the active directory on Microsoft Windows Server 2019, using Oracle VM VirtualBox Manager as the virtualization software. Download links are available here:
https://www.virtualbox.org/wiki/Download_Old_Builds_6_1
https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2019
Before starting the installation I configured the settings of the Windows server, changing the network adapter to bridged and removed the floppy disk from the boot order. This allows the machine to be booted from the ISO.
After this, a custom install was selected. This will install a clean operating system and will be used as the domain controller for my virtual server.
Upon Installation the name will need to be changed to DC this can be done via Settings.
After this a client machine will need to be set up, this can be done by installing the Windows 10 enterprise edition from https://www.microsoft.com/en-gb/evalcenter/download-windows-10-enterprise and selecting 64-bit download. This machine has the same settings as the server, using a bridged network and removing the floppy disk. The machine is called the helpdesk to replicate a real scenario. This machine will need to have its name changed to helpdesk in the settings, and then cloned, creating a new machine called staff.
Next, the DC virtual machine needs to be re-launched. Installing active directory can be done via the server manager.
Following the installation wizard, within the results section a new forest can be created; a forest is a logical container that contains the domains, users, computers and group policies. This can be done after promoting the server to a domain controller
Following the installation wizard, and waiting for the installation, after a restart the domain controller was successfully installed.
The next stage is to create a new user, I created a helpdesk account, and will then allocate it some permissions.
Clicking properties on the helpdesk account and navigating to “member of” I allocated the helpdesk the domain admin role.
Launching the helpdesk virtual machine, the domain controller IP address can be set as the helpdesk’s DNS server.
After this the domain name can be entered through access work or school, followed by entering the credentials established by the dc.
Navigating to the domain controller, under the management for active directory > computers the helpdesk virtual machine can be seen, confirming their connection.
The staff machine will not be configured due to hardware limitations; the next steps for understanding would be:
https://tryhackme.com/room/activedirectoryhardening
https://tryhackme.com/room/adenumeration
https://tryhackme.com/room/exploitingad