Dns

Adding Windows Server 2012 DC in an existing Windows Server 2008 R2 DC

As part of the series of Windows Server 2012 deployment, I will be showing us how to promote a Windows Server 2012 member server into a domain controller in an existing Windows Server 2008 R2 domain. Lets begin the journey 🙂 Exciting. Requirements: – Ensure your Forest/Domain functional level is minimum Windows server 2003 – Ensure that you have an existing Windows Server 2008 R2 Domain Controller in place – Ensure you assign a static IP address to the server.

Assign a static IP Address to Windows Server 2012

This tutorial is about assign a static IP Address to windows server 2012 before proceeding with the installation of Windows Server 2012 Active Directory Services, we need to assign a static IP Address in preparation for the installation of the Active Directory Domain Services (AD DS). In this article it is assumed that you have already pre-installed Windows Server 2012. – Log onto your newly installed Windows Server 2012, locate the Network Internet Access icon, right-click on it and click “Open Network & Sharing Center” – Click on change adapter settings – Right-click on Ethernet and click properties – Select Internet Protocol Version 4 (TCP/IPv4) and click Properties – Select ‘Use the following IP address’, enter the IP address, subnet mask and gateway (if any).

Configure Active Directory DNS Server 2008R2

Active Directory DNS role by default was installed during the installation of Windows Server 2008 R2 Active Directory in my earlier post. DNS is comprised of two zones “Forward Lookup Zone – Resolves hostname to IP address” and “Reverse Lookup Zone – Resolves IP address to hostname”. In this post I will configure the Reverse Lookup Zone which isn’t configured by default. Requirements: Ensure Active Directory had been installed. Refer to this post

Installing Windows Server 2008 R2 Active Directory

The steps detailed below covers the installation process for building and configuring a Windows 2008 or 2008 R2 Active Directory and DNS implementation, and is a prerequisite for any Active Directory implementation as detailed in the Microsoft product service description. The diagram below shows how I have setup my AD network into separate network segments meaning we need to open up the AD ports. Requirements: 1. Ensure that the following services are started and set to Automatic start-up “DHCP Client” and “TCP/IP NetBIOS Helper“ 2.