Posts Tagged ‘AD DS’

How to: Windows 2012 Server deploy remote domain controllers using Server Manager – part II of II

A few weeks ago I’ve posted an article about how to remotely Install a domain controller within Windows 2012 Server using the Server Manager.

How to: Windows 2012 Server Deploy remote domain controllers using Server Manager – Part I of II

Since Windows 2012 Server, creating a new domain controller is much eassier then ever before. There is another option to create a new domain controller….Yes, using Windows PowerShell!!

As you can see in part I of the post, there are two domain controllers. I have installed a clean Windows 2012 Server within my labenvironment, called Server2.

1.) Logon to Server1 with the Administrator account
2.) Open Windows PowerShell
3.) Type the following command:
Install-WindowsFeature -Name AD-Domain-Services -ComputerName Server2
4.) After the Windows feature is installed succesfully, type the following command:
Invoke-Command –ComputerName Server2 –ScriptBlock {Import-Module ADDSDeployment;Install-ADDSDomainController –NoGlobalCatalog:$False –CreateDNSDelegation:$False –Credential (Get-Credential) –CriticalReplicationOnly:$False –DatabasePath “C:\Windows\NTDS” –DomainName “” –InstallDNS:$True –LogPath “C:\Windows\NTDS” –NoRebootOnCompletion:$False –SiteName “Default-First-Site-Name” –SysVolPath “C:\Windows\SysVol” }
When prompted for credentials, enter the username and password of your domain administrator account!

In my labenvironment, I have used the following parameters:
-ComputerName, this is the name of the new domain controller
-NoGlobalCatalog:$False, the new domain controller becomes also an Global Catalog Server
-CreateNDSDelegation:$False, there are no ohter DNS servers available for DNS delegation
-Creadential(Get-Credential), before executing the command, there will be an popup asking your admin crerdentials
-CriticalReplicationOnly:$False, this entry specifies whether the installation operation performs only important replication before a restart and then skips the noncritical and potentially lengthy part of replication. The noncritical replication occurs after the role installation is complete, and the computer restarts
-Databasepath, the location of the ADDS database (NTDS.DIT)
-DomainName, specifies the fully qualified domain name of your domain
-InstallDNS:$True, the new domain controllers becomes also an DNS server
-LogPath, this is the path of the fully qualified, non-UNC directory on a hard disk on the local computer that will  host the AD DS log files.
-NoRebootOnCompletion:$False, there will be no reboot at the end of the installation
-SiteName, this is the name of your Active Directory site where the new domain controller becomes a member of
-SysVolPath, this folder contains all content replicated to the other domain controller (NETLOGON and SYSVOL directories)
5.) After executing the commands above, and the installation has finished, the new domain controller becomes vissible in your Active Directory environment
6.) All you have to do now is waiting for the next Active Directory replication, so all your domain controllers are synchronized





How to: Install a domain controller in Windows Server 2012

Now the Release Candidate version of Windows Server 2012 is available, I’ve setup a new testlab to play with this new version of Windows. A few posts ago you’ve seen the installation of Windows Server 2012. Now we’re going to prepare this server to become a domain controller. The simple command “DCPROMO” don’t work anymore, so we’ve to do some additional actions.

1.) Open the Server Manager and select Add roles and features
2.) Select Role-based or features-based installation
3.) Select the right server, in my example W2012 (
4.) Select the roles Active Directory Domian Services and DNS Server
5.) Select the features Group Policiy Management and DNS Server Tools
6.) After the installation of this roles and features, there’s a notification within the Server Manager Dashboard
7.) Select Promote this server to a domain controller. A Deployment Configuration Wizard starts
8.) Select Add a new forest and fill in the Root domain name. In my example TESTLAB.LOCAL
9.) Both Forest and Domain functional level are Windows Server 2012 Release Candidate
10.) If the domain controller is also an DNS Server, check the Domain Name System (DNS) server
11.) The domain controllers becomes also an Global Catalog (GC)
12.) You could choose to install an Read only domain controller (RODC)
13.) Fill in the NetBIOS name of the new domain. In my example TESTLAB
14.) Specify the location of the AD DS database, log files, and SYSVOL directory. Default it will be
C:\Windows\NTDS and C:\Windows\SYSVOL
15.) After all configuration, there’s a last prerequisites check. After this step, you can hit Install
16.) The server will reboot and the new Domain Controller is ready to use.

You can script all the steps above with powershell. You can use the following script.

# Windows PowerShell script for AD DS Deployment

Import-Module ADDSDeployment Install-ADDSForest ` -CreateDnsDelegation:$false ` -DatabasePath “C:\Windows\NTDS” ` -DomainMode “Win2012” ` -DomainName “TESTLAB.LOCAL” ` -DomainNetbiosName “TESTLAB” ` -ForestMode “Win2012” ` -InstallDns:$true ` -LogPath “C:\Windows\NTDS” ` -NoRebootOnCompletion:$false ` -SysvolPath “C:\Windows\SYSVOL” ` -Force:$true