Posted on

Setting up a Virtual Lab – 0x01 – Creating a Windows AD Enviroment

Resources:

Microsoft setup guide

Windows Server 2012 Evaluation

 

 

Download a server iso – for this I used Windows Server 2012. I am purposely not using 2016 because I want to simulate an older environment.

I grabbed an evaluation copy from Microsoft’s Eval Center.

As soon as that was finished downloading, I created a new VM using VirtualBox and started the setup

001.png

I’m one of those GUI guys… I could go without it but I want to be able to poke around a bit since I am no expert.

002.png

One that is finished, I setup the network adapter to the host only adapter since I do not want this machine (or any in my lab environment) to talk to the outside world. Firewall rules should prevent it, but why take the chance?

003.png

Now that that is setup, I am going to install Win 10 Enterprise onto another VM.

Back to the server

Log in using [Host Key]+Del

The first thing I will need is AD DS or Active Directory Domain Services.

  1. Add Roles and Features
  2. Next
  3. Role Based > Next > Next
  4. Check AD DS > Add Features > Next
    004.png
  5. In the features list, make sure Group Policy Management is Checked
  6. Next > Next > Check Restart Automatically > Install
    005.png

Now that that is finished, I need to setup this machine as a DC.

In server Manager, click the flag > promote this server to a domain controller.

006.png

Since I do not already have a domain setup, I will create one.

007.png

Setup a new DNS server

008.png

This error looks like it is normal – the microsoft site shows the same thing

009.png

My hostname is now set to ALLZA so we are all good here!

010.png

I will leave the default folder locations.

Now I will start the installation of AD DS

011.png

 

After restarting it looks like I am getting a domain\ login prompt so that is a good sign!

012.png

Login successful! Let’s check AD and make sure that it shows up properly.

Side note: I had that I used 2012 and not 2012 R2 – it has the charm window instead of the start menu… I am going to fix that with classic shell.

Things look alright with the exception of my hostname being incorrect. This might just take a reboot to fix.

013.png

 

It actually looks like restarting did not change it, so I will update it.

I probably should have updated the name before making the server a DC, but that is okay. It looks like there are just a couple more steps to take to make sure everything works as it should after updating the name.

  1. Update DC Name
  2. Reboot
  3. Check to make sure hostname updated (success)
  4. Now I need to update the name of the Domain System Volume
  5. ADUC > System > DFSR-Global Settings > Domain System Volume > Topology
  6. Right click WIN-blah and click rename
    014.png
  7. Rename to hostname (Allza-DC01)
    015.png

Now we should be good for the basic domain setup!

Leave a comment