Joining a Windows Server 2008 / 2008 R2 DC to a Samba AD
You can join Windows Server 2008 and 2008 R2 as an domain controller (DC) to a Samba Active Directory (AD).
If you want to join a computer running a Windows Server operating system as a domain member, see Joining a Windows Client or Server to a Domain.
- Click the
Startbutton, search for
View network connections, and open the search entry.
- Right-click to your network adapter and select
- Configure the IP settings:
- Assign a static IP address, enter the subnet mask, and default gateway.
- Enter the IP of a DNS server that is able to resolve the Active Directory (AD) DNS zone.
OKto save the settings.
Date and Time Settings
Active Directory uses Kerberos for authentication. Kerberos requires that the domain member and the domain controllers (DC) are having a synchronous time. If the difference exceeds 5 minutes (default), the client is not able to access domain resources for security reasons.
Before you join the domain, check the time configuration:
- Open the
- Navigrate to
Clock, Language and Region.
Date and Time.
- Verify the date, time, and time zone settings. Adjust the settings, if necessary.
OKto save the changes.
Joining the Windows Server to the Domain
- Windows Server automatically installs missing features, if necessary:
Use advanced mode installationto display additional options in later steps. Click
- Read the
Operating System Compatibilityinformation and click
Add a domain controller to an existing domain, and click
- Enter the Samba Active Directory (AD) domain name and credentials that are enabled to join a domain controller (DC) to the domain, such as the domain administrator account. Click
- Select the domain to join and click
- If AD sites are configured, select the site to join. Otherwise continue using the
- Select the options to enable on the new DC and click
- If you enabled the
DNS serveroption in the previous step, you may see a note, that a delegation for this DNS server cannot be created. Click
Replicate data over the network from an existing domain controllerand click
- Select a DC as source for the initial directory replication or let the installation wizard choose an appropriate DC. Click
- Set the folders for the AD database, log files and the Sysvol folder. Click
- Set a Directory Service Restore Mode Administrator Password (DSRM). It is required to boot the Windows DC in safe-mode to restore or repair the AD. Click
- Verify your settings and click
Nextto start the DC promotion.
- The wizard starts the installation, replicates the directory, and so on.
- Verify that all DC related DNS records have been created during the promotion. See Verifying and Creating a DC DNS Record.
Do not continue without verifying the DNS records. They must exist for a working directory replication!
- After the wizard completed click
- Restart the computer.
The Windows server now acts as an AD DC.
Verifying Directory Replication
|To optimize replication latency and cost, the knowledge consistency checker (KCC) on Windows DCs do not create a fully-meshed replication topology between all DCs. For further details, see The Samba KCC.|
During the join, Windows tries to replicate the Sysvol directory content from an existing domain controller (DC). Samba currently does not support the DFS-R protocol. For this reason, the new DC may not show a
Sysvol share. To enable the share:
- Save the following content to a plain text file named
Win-Create-Sysvol-Share.regusing a text editor such as "Notepad" or "Editor" (not Word/Wordpad/OpenOffice/LibreOffice/etc.):
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters] "SysvolReady"=dword:00000001
- Log in using an account that is member of the local
- Double-click the file to import it to the Windows registry.
- Reboot to take the changes effect.
Samba currently does not support the DFS-R protocol required for Sysvol replication. Please manually synchronise the content between domain controllers (DC) or use a workaround such as Robocopy-based Sysvol Replication.