Setting Up a Virtual Network Lab with VMware Workstation and pfSense – Part 5, DHCP server

Now that we have our server set up for DNS and Active Directory we need to add one final role. We need a DHCP server on our network to handle giving out IP addresses. Since we turned DHCP off on our pfSense router in part 1 of this tutorial we need to add it to the server. So here we go… On the Server Manager dashboard click add roles which will start the add roles and features wizard. on the before you begin screen click next.


For installation type choose role based and click next.


select your server and click next.


Select the DHCP Server role.


and accept the required features by clicking add features.


for features accept the defaults and click next.


review the DHCP Server screen and click next


then click install and let the install complete and click close.


In the Server Manager dashboard up in the right hand corner by the task flag indicator you will see a yellow exclamation mark trying to get your attention. click it to open the task details and click the link “Complete DHCP configuration”. This will open the DHCP Post-Install configuration wizard.


Review the first window and click next.


Select “Use the following user’s credentials” and click commit


review the summary and click close.


Now go to Server Manager tools and open the DHCP manager. Right click the IPv4 node and select “New Scope” from the menu.


This will start the “New Scope Wizard” click next.


Name your scope, I chose bimpression-lan, and give it a short description.


Enter the IP info for your network from part 1 of this tutorial. Our start IP will be and the end IP will be with a class c subnet mask of and click next.


In the next window we will add an exclusion range for IP’s that we don’t want the DHCP server to hand out. I would like to keep the first 90 IP addresses for other things like static IP’s so I’ll add the range of – to the excluded address range list and click next.


You can set the lease duration for the IP’s, I accepted the default and click next


Select Yes for configuring DHCP options and click next.


Enter the router info, in our case its and click next.


On the next screen you can accept the defaults and click next.


Add the WINS Server and click next.


Select yes to activating the scope now and click next.


Click finish.


Now reboot the server and once rebooted log in and go back to the DHCP manager where you can review your new scope.


you can now start up your virtual client that we created in Part 2 of this tutorial and go to the cmd prompt and give an ipconfig /all command. you can see that it now has an IP address in the range that we set our DHCP server to hand out. the DNS sever is also listed correctly.


Now when you go back to your server with the client still running you can view it in the DHCP manager under address leases, you will see the Client01 pc in your domain.


Our next step will be to add the Client01 PC to the active directory domain. Stay tuned!

Setting Up a Virtual Network Lab with VMware Workstation and pfSense – Part 4 DNS and Active Directory

Now that we have a clean server install we can start adding roles for DNS and the Domain Controller. The first thing we must do is give the server a staticĀ IP address and a preferred DNS server. For the static IP I’ll use and I’ll use a local DNS address of since this server will act as the DNS server. Then reboot the server.


Once we have our IP set up we can start by adding the DNS role to the server. From the Server Manager dashboard choose “Add roles and Features” to start the Add Roles and Features Wizard.


Click next and under select installation type choose “Role based or feature based installation and click next.


in the Select destination server screen you should see the static IP that you set earlier. Highlight the server and click next.


You can now select the DNS server role.


and then add the default features that are needed for the DNS server role.


for the Features screen accept the defaults and click next.


then on the DNS Server window you can review the info and click next.


in the confirmation window click the install button.


You can see the installation of the role.


Once the installation is complete you can close the window and your DNS server role is installed. You can now go to server manager Tools and open the DNS Manager to prove the role has been installed successfully.


Now that we have the DNS role installed we can install our Active Directory Domain Services role. the steps are very similar to the once for installing the DNS role. From the Server Manager dashboard choose “Add roles and Features” to start the Add Roles and Features Wizard and click next.


accept the role based or feature based installation and click next.


Select your server from the list and click next.


select the Active Directory Domain Services from the server roles.


and under the add features that are requited for Active Directory Domain Services accept the defaults and click Add Features.


in the Features window accept the defaults and click next.


review the Confirmation window and click install.


When the installation is complete click close and notice that on the Server Manager dashboard you will see a yellow exclamation up in the right hand corner by the task flack. click that and you should see the task details where you can click the “Promote this server to a domain controller.


This will start the “Active Directory Domain Services Configuration Wizard”. in the Deployment Configuration windows choose “Add a new forest” and give it a Root domain name, I choose, and click next.


On the Domain Controller Options I accepted the defaults and entered a password for the DSRM and click next.


On the following screen you will get a warning which you can ignore for now and click next.


Under additional options enter a NetBIOS name and click next


in the paths screen choose the paths you want, I accepted the defaults and click next


review the options and click next.


Windows will run a prerequisites Check, let it finish and it should be successful with a few warnings. go ahead and click install.


Once installed the server will reboot automatically. on the log in screen notice that you are now logging in to the domain that you have created.


once logged in you can go to the Server Manager tools and you will see the active directory tools that are now available to you.


We now have our server set up as a DNS Server and a Domain controller but we also need a DHCP server on our virtual private network and we will install that role in part 5 of this tutorial so stay tuned!

Setting Up a Virtual Network Lab with VMware Workstation and pfSense – Part 3 the server

In part 3 of this tutorial I’ll set up a virtual Windows 2012 R2 server that will act as our DNS server, Domain Controller and a DHCP Server for our virtual private network. The server install is pretty straight forward and I won’t go into much detail. So here we go. First we’ll create another typical virtual machine.


Once again choose to install the operating system later.


Select Microsoft Windows version Windows Server 2012 for the operating system.


Name the virtual machine and choose a location for it.


Then choose the disk capacity, I kept the defaults.


no we need to customize the hardware and change the network adapter to use our custom virtual network we created in part 1 of this tutorial.



now drop the windows server install media into the dvd drive by browsing to the iso image.


We can now start the virtual machine and install the software. The following screens will show the install progress.

Language and keyboard selection
Install now
Choose the version of the server (choose one with a GUI)
Accept the license terms
Choose custom install
Select the partition to install to.
Let the install happen
Once installed choose an admin password and reboot.
Once rebooted, send a Ctrl+Alt+Delete to the machine to get to the login screen.
Log in with the admin password that you created
Choose yes to automatically connect to devices on your network.
Change name of sever to something meaningful (I chose Server01) and set the time and time zone.

We now have a brand new server. As you can see it cant find a DNS server and isn’t getting a proper IP address. I part 4 we will take care of this so stay tuned!