Promoting Windows server 2008 via command line into a domain controller are pretty straight forward procedure. That is true for the first Domain Controller in the Forest. However, If you planning to deploy a second Domain Controller, which is best practice since the second DC provides redundancy for user account data and helps distribute the load for authentication and global catalog, there are some prerequisites you need to be aware of before you promote your server into a Domain Controller DC/AC which are not discuses in this post.

To initiate the Active Directory Installation Wizard (promoting Windows Server into a domain controller) you must be logged in with an Administrator account, then do the following:

1. Click Start ==> click Run ==> type DCPROMO, and then click OK.

2. On the Welcome page, click Next.

3. On the Operating System Compatibility page, click Next.

4. On the Choose a deployment Configuration page, select Create a new domain in a new forest , and then click Next.

5. On the Name the Forest Root Domain page, enter the fully qualified domain name. ie: nj180degree.net , or: nj180degree.local, or: sales.nj180degree.net or monkeysandit.local ..etc

6. On the Set Forest Functional level page, choose the appropriate functional level to your organization considering the following:

For Windows Server 2000 Functional level: The Windows 2000 forest functional level provides all Active Directory Domain Services features that are available in Windows 2000 Server. If you have domain controllers running later versions of Windows Server, some advanced features will not be available on those domain controllers while this forest is at the Windows 2000 functional level.The Windows 2000 forest functional level provides all Active Directory Domain Services features that are available in Windows 2000 Server. If you have domain controllers running later versions of Windows Server, some advanced features will not be available on those domain controllers while this forest is at the Windows 2000 functional level.

For Windows Server 2003 functional level: the Windows Server 2003 forest functional level provides all features that are available in Windows 2000 forest functional level, and the following additional features:
- Linked-value replication, which improves the replication of changes to group memberships.
- More efficient generation of complex replication topologies by the KCC.
- Forest trust, which allows organizations to easily share internal resources across multiple forests.
Note: If you decided to go with 2003 functional level you will be able to add ONLY Domain Controllers that are running Windows server 2003 or later to this forest. Any new domains that are created in this forest will automatically operate at the Windows Server 2003 domain functional level.

For Windows Server 2008 Functional level: This forest functional level does not provide any new features over the Windows 2003 forest functional level. However, it ensures that any new domains created in this forest will automatically operate at the Windows Server 2008 domain functional level, which does provide unique features.
Note: You will be able to add only domain controllers that are running Windows server 2008 or later to this forest.

Tip: Since the Windows Server 2008 Functional level doesn’t provide any new features over the Windows 2003 forest functional level, it is preffered to go with windows server 2003 functional level.

Click Next.

7. Set Domain Functional level page, this is quit similar to the Forest Functional level yet applied only to a domain level. Your options will be restricted depending on the Forest Functional level. ie: if you go with Windows 2008 functional level at the forest level you may have only one option at domain functional level which is Windows server 2008, So choose carefully then click Next.

8. On Additional Domain Controller Options you may notice that the box close to Global Catalog already ticked this is critical behavior because the first domain controller in a forest must be a global catalog server.

Tip: It is recommend that you install the DNS Server service on the first domain controller. If you do so make sure to assign a static IP to the Server. Alternatively you may install a DNS server on standalone server to act as a DNS Server.

9. On Location for Database, Log giles and SYSVOL page specify the folders that will contain the Active Directory domain controller database, lo files and SYSVOL. Click Next.

10. On Directory Services Restore Mode Administrator Password page, enter a strong password, confirm it then click Next.

11. On Summary page double chick our selection then click Next. Active directory domain service installation initiates right a way.

12. When complete, click Finish, and then click Restart Now to restart the server.

13. After the server restarts, log on using an account that is a member of the Domain Administrators group.

This starts the creation of the Windows Server 2003 domain controller
Share

Related posts:

  1. How to integrate Windows 7 to a domain using NETDOM
  2. Windows Server 2008 Hardware Requirements
  3. Installing IIS7 on Windows Vista/ Windows Server 2008
  4. Installing DNS server on a standalone or member server
  5. Windows activation problem – code 0x8007232B
  6. Configuring DNS Zones