This articles is part of the multi-part article, please read the previous stages here
In this article we will convert one of the virtual machines we created early as our primary active directory/DNS server for our virtual network.
Login to the windows azure portal and click on Virtual machines. From the list of virtual machines displayed, select QE-AD-DNS. We will attach an empty disk to the virtual machine to install some AD configuration. In order to do that. Click on “Add Disk” -> “Attach Empty Disk” from the bottom pane.
Leave everything default and enter 5 for the size and press the small tick. Once the disk is allocated, click “Connect” from the bottom pane. A RDP file with all the connection details will be downloaded, click to open it. Enter the password and click yes for couple of security warning and you’ll be logged in.
Once logged in the first thing we need to do is to initialize the disk we just attached to the virtual machine. Type “create and format hard disk partitions” in the start menu, and click on the disk management application, as soon as it’s opened it will automatically pop-in a window asking to initialize the disk as shown below
Click OK, and right-click on the disk and select “New Simple Partition” as shown below
Just click Next all the way through the wizard just leaving defaults, the disk will finally get initialized with a drive letter “F”.
In the start menu, type “dcpromo” and once the application shows up in the list, click to select. The application will take a while to initialize, as shown below,
and finally the “Active Directory Domain Installation Wizard” screen will appear as shown below. Carefully go through the steps outlined here.
Click Next, In the operating system compatibility screen (as shown below) click Next.
In the Choose Deployment configuration screen, select “create a new domain in a forest” option as shown in the below picture and click next.
In the “Name the forest root domain” screen enter a fully qualified name (FQDN) for your domain, (Note: There is no need to have b360.com domain, you can simply specify some random name here) as shown below
In the next screen, set the Forest Functional level to “Window Server 2008 R2” and click next
The wizard will check the DNS settings and it will take a while to initialize at this stage. Once initialized, you’ll see the DNS setting screen as shown below. It’s very important you select the “DNS Server”, check box, we want this single server to be our domain controller as well DNS server to resolve our server names.
Click next, which will bring the warning window as shown below, make sure you select the “not recommended” Yes option as shown below. Since we are not going to assign static IP addresses.
le=”ad 7″ border=”0″ alt=”ad 7″ src=”https://blogs.biztalk360.com/wp-content/uploads/b360/ad%207_thumb.png” width=”560″ height=”296″ />
Click Yes in the next warning screen as shown below.
In the next screen it will ask for the location to place the database, log files and SYSVOL information, change the default setting from C: to F: ( the disk we attached and initialized at the beginning of this article).
In the next screen enter the administrator password and confirm it and click next.
The summary page will be displayed, if you have done everything carefully so far, simply click on the next page.
The wizard will take a while to setup everything and finally shows a confirmation screen as shown below.
Click finish, which will ask you to restart the machine.
Our AD/DNS setting is ready now, leave few minutes for the server to come up. Go back to the Azure management portal and connect to our new AD machine QE-AD-DNS.
This time you can login with you domain credentials “CORPAdministrator” and your original password.
In the next stage article we will explain
how we can domain join all the virtual machines we have have create in the earlier articles.