Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 Network

7/22/2019 Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 Network

1/12

PREPARED BY RAVI KUMAR LANKE Page 1

Adding a Windows Server2012 Domain Controller to anExisting Windows Server 2003network

Prerequisites

1.Download Windows Server 2012.If you plan on completing this Step-By-Step ina virtual lab, it is recommended todownload the FREE Hyper-V Server 2012 first.

2. Check to ensure the Domain Functional Level is currently setup to atleast Windows 2003 mode. This is the lowest required Domain FunctionalLevel that would allow a Windows Server 2012 Domain Controller installation.Windows NT / 2000 Domain Controllers are not supported via this process.

a. Via theActive Directory Users and Computers console, select thedomain via the right mouse button on it.

b. Select Raise Domain Functional Level and review the Currentdomain functional levelreported
http://aka.ms/WS2012ABhttp://aka.ms/WS2012ABhttp://aka.ms/HV2012ABhttp://aka.ms/HV2012ABhttp://aka.ms/HV2012ABhttp://aka.ms/HV2012ABhttp://aka.ms/WS2012AB


2/12


The Domain Functional Level does not need to be raised if the Currentdomain functional level is reporting Windows Server 2003.

NOTE: Should a lower domain be showcased (i.e., Windows Server2000), please keep in mind that raising Domain Functional Level is a one

time action and cannot be reverted. Remember Windows NT / 2000Domain Controllers are not supported via this process.

c. Ensure your profile is a member of the Enterprise Admins group.Getting Started

1. Setup and install your Windows Server 2012 machine2. Configure the new server's IP address to correspond to the target domain and

ensure the existing Domain Controllers, where DNS is installed and configured,

are visible by your new Windows Server 2012 install.

Setting Up Domain Controller Fuctionality
http://aka.ms/WS2012ABhttp://aka.ms/WS2012ABhttp://aka.ms/WS2012ABhttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6052.Add2012DCto2003a.pnghttp://aka.ms/WS2012ABhttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6052.Add2012DCto2003a.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6052.Add2012DCto2003a.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6052.Add2012DCto2003a.png


3/12


1. Open the Server Manager console and click onAdd roles and features

2. Select Role-based of featured-based installation and select Next.
http://blogs.technet.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/0486.DCHP0312b.png


4/12


3. Select theActive Directory Directory Services role.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/5857.Add2012DCto2003b.pnghttp://blogs.technet.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/8814.DCHP0312c.pnghttp://blogs.technet.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/8814.DCHP0312c.png


5/12


4. Accept the default features required by clicking theAdd Features button.

5. On the Features screen click the Next button.6. On the Confirm installation selections screen click the Install button.

NOTE: Check off the Restart the destination server automatically ifrequired box to expedite the install should you be able to reset the target

server automatically.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/4263.Add2012DCto2003c.png


6/12


7. Click the Close button once the installation has been completed.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/5228.Add2012DCto2003f.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6505.Add2012DCto2003e.png


7/12


8. Once completed, notification is made available on the dashboard highlighted by an exclamation mark. Selectit and amidst the drop down menu select Promote this server to a domain controller.

9. Select add a Domain Controller into existing domain

10. Ensure the target domain is specified. If it is not, please either Select theproper domain or enter the proper domain in the field provided.

11. ClickChange, provide the required Enterprise Administrator credentials and clickthe Next button.

12. Define if server should be a Domain Name System DNS server and GlobalCatalog (GC). Select the Site to which this DC belongs to and define DirectoryServices Restoration Mode (DSRM)password for this DC
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/5466.Add2012DCto2003h.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/3441.Add2012DCto2003g.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/5466.Add2012DCto2003h.png


8/12


13. Click the Next button on the DNS options screen.14. In theAdditional Options screen you are provided with the option to install the

Domain Controller from Install From Media (IFM).Additionally you areprovided the option to select the point from which DC replication should be

completed. The server will choose the best location for AD database replication ifnot specified. Click the Next button once completed.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/2620.Add2012DCto2003i.png


9/12


15. Specify location for AD database and SYSVOL and Click the Next button.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/3618.Add2012DCto2003k.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/7888.Add2012DCto2003j.png


10/12


16. Next up is the Schema and Domain preparation. Alternately, one couldrunAdprepprior to commencing these steps, Regardless, if Adprep is notdetected, it will automatically be completed on your behalf.

17. Finally, the Review Options screen provides a summary of all of the selectedoptions for server promotion. As an added bonus, when clickingViewScript button you are provided with the PowerShell script to automate futureinstallations. To click the Next button to continue.
http://technet.microsoft.com/en-us/library/cc731728(v=ws.10).aspxhttp://technet.microsoft.com/en-us/library/cc731728(v=ws.10).aspxhttp://technet.microsoft.com/en-us/library/cc731728(v=ws.10).aspxhttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6052.Add2012DCto2003l.pnghttp://technet.microsoft.com/en-us/library/cc731728(v=ws.10).aspx


11/12


18. Should all the prerequisites pass, click the Install button to start the installation.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/3630.Add2012DCto2003n.pnghttp://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/3124.Add2012DCto2003m.png


12/12


19.After it completes the required tasks and the server restarts, the new WindowsServer 2012 Domain Controller setup is completed.

20. Lastly, on each server/workstation within the target domain require aNIC properties configuration update to point to the new Domain Controller. Openthe DHCP management console, select Option no. 006 and under

server/scope options and add the IP address of your new Domain Controller asDNS server.
http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-48-12/6443.Add2012DCto2003o.png

Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 Network

Documents

Transcript of Adding a Windows Server 2012 Domain Controller to an Existing Windows Server 2003 Network