- Advertisement -
HomeVirtualizationVDIVDI-LAB-2018 – Part 5 – Configuring a Domain Controller server with AD, DNS and DHCP services

VDI-LAB-2018 – Part 5 – Configuring a Domain Controller server with AD, DNS and DHCP services

Summary:

In this part, we are going to deploy a new VM from a Windows server 2016 template, then install and configure the active directory, DNS, and DCHP services for this, our domain controller server. Also, we are going to create the user's infrastructure. This is going to be the most important VM of the infrastructure, this machine, is the one that will manage the whole VDI LAB, providing the rights and access to all the other virtual servers and, more importantly, to all the virtual desktops.

This is part 5 out of 12 of the VDI LAB series. Check out the introduction first.

The ultimate VDI deployment guide (from scratch) with VMware vSphere 6.5 and Horizon View 7.3 – 2018. 😉

1. Prerequisites

  • Network and IP address range designed. This was done in part 1 of this series.
  • Windows Server 2016 template, previously created in part 4 of this series.

2. Deploying the VM from a template

@VCSA

  1. Right-click on Windows Server template and select New VM from This Template...
Part5 Image01
  1. Name this domain controller VM, select ESXi host for the computer resources and leave the rest of the wizard as default.
  2. After the VM is created, change the hardware specs. CPU, RAM, and HDD. For my case, it looks like the image below.
Part5 Image02.1
  1. Power on the VM, the first thing to do is configure the IP address. I’ll use the IP configuration as the image below.
Part5 Image02
  1. Change also the computer name and reboot the VM

3. Install roles and features

- Advertisement -

@Domain Controller Server

  1. From Server Manager go to Dashboard / Add roles and features
Part5 Image03
  1. Click Next to the first option of the installation wizard.
Part5 Image04
  1. Select Role-based or feature-based installation, click Next.
Part5 Image05
  1. Select the current server. It should be the only one available from the pool.
Part5 Image06
  1. Select:
    • Active Directory Domain Service
    • DHCP Server
    • DNS Server
Part5 Image07
  1. Make sure .NET Framework 3.5 and 4.6 are selected. Also Group Policy Management.
Part5 Image08
  1. Click Next on the following steps.
Part5 Image09
Part5 Image10
Part5 Image11
  1. Review the installation and click Install
Part5 Image12
  1. The installation will start, wait until is completed and click Close.
Part5 Image13
Part5 Image14

DHCP service will be installed later, a warning message will show up.

3. Promote the server to a domain controller

  1. From Server Manager, click on the “flag” icon and then Promote this server to a domain controller.
Part5 Image15
  1. Select Add a new forest and choose a name to your domain. This is an important step, this domain name will be used for the whole infrastructure.
Part5 Image16
  1. Leave everything as default and type a DSRM password.
Part5 Image17
  1. Skip this step and click Next.
Part5 Image18
  1. Leave as default or change NetBIOS name.
Part5 Image19
  1. Select a location for AD database, or leave as default
Part5 Image20
  1. Review options
Part5 Image21
  1. Check prerequisites and click Install.
Part5 Image22
  1. The computer must be restarted.
Part5 Image23
  1. Login to the as the new domain configured.
Part5 Image24

4. Configure DHCP service

  1. From Server Manager, click on the “flag” icon and then Complete DHCP configuration
Part5 Image25
  1. Click Next to start DHCP configuration.
Part5 Image26
  1. Select credential and click Next. Use the same as Administrator computer.
Part5 Image27
  1. Close the wizard to finish the initial DHCP configuration.
Part5 Image28
  1. From Server Manager, go to Tools / DHCP
Part5 Image29
  1. Under DHCP, should be the server name, expand it to see IPv4 and IPv6.
Part5 Image30
  1. Right-click on IPv4 and select New Scope...
Part5 Image31
  1. Click Next to start the New Scope Wizard
Part5 Image32
  1. Provide a name and description for this scope.
Part5 Image33
  1. Add IP Address Range. Note that the network was previously configured in part 1 of this series. I’ll start my IP range leaving 20 IP addresses for the virtual infrastructure.
Part5 Image34
  1. Add Exclusions. I will exclude 80 IP address for ESXi host, Login VSI launchers and any other network element of the lab, so I want my DHCP range start from 10.0.0.100, which is the range for the golden images and the desktops.

NOTE: This could be done excluding all these IPs from step 10, but I prefer this option.

Part5 Image35
  1. Set Lease Duration. I am leaving 8 days as default.
Part5 Image36
  1. Confirm the configuration of the DHCP.
Part5 Image37
  1. Set and Add Router (default gateway) IP address.
Part5 Image38
Part5 Image39
  1. Set Domain Name and DNS Servers. I am using this server (Domain controller) and the Router IP address.
Part5 Image40
  1. Set WINS Servers if needed. This option won't be configured for this LAB.
Part5 Image41
  1. Activate the scope.
Part5 Image42
  1. Click Finish to complete the scope configuration.
Part5 Image43
  1. From IPv4 / Scope / Address pool we can see that the pool is all set now.
Part5 Image44
  1. There is no need to do extra configuration for the DNS. We can go to Server Manager / DNS, Right-click on computer name and select DNS manager.
Part5 Image45
  1. From the computer name and domain name we can confirm that so far our only computer added to the DNS list is this one, the domain controller. All other servers and desktops will be added to this list.
Part5 Image46

5. Create OU and Add users

Let’s create users for vCenter, View Composer, events database and another one for this domain controller (those can be added later).

NOTE: If it is planned to use VCSA as vCenter and not Windows server based, this vCenter user is not necessary. For vSphere 6.7 this is the best option.

  1. First, add a new OU (Organization Unit) to “organize” all our infrastructure.
Part5 Image47
  1. I will call this OU “VM”.
Part5 Image48
  1. Add two more OU, Computer and Users. Add (drag and drop) the domain computer from Computer into the new Computer OU.
Part5 Image49
  1. From the User OU, right-click and select New / User
Part5 Image50
  1. Create vCenter user. Use the image below as an example.
Part5 Image51
  1. Create a password and check Password never expires
Part5 Image52
  1. Confirm user and password options and click Finish
Part5 Image53
  1. Follow the same steps to create other users, View Composer, and Events database. Domain user is optional for now.
Part5 Image54
Juan Mulford
Juan Mulford
I have been active in IT for over fourteen years now. I am a solutions architect, working with storage, virtualization, and VDI solutions. For the past ten years, I have been living and working in Taiwan.

Leave a Reply

- Advertisement -

Popular Articles

mulcas.com-Raspberry-Pi

Raspberry Pi OS in a Virtual Machine with VMware

4
Although the Raspberry Pi OS is designed and optimized for the Raspberry Pi module, it is possible to test and use it without its hardware, with VMware. This solution can be useful if you are a developer (or just a curious guy) and don't have a Raspberry Pi module with you
Unable to delete inaccessible datastore

Unable to delete an "inaccessible" datastore

4
I was switching my storage array, so I migrated the VMs from that old datastore/storage to a new datastore/storage. The old datastore was shared by 3 ESXi hosts, no cluster. After migrating the VMs and unmount/delete the datastore, it was still presented in two of the ESXi hosts and was marked as inaccessible.
mulcas.com-VMware-OVF-Tool

How to export a Virtual Machine using the VMware OVF Tool

8
The VMware OVF Tool is implemented by VMware for easily importing and exporting virtual machines in Open Virtualization Format (OVF) standard format. Here, I want to show you how to download and install it, and then how to use it from a Windows machine.
This is not a valid source path / URL

This is not a valid source path / URL - SourceTree and Gitlab

0
I have been working on a project with a friend who set up a repository in Gitlab but even though I was able to view all projects on it, I couldn’t really join the repository. I was using SourceTree and Gitlab.
WinSCP VCSA

Unable to Access the VCSA 6.7 via WinSCP

9
One of the many and easiest ways to get the logs from the ESXi hosts and vCenter Server Appliance (VCSA), is accessing directly to the files directory using tools such as WinSCP, which helps to transfer the files between a local and a remote computer ( Ex. VCSA). I never have had issues with the ESXi hosts and WinSCP, however, trying to access the VCSA is a different story.
- Advertisement -

Recent Comments