Setting up Samba as an Active Directory Domain Controller: Difference between revisions
(624 intermediate revisions by 65 users not shown) | |||
Line 1: | Line 1: | ||
= |
= Introduction = |
||
tridge@samba.org, December 2004 |
|||
Starting from version 4.0 (released in 2012,) Samba is able to serve as an Active Directory (AD) domain controller (DC). Samba operates at the forest functional level of '''Windows Server 2008 R2''' which is more than sufficient to manage sophisticated enterprises that use Windows 10/11 with strict compliance requirements (including NIST 800-171.) |
|||
{{Imbox |
|||
This is a very basic document on how to setup a simple Samba4 |
|||
| type = note |
|||
server. This is aimed at developers who are already familiar with |
|||
| text = Starting with Samba version 4.19, Samba supports setting a higher functional level. This is still a work in progress so it should not be used in a production environment. For more information, see the Samba 4.19.0 release notes. |
|||
Samba3 and wish to participate in Samba4 development. This is not |
|||
}} |
|||
aimed at production use of Samba4. |
|||
If you are installing Samba in a production environment, it is recommended to run two or more DCs for failover reasons, more detail on the provisioning of a failover DC can be found elsewhere on the wiki. This documentation describes how to set up Samba as the first DC to build a new AD forest. Additionally, use this documentation if you are migrating a Samba NT4 domain to Samba AD. To join Samba as an additional DC to an existing AD forest, see [[Joining_a_Samba_DC_to_an_Existing_Active_Directory|Joining a Samba DC to an Existing Active Directory]]. |
|||
== Step 1: download Samba4 == |
|||
Samba as an AD DC only supports: |
|||
If you have downloaded the Samba4 code via a tarball released from the |
|||
* The integrated LDAP server as AD back end. For details, see the frequently asked question (FAQ) [[FAQ#Does_Samba_AD_DCs_Support_OpenLDAP_or_Other_LDAP_Servers_as_Back_End.3F|Does Samba AD DCs Support OpenLDAP or Other LDAP Servers as Back End?]] |
|||
samba.org website, Step 1 has already been completed for you. For testing |
|||
* The [http://www.h5l.se/ Heimdal] Kerberos Key Distribution Center (KDC). |
|||
with the version released in the tarball, you may continue on to Step 2. Note |
|||
: Samba provides experimental support for the [https://web.mit.edu/kerberos/ MIT Kerberos] KDC provided by your operating system if you run Samba 4.7 or later and has been built using the <code>--with-system-mitkrb5</code> option. In other cases Samba uses the Heimdal KDC included in Samba. For further details about Samba using the MIT KDC, and why it is experimental see [[Running a Samba AD DC with MIT Kerberos KDC]]. |
|||
that the references below to the top-level directory named "samba4" will |
|||
* Hosting and Administering of Group Policy Objects to be used for enterprise fleet management |
|||
instead be based on the name of the tarball downloaded (e.g. |
|||
: {{Imbox |
|||
"samba-4.0.0alpha3" for the tarball samba-4.0.0alpha3.tar.gz). |
|||
| type = important |
|||
| text = Installation of Samba and associated provisioning of a domain controller does not automatically translate into Group Policy functionality. Please keep this in mind, and expect to update this flag in the <code>smb.conf</code> post provisioning |
|||
}} |
|||
This tutorial assumes that this is a fresh installation of Samba on a fresh operating system installation. It is important to note that there is a distinction between installing of Samba and Provisioning of Samba. In general, the entire process of setting up a Samba domain controller consists of 5 steps which are relatively straight forward. These steps are as follows: |
|||
There are 2 methods of doing this: |
|||
# Installation of Samba and associated packages |
|||
* Via Rsync: "rsync -avz samba.org::ftp/unpacked/samba_4_0_test/ samba4" |
|||
# Deletion of pre-configured Samba and Kerberos placeholder configuration files |
|||
* Via Git: "git clone git://git.samba.org/samba.git samba4; cd samba4 && git checkout -b v4-0-test origin/v4-0-test; cd .." |
|||
# Provisioning of Samba using the automatic provisioning tool |
|||
# Editing of the <code>smb.conf</code> as needed (enabling of Group Policy and/or other features as needed) see [[Group_Policy|Group Policy]] for more information |
|||
# Any environmental configuration based on Unix/Linux Distribution |
|||
This page covers a lot of ground for Samba installations on both Unix and Linux systems. The installation process varies slightly based on environment, so expect to follow the linked web pages in multiple tabs throughout this read. For the remainder of this tutorial the following example information is used: |
|||
Both methods will create a directory called "samba4" in the current |
|||
directory. If you don't have rsync or git then install one of them. |
|||
* Hostname = <code>DC1</code> |
|||
Since only released versions of Samba contain a pre-generated configure script, |
|||
* DC local IP Address = <code>10.99.0.1</code> |
|||
you will have to generate it by hand: |
|||
* Authentication Domain = <code>SAMDOM.EXAMPLE.COM</code> |
|||
* Top level Domain = <code>EXAMPLE.COM</code> |
|||
= Preparing the Installation = |
|||
$ cd samba4/source |
|||
$ ./autogen.sh |
|||
==== Fresh Installation ==== |
|||
Note that the above rsync command will give you a checked out git |
|||
repository, but it's is missing all git objects. To turn it into |
|||
a working git repository you need to do the following steps: |
|||
$ cd samba4 |
|||
$ rm .git/objects/info/alternates |
|||
$ rm .git/refs/tags/* |
|||
$ rm -r .git/refs/remotes/ |
|||
$ git config remote.origin.url git://git.samba.org/samba.git |
|||
$ git config --add remote.origin.fetch +refs/tags/*:refs/tags/* (this line is optional) |
|||
$ git fetch |
|||
* Select a DNS domain for your AD forest. It is not recommended to use the top level domain for your organization. This is because the domain used during the installation of Samba will resolve to the domain controller. For Example: If your organization used <code>EXAMPLE.COM</code> as their domain and this was used during the Samba installation process, then the public facing website would no longer be accessible (assuming the publicly accessible website was not running on the DC, which it shouldn't!) It would be wise to define a subdomain for your Domain Controller to reside in. In this tutorial <code>SAMDOM.EXAMPLE.COM</code> is used, however in a lab environment it is not necessary to own a publicly accessible domain and <code>.INTERNAL</code> could hypothetically be used. The name will also be used as the AD Kerberos realm. |
|||
Note you can ignore this error from git fetch: |
|||
: {{Imbox |
|||
error: refs/heads/v4-0-test does not point to a valid object! |
|||
| type = important |
|||
| text = Make sure that you provision the AD using a DNS domain that will not need to be changed. Samba does not support renaming the AD DNS zone and Kerberos realm. Do not use <code>.local</code> for the TLD, this is used by Avahi. |
|||
}} |
|||
: For additional information, see [[Active_Directory_Naming_FAQ|Active Directory Naming FAQ]]. |
|||
* Select a host name for your AD DC which consists of less than 15 characters (netbios limitation.) A fantastic hostname is <code>DC1</code> |
|||
Also note that the git fetch will download the complete git history |
|||
: Do not use NT4-only terms as host name, such as <code>PDC</code> or <code>BDC</code>. These modes do not exist in an AD and cause confusion. |
|||
(about 160 MB with all the tags and about 125 MB without old tags). |
|||
* Set a static IP address on the DC and make the associated reservation on your router. '''Important:''' The Samba domain controller will become your DNS resolver for all domain-joined workstations. As a result it may be required to assign this IP address outside of your DHCP pool |
|||
You can update it to the latest version at some future date using: |
|||
* Disable tools, such as <code>resolvconf</code>, that automatically update your <code>/etc/resolv.conf</code> DNS resolver configuration file. AD DCs and domain members must use an DNS server that is able to resolve the AD DNS zones. (More information on this on the [[Distribution-specific_Package_Installation| Distribution Specific Package Installation]] page) |
|||
$ git pull |
|||
* Verify that the <code>/etc/hosts</code> file on the DC correctly resolves the fully-qualified domain name (FQDN) and short host name to the LAN IP address of the DC. For example: |
|||
== Step 2: compile Samba4 == |
|||
127.0.0.1 localhost |
|||
10.99.0.1 DC1.samdom.example.com DC1 |
|||
:The host name and FQDN must not resolve to the <code>127.0.0.1</code> IP address or any other IP address than the one used on the LAN interface of the DC. |
|||
* Remove any existing <code>smb.conf</code> file. To list the path to the file: |
|||
Recommended optional development libraries: |
|||
*acl and xattr development libraries (libattr1-dev package in Debian/Ubuntu) |
|||
*blkid development libraries (libblkid-dev package in Debian/Ubuntu) |
|||
*gnutls (libgnutls-dev package in Debian/Ubuntu) |
|||
*readline (libreadline5-dev package in Debian/Ubuntu) |
|||
*Python development libraries (python-dev in Debian/Ubuntu) required to compile |
|||
# smbd -b | grep "CONFIGFILE" |
|||
Run this: |
|||
CONFIGFILE: /usr/local/samba/etc/samba/smb.conf |
|||
==== Only Applicable if Samba was Previously Installed ==== |
|||
$ cd samba4/source |
|||
* If you previously ran a Samba installation on this host: |
|||
$ ./configure |
|||
: |
|||
$ make |
|||
:* Remove all Samba database files, such as <code>*.tdb</code> and <code>*.ldb</code> files. To list the folders containing Samba databases: |
|||
== Step 3: install Samba4 == |
|||
# smbd -b | egrep "LOCKDIR|STATEDIR|CACHEDIR|PRIVATE_DIR" |
|||
Run this as a user who have permission to write to the install |
|||
LOCKDIR: /usr/local/samba/var/lock/ |
|||
STATEDIR: /usr/local/samba/var/locks/ |
|||
configure above to change this. |
|||
CACHEDIR: /usr/local/samba/var/cache/ |
|||
PRIVATE_DIR: /usr/local/samba/private/ |
|||
# make install |
|||
: Starting with a clean environment helps to prevent confusion and ensures that no files from any previous Samba installation will be mixed with your new domain DC installation. |
|||
== Step 4: provision Samba4 == |
|||
= Installing Samba = |
|||
The "provision" step sets up a basic user database. |
|||
Must be run as a user with permission to write to the install directory. |
|||
# cd source |
|||
# ./setup/provision --realm=YOUR.REALM --domain=YOURDOM --adminpass=SOMEPASSWORD --server-role='domain controller' |
|||
{{:Installing_Samba}} |
|||
'YOURDOM' is the NT4 style domain name. 'YOUR.REALM' is your kerberos |
|||
realm, which is typically your DNS domain name. |
|||
== Step 5: Create a simple smb.conf == |
|||
The provisioning will create a very simple smb.conf with no shares by |
|||
default. You will need to update it to add at least one share. For |
|||
example: |
|||
= Provisioning a Samba Active Directory = |
|||
[test] |
|||
path = /data/test |
|||
read only = no |
|||
{{Imbox |
|||
| type = note |
|||
| text = The AD provisioning requires root permissions to create files and set permissions. |
|||
}} |
|||
The Samba AD provisioning process creates the AD databases and adds initial records, such as the domain administrator account and required DNS entries. Samba comes with a built in command lined tool called <code>samba-tool</code> which can be used to automatically configure your <code>smb.conf</code> when ran in interactive mode. |
|||
== Step 6: starting Samba4 == |
|||
If you are migrating a Samba NT4 domain to AD, skip this step and run the Samba classic upgrade. For details, see [[Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade)|Migrating a Samba NT4 Domain to Samba AD (Classic Upgrade)]]. |
|||
The simplest is to just run "smbd", but as a developer you may find |
|||
the following more useful: |
|||
# smbd -i -M single |
|||
The <code>samba-tool domain provision</code> command provides several parameters to use with the interactive and non-interactive setup. For details, see: |
|||
that means "start smbd without messages in stdout, and running a |
|||
single process. That mode of operation makes debugging smbd with gdb |
|||
particularly easy. |
|||
# samba-tool domain provision --help |
|||
Note that now it is no longer necessary to have an instance of nmbd |
|||
from Samba 3 running. If you are running any smbd or nmbd processes |
|||
they need to be stopped before starting smbd from Samba 4. |
|||
Make sure you put the bin and sbin directories from your new install |
|||
in your $PATH. Make sure you run the right version! |
|||
{{Imbox |
|||
| type = note |
|||
| text = When provisioning a new AD, it is recommended to enable the NIS extensions by passing the <code>--use-rfc2307</code> parameter to the <code>samba-tool domain provision</code> command. There are no disadvantages to enabling the NIS extensions, but enabling them in an existing domain requires manually extending the AD schema. For further details about Unix attributes in AD, see: |
|||
* [[Setting_up_RFC2307_in_AD|Setting up RFC2307 in AD]] |
|||
* [[Idmap_config_ad|idmap config = ad]] |
|||
}} |
|||
== Step 7: testing Samba4 == |
|||
try this command: |
|||
==== Parameter Reference ==== |
|||
$ smbclient //localhost/test -Uadministrator%SOMEPASSWORD |
|||
Set the following parameters during the provisioning: |
|||
{| class="wikitable" |
|||
== Step 8 (Optional): Configure Server-side DNS == |
|||
!Interactive Mode Setting |
|||
At this point, you can configure DNS on the Samba server to support dynamic update and to work correctly with Windows clients. First, install Bind9 (the 'bind9' package in Debian). |
|||
!Non-interactive Mode Parameter |
|||
Once that's installed, look in /usr/local/samba/private for two files. You'll see "YOUR.REALM.zone" and "named.conf". Copy *just* your.realm.zone to /etc/bind/ (or wherever you want to store zone files) and then take a look at named.conf in the local directory. You'll notice it's not actually a named.conf file, but a set of directions. The following directions are Debian-centric but you should be able to adapt them easily: |
|||
!Explanation |
|||
|- |
|||
|<code>--use-rfc2307</code> |
|||
|<code>--use-rfc2307</code> |
|||
|Enables the NIS extensions required for the ADUC Unix Attributes tab. |
|||
|- |
|||
|<code>Realm</code> |
|||
|<code>--realm</code> |
|||
|Kerberos realm. The uppercase version of the AD DNS domain. For example: <code>SAMDOM.EXAMPLE.COM</code>. |
|||
|- |
|||
|<code>Domain</code> |
|||
|<code>--domain</code> |
|||
|NetBIOS domain name (Workgroup). This can be anything, but it must be one word, not longer than 15 characters and not containing a dot. It is recommended to use the first part of the AD DNS domain. For example: <code>samdom</code>. Do not use the computers short hostname. |
|||
|- |
|||
|<code>Server Role</code> |
|||
|<code>--server-role</code> |
|||
|Installs the domain controller <code>DC</code> role. |
|||
|- |
|||
|<code>DNS backend</code> |
|||
|<code>--dns-backend</code> |
|||
|Sets the DNS back end. The first DC in an AD must be installed using a DNS back end. Note that the <code>BIND9_FLATFILE</code> is not supported and will be removed in a future Samba version. |
|||
|- |
|||
|<code>DNS forwarder IP address</code> |
|||
|not available |
|||
|This setting is only available when using the <code>SAMBA_INTERNAL</code> DNS back end. For details, see [[Samba_Internal_DNS_Back_End#Setting_up_a_DNS_Forwarder|Setting up a DNS Forwarder]]. |
|||
|- |
|||
|<code>Administrator password</code> |
|||
|<code>--adminpass</code> |
|||
|Sets the domain administrator password. If the password does not match the complexity requirements, the provisioning fails. For details, see [https://technet.microsoft.com/en-us/library/cc786468%28v=ws.10%29.aspx Microsoft TechNet: Passwords must meet complexity requirements]. |
|||
|} |
|||
Other parameters frequently used with the <code>samba-tool domain provision</code> command: |
|||
# Copy and paste the first portion of named.conf (the zone listing for your realm) into the real /etc/bind/named.conf. |
|||
* <code>--option="interfaces=lo eth0" --option="bind interfaces only=yes"</code>: If your server has multiple network interfaces, use these options to bind Samba to the specified interfaces. This enables the <code>samba-tool</code> command to register the correct LAN IP address in the directory during the join. |
|||
# You'll notice a lot of comments. Read those. If you have a version of bind that works (9.5.0 from Debian Unstable works) then you can also uncomment the "grant ..." line. |
|||
# About line 65, search for "tkey-gssapi" and add those two lines to /etc/bind/named.conf.options |
|||
# About line 78, add the "export KRB5_KTNAME ..." line to /etc/default/bind |
|||
# Run the two commands listed at the bottom of the file |
|||
# Extra Optionally: You can add reverse DNS entries and updating as per the example in the file. You'll also have to create the reverse zone in the bind config dir. |
|||
# Copy the krb5.conf file from /usr/local/samba/private/ to /etc |
|||
# Bind has to be able to update the journal files. The easiest, laziest, and worst way to do this is by 'chown -R bind.bind /etc/bind"; this is totally insecure, but since you're just testing that's okay...for the moment. The correct way to do it is to create the journal files by hand and change their ownership to bind.bind, OR put the journals in a seperate directory (like /var/bind/dynamic or something) and change it's ownership. |
|||
# Restart bind |
|||
# `tail -n 30 /var/log/daemon.log` and check for any errors regarding the zone files. You may have to do some tweaking. |
|||
Note: If you decide to test bind via something like `named -d 9999 -f -g`, remember to run the "EXPORT KRB5_KTNAME..." line beforehand, or it will fail with a GSS/"File Not Found" error. |
|||
# Assuming it's all up and working, test the DNS resolution. You should be able to do |
|||
`dig _ldap._tcp.dc._msdcs.your.realm SRV @localhost` And get something back. For instance, on mine: |
|||
samba4-alpha5:~# dig _ldap._tcp.dc._msdcs.samba5.local SRV @localhost |
|||
{{Imbox |
|||
<pre>; <<>> DiG 9.5.0 <<>> _ldap._tcp.dc._msdcs.samba5.local SRV @localhost |
|||
| type = important |
|||
;; global options: printcmd |
|||
| text = do NOT use <code>NONE</code> as the DNS backend, it is not supported and will be removed in a future Samba version. |
|||
;; Got answer: |
|||
}} |
|||
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1550 |
|||
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 |
|||
{{Imbox |
|||
;; QUESTION SECTION: |
|||
| type = important |
|||
;_ldap._tcp.dc._msdcs.samba5.local. IN SRV |
|||
| text = If using Bind as the DNS backend, do NOT use <code>BIND9_FLATFILE</code>, it is not supported and will be removed in a future Samba version. |
|||
}} |
|||
{{Imbox |
|||
;; ANSWER SECTION: |
|||
| type = important |
|||
_ldap._tcp.dc._msdcs.samba5.local. 604800 IN SRV 0 100 389 samba4-alpha5.samba5.local. |
|||
| text = Once you have provisioned the first DC in an AD domain, do not provision any further DCs in the same domain, [[Joining_a_Samba_DC_to_an_Existing_Active_Directory|Join]] any further DCs. |
|||
</pre> |
|||
}} |
|||
DNS should be set to go. Read on for joining workstations to the domain. |
|||
== NOTE about filesystem support == |
|||
== Provisioning Samba AD in Interactive Mode == |
|||
To use the advanced features of Samba4 you need a filesystem that |
|||
supports both the "user" and "system" xattr namespaces. |
|||
As mentioned above, when run as root, <code>samba-tool</code> will automatically configure your <code>smb.conf</code> to build a domain controller. Interactive Mode will not automatically enable Group Policy support. However this can be added in afterwards by manually editing <code>smb.conf</code>. |
|||
If you run Linux with a 2.6 kernel and ext3 this means you need to |
|||
include the option "user_xattr" in your /etc/fstab. For example: |
|||
{{Imbox |
|||
/dev/hda3 /home ext3 user_xattr 1 1 |
|||
| type = note |
|||
| text = When following the instructions below, it may be helpful to have the [[Group_Policy#Winbind|Group Policy]] page open in a separate browser tab or window. |
|||
}} |
|||
{{Imbox |
|||
You also need to compile your kernel with the XATTR and SECURITY |
|||
| type = warning |
|||
options for your filesystem. For ext3 that means you need: |
|||
| text = The installation of Samba will create a <code>smb.conf</code> file that must be discarded prior to running the Provisioning Tool in Interactive mode, or else it will fail. On most Linux distributions this can be done by running: |
|||
# mv /etc/samba/smb.conf /etc/samba/smb.conf.initial |
|||
}} |
|||
With the existing <code>smb.conf</code> file removed, provision a Samba AD interactively by running: |
|||
CONFIG_EXT3_FS_XATTR=y |
|||
CONFIG_EXT3_FS_SECURITY=y |
|||
# samba-tool domain provision --use-rfc2307 --interactive |
|||
If you are running a Linux 2.6 kernel with CONFIG_IKCONFIG_PROC |
|||
Realm [SAMDOM.EXAMPLE.COM]: SAMDOM.EXAMPLE.COM |
|||
defined you can check this with the following command: |
|||
Domain [SAMDOM]: SAMDOM |
|||
Server Role (dc, member, standalone) [dc]: dc |
|||
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: SAMBA_INTERNAL |
|||
DNS forwarder IP address (write 'none' to disable forwarding) [10.99.0.1]: 8.8.8.8 |
|||
Administrator password: Passw0rd |
|||
Retype password: Passw0rd |
|||
Looking up IPv4 addresses |
|||
Looking up IPv6 addresses |
|||
No IPv6 address will be assigned |
|||
Setting up share.ldb |
|||
Setting up secrets.ldb |
|||
Setting up the registry |
|||
Setting up the privileges database |
|||
Setting up idmap db |
|||
Setting up SAM db |
|||
Setting up sam.ldb partitions and settings |
|||
Setting up sam.ldb rootDSE |
|||
Pre-loading the Samba 4 and AD schema |
|||
Adding DomainDN: DC=samdom,DC=example,DC=com |
|||
Adding configuration container |
|||
Setting up sam.ldb schema |
|||
Setting up sam.ldb configuration data |
|||
Setting up display specifiers |
|||
Modifying display specifiers |
|||
Adding users container |
|||
Modifying users container |
|||
Adding computers container |
|||
Modifying computers container |
|||
Setting up sam.ldb data |
|||
Setting up well known security principals |
|||
Setting up sam.ldb users and groups |
|||
Setting up self join |
|||
Adding DNS accounts |
|||
Creating CN=MicrosoftDNS,CN=System,DC=samdom,DC=example,DC=com |
|||
Creating DomainDnsZones and ForestDnsZones partitions |
|||
Populating DomainDnsZones and ForestDnsZones partitions |
|||
Setting up sam.ldb rootDSE marking as synchronized |
|||
Fixing provision GUIDs |
|||
A Kerberos configuration suitable for Samba 4 has been generated at /usr/local/samba/private/krb5.conf |
|||
Setting up fake yp server settings |
|||
Once the above files are installed, your Samba4 server will be ready to use |
|||
Server Role: active directory domain controller |
|||
Hostname: DC1 |
|||
NetBIOS Domain: SAMDOM |
|||
DNS Domain: samdom.example.com |
|||
DOMAIN SID: S-1-5-21-2614513918-2685075268-614796884 |
|||
{{Imbox |
|||
$ zgrep CONFIG_EXT3_FS /proc/config.gz |
|||
| type = note |
|||
| text = The interactive provisioning mode supports passing further parameters to the <code>samba-tool domain provision</code> command. This enables you to modify parameters that are not part of the interactive setup. |
|||
}} |
|||
== Provisioning Samba AD in Non-interactive Mode == |
|||
If you don't have a filesystem with xattr support, then you can |
|||
simulate it by using the option: |
|||
For example, to provision a Samba AD non-interactively with the following settings: |
|||
posix:eadb = /usr/local/samba/eadb.tdb |
|||
* Server role: <code>dc</code> |
|||
* NIS extensions enabled |
|||
* Internal DNS back end |
|||
* Kerberos realm and AD DNS zone: <code>samdom.example.com</code> |
|||
* NetBIOS domain name: <code>SAMDOM</code> |
|||
* Domain administrator password: <code>Passw0rd</code> |
|||
# samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=SAMDOM.EXAMPLE.COM --domain=SAMDOM --adminpass=Passw0rd |
|||
that will place all extra file attributes (NT ACLs, DOS EAs, streams |
|||
etc), in that tdb. It is not efficient, and doesn't scale well, but at |
|||
least it gives you a choice when you don't have a modern filesystem. |
|||
=== Testing your filesystem === |
|||
To test your filesystem support, install the 'attr' package and run |
|||
the following 4 commands as root: |
|||
# touch test.txt |
|||
# setfattr -n user.test -v test test.txt |
|||
# setfattr -n security.test -v test2 test.txt |
|||
# getfattr -d test.txt |
|||
# getfattr -n security.test -d test.txt |
|||
You should see output like this: |
|||
= Setting up the AD DNS back end = |
|||
# file: test.txt |
|||
user.test="test" |
|||
Skip this step if you provisioned the DC using the <code>SAMBA_INTERNAL</code> DNS back end. |
|||
# file: test.txt |
|||
security.test="test2" |
|||
* Set up the BIND DNS server and the <code>BIND9_DLZ</code> module. For details, see [[Setting_up_a_BIND_DNS_Server|Setting up a BIND DNS Server]]. |
|||
If you get any "Operation not supported" errors then it means your |
|||
kernel is not configured correctly, or your filesystem is not mounted |
|||
with the right options. |
|||
* Start the BIND DNS server. For example: |
|||
If you get any "Operation not permitted" errors then it probably means |
|||
# systemctl start named |
|||
you didn't try the test as root. |
|||
: For details how to start services, see you distribution's documentation. |
|||
= Configure Windows XP Pro client to join Samba 4 Active Directory= |
|||
Active Directory is a powerful administration service which enables an administrator to centrally manage a network of Windows 2000, Windows XP Pro, Windows 2003, and Windows Vista Business Edition effectively. To test the real Samba 4 capability, we use Windows XP Pro as testing environment (Windows XP Home doesn't include Active Directory functionality and won't work). |
|||
To allow Samba 4 Active Directory or Microsoft Active Directory to manage a computer, we need to join the computer into the active directory. |
|||
It involves: |
|||
1. Configuring DNS Setting |
|||
2. Configuring date/time and time zone |
|||
3. Joining the domain |
|||
== Step 1: Configure DNS Setting for Windows XP Pro == |
|||
Before we configure the DNS setting, verify that you are able to ping the Server's IP Address. If you are not able to ping the server, double check your IP address, firewall, routing, etc. |
|||
= Configuring the DNS Resolver = |
|||
Once you have verified network connectivity between the Samba server and XP client, |
|||
1. Right Click My Network Places -> Properties |
|||
2. Double click local area network->Properties |
|||
3. Double click tcp/ip |
|||
4. Use static dns server, add the Samba 4 server's ip address inside the primary dns server column. [http://www.extraknowledge.org/xoops/images/samba/dnsclient.jpg Configure DNS Screen Shot] |
|||
5. Press ok, ok, ok again until finished. |
|||
6. Open a command prompt, type 'ping servername.your.realm' (change to suit your custom realm per your provision) |
|||
Domain members in an AD use DNS to locate services, such as LDAP and Kerberos. For that, they need to use a DNS server that is able to resolve the AD DNS zone. |
|||
If you get replies, then it means your Windows XP settings are correct (for DNS) and Samba4 Server's DNS services is working as well. |
|||
On your DC, set the AD DNS domain in the <code>search</code> and the IP of your DC in the <code>nameserver</code> parameter of the <code>/etc/resolv.conf</code> file. For example: |
|||
== Step 2: Configure date/time and time zone == |
|||
Active Directory uses Kerberos as the backend for authentication. Kerberos requires that the system clock on the client and server be synchronized to within a few seconds of each other. If they are not synchronized, authentication will fail for apparently no reason. |
|||
search samdom.example.com |
|||
1. Change the timezone in Windows XP Pro so that server and client using same time zone. In my computer, I use Asia/Kuala_Lumpur (I come from Malaysia).[http://www.extraknowledge.org/xoops/images/samba/timezone.jpg Changing Time Zone Screen Shoot] |
|||
nameserver 10.99.0.1 |
|||
2. Change the date/time so the client have same HH:MM with the server [http://www.extraknowledge.org/xoops/images/samba/time.jpg Changing Date/Time Screen Shoot] |
|||
== Step 3: Joining windows XP Pro into Domain == |
|||
Now your Windows XP Pro is ready to join the Active Directory (AD) domain, |
|||
As administrator:- |
|||
1. Right Click my Computer-> Properties |
|||
2. Choose Computer Name, click change.. |
|||
3. Click option 'Domain', insert YOUR.REALM (if you failed, try YOURDOM)([http://www.extraknowledge.org/xoops/images/samba/joindomain.jpg screen shoot]) |
|||
4. When it request username/password, type '''administrator''' as username, '''SOMEPASSWORD''' as password (per your earlier provision). |
|||
5. It will tell you the Windows XP has successfully join into Active Directory Domain, and you need to restart. |
|||
6. After restart, you should get the normal domain logon dialog |
|||
7. Choose domain YOURDOM, insert username '''administrator''' as username, '''SOMEPASSWORD''' as password (again, per your earlier provision) |
|||
8. If you login successfully, then you able to enjoy samba 4 active directory services at next section. |
|||
= Viewing Samba 4 Active Directory object from Windows XP Pro = |
|||
Due to Samba 4 SWAT is not yet ready for production, we need install windows 2003 adminpak into windows XP in order to manage the domain(It is user friendly). |
|||
Before begin, make sure the domain administrator have administrative right to control your computer.(To give any user administrative right, in Windows XP Pro, right click my computer, press manage-> choose groups-> doble click administrators and add members from domain into the member list. During you add member from active directory as member, it will prompt you to enter active directory username/password). |
|||
= Configuring Kerberos = |
|||
== Step 1: Installing Windows 2003 Administration Pack and support tools onto Windows XP Pro == |
|||
1. In Windows XP, download adminpak and supporttools from |
|||
In an AD, Kerberos is used to authenticate users, machines, and services. |
|||
http://www.microsoft.com/downloads/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&displaylang=en |
|||
http://download.microsoft.com/download/3/e/4/3e438f5e-24ef-4637-abd1-981341d349c7/WindowsServer2003-KB892777-SupportTools-x86-ENU.exe |
|||
During the provisioning, Samba created a Kerberos configuration file for your DC. Copy this file to your operating system's Kerberos configuration. For instance, if you built Samba yourself: |
|||
# cp /usr/local/samba/private/krb5.conf /etc/krb5.conf |
|||
Your <code>krb5.conf</code> path probably will be different, always use the path in the provision output. However, wherever Samba creates the <code>krb5.conf</code>, you need to copy it to <code>/etc/krb5.conf</code>. |
|||
{{Imbox |
|||
| type = important |
|||
| text = Do not create a symbolic link to the the generated <code>krb5.conf</code> file. In Samba 4.7 and later, the <code>/usr/local/samba/private/</code> directory is no longer accessible by other users than the <code>root</code> user. If the file is a symbolic link, other users are not able to read the file and, for example, dynamic DNS updates fail if you use the <code>BIND_DLZ</code> DNS back end. |
|||
}} |
|||
The pre-created Kerberos configuration uses DNS service (SRV) resource records to locate the KDC. |
|||
= Testing your Samba AD DC = |
|||
To start the <code>samba</code> service manually, enter: |
|||
# samba |
|||
Samba does not provide System V init scripts, <code>systemd</code>, <code>upstart</code>, or other services configuration files. |
|||
* If you installed Samba using packages, use the script or service configuration file included in the package to start Samba. |
|||
* If you built Samba, see [[Managing_the_Samba_AD_DC_Service|Managing the Samba AD DC Service]]. |
|||
= Create a reverse zone = |
|||
You can optionally add a reverse lookup zone. |
|||
# samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa -U Administrator |
|||
Password for [administrator@SAMDOM.EXAMPLE.COM]: |
|||
Zone 0.99.10.in-addr.arpa created successfully |
|||
If you need more than one reverse zone (multiple subnets), just run the above command again but with the data for the other subnet. |
|||
The reverse zone is directly live without restarting Samba or BIND. |
|||
{{Imbox |
|||
| type = note |
|||
| text = You must start the Samba AD DC before you can add a reverse zone. |
|||
}} |
|||
Now that you have created a reversezone, it would be a good time to create the <code>PTR</code> (reverse) dns record for the new DC. |
|||
For a DC with the FQDN of <code>dc1.samdom.example.com</code> and the ipaddress of <code>10.99.0.1</code>, to add a record to the <code>0.99.10.in-addr.arpa</code>, you would run a command like this: |
|||
# samba-tool dns add <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa 1 PTR dc1.samdom.example.com -U Administrator |
|||
Password for [administrator@SAMDOM.EXAMPLE.COM]: |
|||
Record added successfully |
|||
{{Imbox |
|||
| type = note |
|||
| text = The reverse records are not added automatically, you must add them manually, or set Windows computers to add them when updating their dns records. |
|||
}} |
|||
== Verifying the File Server (Optional)== |
|||
To list all shares provided by the DC: |
|||
Before Samba 4.11.0: |
|||
$ smbclient -L localhost -N |
|||
Anonymous login successful |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] |
|||
Sharename Type Comment |
|||
2. Run through the installation. |
|||
--------- ---- ------- |
|||
3. Press start->run, type 'dsa.msc', if a window 'active directory users and computers' prompt up, it mean you had install adminpak it successfully. You can also find this at Start>Programs>Administrative Tools, which should have a lot more items now. |
|||
netlogon Disk |
|||
4 Go to c:\Program Files\Support Tools to check whether the support tools were installed correctly; if yes, then your XP workstation is ready to manage the Samba 4 Active Directory. |
|||
sysvol Disk |
|||
IPC$ IPC IPC Service (Samba x.y.z) |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] |
|||
Server Comment |
|||
--------- ------- |
|||
Workgroup Master |
|||
--------- ------- |
|||
From Samba 4.11.0: |
|||
smbclient -L localhost -N |
|||
Anonymous login successful |
|||
Sharename Type Comment |
|||
--------- ---- ------- |
|||
sysvol Disk |
|||
netlogon Disk |
|||
IPC$ IPC IPC Service (Samba 4.12.6-Debian) |
|||
SMB1 disabled -- no workgroup available |
|||
{{Imbox |
|||
| type = note |
|||
| text = The <code>netlogon</code> and <code>sysvol</code> shares were auto-created during the provisioning and must exist on a DC. |
|||
}} |
|||
To verify authentication, connect to the <code>netlogon</code> share using the domain administrator account: |
|||
$ smbclient //localhost/netlogon -UAdministrator -c 'ls' |
|||
Enter Administrator's password: |
|||
Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] |
|||
. D 0 Tue Nov 1 08:40:00 2016 |
|||
.. D 0 Tue Nov 1 08:40:00 2016 |
|||
49386 blocks of size 524288. 42093 blocks available |
|||
If one or more tests fail, see [[#Troubleshooting|Troubleshooting]]. |
|||
== Verifying DNS (Optional)== |
|||
To verify that your AD DNS configuration works correctly, query some DNS records: |
|||
* The tcp-based <code>_ldap</code> SRV record in the domain: |
|||
$ host -t SRV _ldap._tcp.samdom.example.com. |
|||
_ldap._tcp.samdom.example.com has SRV record 0 100 389 dc1.samdom.example.com. |
|||
* The udp-based <code>_kerberos</code> SRV resource record in the domain: |
|||
$ host -t SRV _kerberos._udp.samdom.example.com. |
|||
_kerberos._udp.samdom.example.com has SRV record 0 100 88 dc1.samdom.example.com. |
|||
* The A record of the domain controller: |
|||
$ host -t A dc1.samdom.example.com. |
|||
dc1.samdom.example.com has address 10.99.0.1 |
|||
* If you have created a reverse zone, the PTR record of the domain controller: |
|||
$ host -t PTR 10.99.0.1 |
|||
1.0.99.10.in-addr.arpa domain name pointer dc1.samdom.example.com. |
|||
If one or more tests fail, see [[#Troubleshooting|Troubleshooting]]. |
|||
== Verifying Kerberos (Optional) == |
|||
This is not explicitly required, but it is a good idea to verify that your Domain Controller's authentication mechanisms are operating as intended. To test this, login by requesting a Kerberos ticket for the Domain Administrator account: |
|||
$ kinit administrator |
|||
Password for administrator@SAMDOM.EXAMPLE.COM: |
|||
: {{Imbox |
|||
| type = note |
|||
| text = If you do not pass the principal in the <code>user@REALM</code> format to the <code>kinit</code> command, the Kerberos realm is automatically appended.<br />Always enter the Kerberos realm in uppercase. |
|||
}} |
|||
* List the cached Kerberos tickets: |
|||
$ klist |
|||
Ticket cache: FILE:/tmp/krb5cc_0 |
|||
Default principal: administrator@SAMDOM.EXAMPLE.COM |
|||
Valid starting Expires Service principal |
|||
01.11.2016 08:45:00 12.11.2016 18:45:00 krbtgt/SAMDOM.EXAMPLE.COM@SAMDOM.EXAMPLE.COM |
|||
renew until 02.11.2016 08:44:59 |
|||
If one or more tests fail, see [[#Troubleshooting|Troubleshooting]]. |
|||
= Configuring Time Synchronization (Optional Depending on Use-Case)= |
|||
Kerberos requires synchronized time on all domain members. For further details and how to set up the <code>ntpd</code> or <code>chrony</code> service, see [[Time_Synchronisation|Time Synchronization]]. However if Samba is being used as a domain controller to administer Group Policy, it is possible to define a Group Policy Object that synchronizes workstations with <code>time.windows.com</code> post installation which simplifies this |
|||
= Using the Domain Controller as a File Server (Optional) = |
|||
{{Imbox |
|||
| type = warning |
|||
| text = Do not use an AD DC as a fileserver if you have multiple DC's. You should only use a DC as a fileserver, if it is the only Samba instance running in a domain. If you have multiple DC's, you should also set up Unix domain members and use them as fileservers. You should be aware that it is problematic to use a DC as a fileserver and can cause strange errors. |
|||
}} |
|||
== Step 2: Viewing samba 4 active directory content == |
|||
1. Login as domain 'testing1.org' administrator, press start->run. |
|||
2. type dsa.msc.[http://www.extraknowledge.org/xoops/images/samba/run.jpg Screen Shoot] |
|||
3 Expand the testing1.org tree to see existing object in domain. [http://www.extraknowledge.org/xoops/images/samba/dsa.msc.jpg Active Directory Screen Shoot] |
|||
While the Samba AD DC is able to provide file shares like all other installation modes, the Samba team does not recommend using a DC as a file server for the following reasons: |
|||
= Managing Samba 4 Active Directory From Windows XP Pro = |
|||
Due to Samba 4 Swat is not ready, managing samba 4 now is a little bit tricky. Most of the configuration we can done easily with active directory users and computers (dsa.msc), for adding a new users we need to use Windows 2003 support tools. |
|||
* For anything but the smallest organizations, having more than one DC is a really good backup measure, and makes upgrades safer |
|||
* It encourages upgrades of the DC to also be upgrades of the host OS every year or two, because there isn't complex data to transition or other services involved. |
|||
* This means upgrades can be done by installing fresh, and replicating in the changes, which is better tested in Samba, gains new features and avoids a number of lingering data corruption risks. |
|||
* The DC and file-server have different points at which an organization would wish to upgrade. The needs for new features on the DC and file server come at different times. Currently the AD DC is evolving rapidly to gain features, whereas the fileserver, after over 20 years, is quite rightly more conservative. |
|||
* mandatory smb signing is enforced on the DC. |
|||
== Step 1: Adding user into Samba 4 Active Directory == |
|||
Just as with Samba 3, version 4 needs an existing Unix user to map the Samba user to. Basically this task involve 3 jobs. |
|||
If you do decide to use the Samba DC as a fileserver, please consider running a VM, on the DC, containing a separate Samba Unix domain member and use this instead. |
|||
1. Add Unix User. In most Linux systems, you can use the ''useradd'' command. As root: |
|||
''useradd demo'' |
|||
''passwd demo'' (Will prompt for a new password) |
|||
(Debian/Ubuntu users tend to use the ''adduser'' script, which is an interactive script that handles both user addition and the password) |
|||
If you must use the Samba DC as a fileserver, you should be aware that the auto-enabled <code>acl_xattr</code> virtual file system (VFS) object enables you to only configure shares with Windows access control lists (ACL). Using POSIX ACLs with shares on a Samba DC does not work. |
|||
You should be aware that if wish to use a vfs object on a DC share e.g. recycle, you must not just set <code>vfs objects = recycle</code> in the share. Doing this will turn off the default vfs objects <code>dfs_samba4</code> and <code>acl_xattr</code>. You must set <code>vfs objects = dfs_samba4 acl_xattr recycle</code>. |
|||
NOTE: As of Alpha3, SWAT is '''disabled''' and you will not be able to add users through the web interface. If you are using Alpha3 (April 2008), or possibly later, step two here will not work. Instead, use Step 2B. |
|||
To provide network shares with the full capabilities of Samba, set up a Samba domain member with file shares. For details, see: |
|||
2. Using SWAT to add samba user. |
|||
* [[Setting_up_Samba_as_a_Domain_Member|Setting up Samba as a Domain Member]] |
|||
2.1 Open up mozilla-firefox |
|||
* [[Samba_File_Serving|Samba File Serving]] |
|||
2.2 open url http://samba-4-server-ip:901 |
|||
2.3 User = administrator, password = testing1, domain = testing,->Login. |
|||
2.4 click installation-> new user. |
|||
2.5 type username=demo, unix name = demo, password you like twice [http://www.extraknowledge.org/xoops/images/samba/swat-adduser.jpg Screen shot for add user using swat] |
|||
2b. Go into your Samba4 source tree ('''cd samba4/source''') and run '''./setup/newuser ''username'' ''' |
|||
If you only have a small domain (small office, home network) and do not want to follow the Samba team's recommendation and use the DC additionally as a file server, configure Winbindd before you start setting up shares. For details, see [[Configuring_Winbindd_on_a_Samba_AD_DC|Configuring Winbindd on a Samba AD DC]]. |
|||
Modify the user from Windows XP. |
|||
2.1 Start -> run -> dsa.msc |
|||
2.2 Open testing1.org tree, click container 'users'-> double click 'demo'. |
|||
2.3 Edit first name, lastname and username [http://www.extraknowledge.org/xoops/images/samba/dsa.msc-general.jpg Screen shoot for edit general user info with dsa.msc] |
|||
2.4 Go to account tab, fill in 'demo' in both username and logon name, choose domain (not the pre-win 2000) column.[http://www.extraknowledge.org/xoops/images/samba/dsa.msc-edituser.jpg Screen shot for edit user account] |
|||
2.5 set 'Password never expires' if you'd like. |
|||
2.6 Apply, then try to login with new user. |
|||
{{Imbox |
|||
If you able to login, then the user was successfully created. |
|||
| type = warning |
|||
| text = If you do use an AD DC as a fileserver, you must be aware that it can be problematic and can cause strange errors. |
|||
}} |
|||
{{Imbox |
|||
== Step 2: Adding groups into Samba 4 Active Directory == |
|||
| type = warning |
|||
To manage resource more effectively, we need to use groups. Same with users we need to have a unix group and samba groups. I haven't test whether the groups is working properly, but I guess more or less this method is correct(Please feed back if you found any error). |
|||
| text = If you do use an AD DC as a fileserver, do not add any of the 'idmap config' lines used on a Unix domain member. They will not work and will cause problems. |
|||
}} |
|||
{{Imbox |
|||
1. Creating Unix Groups |
|||
| type = warning |
|||
$sudo groupadd grpdemo |
|||
| text = If you do use an AD DC as a fileserver, You must set the permissions from Windows, do not attempt to use any of the old methods (force user etc) . They will not work correctly and will cause problems. |
|||
$sudo gedit /etc/group |
|||
}} |
|||
we can add user into group with following syntax:- |
|||
grpdemo:x:1007:demo, user1, user2 |
|||
= Troubleshooting = |
|||
2. Adding group into samba 4 active directory |
|||
2.1 As domain testing1.org administrator, start->run->dsa.msc. |
|||
2.2 Open tree testing1.org, right click 'users' container->new->groups |
|||
2.3 type group name 'grpdemo' in both column->ok (others leave default) |
|||
For further details, see [[Samba_AD_DC_Troubleshooting|Samba AD DC Troubleshooting]]. |
|||
3. Link the Unix groups to samba groups |
|||
3.1 Start mozilla-firefox (or IE), open url : http://samba-svr-ip:901 |
|||
3.2 Username=administrator, password = testing1, domain = testing1 |
|||
3.3 Choose preview of new swat-> modules -> LDB Browser |
|||
3.4 Open up sam.ldb tree, open up dc=testing1,dc=org, open cn=users |
|||
3.5 Click CN= grpdemo-> press modify button |
|||
3.6 At bottom most of right side, press '+' (Which is adding a new field) |
|||
3.7 Put field name(left text box) = 'unixName', data(right text box) = 'grpdemo' -> ok |
|||
= Adding organization unit (ou) into samba 4 domain = |
|||
Organizational Unit (ou), is a most powerful feature I found in active directory. Basically this is some kind of container which allow us to drag & drop users,computers into it. |
|||
we can link several kind of group policy (You can consider it is a graphical setting) to an ou, and the setting will deploy to all users/computers under the ou. With a single domain we can have many ou and sub ou. So the result is it greatly reduce administrative afford because we able to manage everything via ou. The implementation of group policy will discuss at next chapter. |
|||
Before we create an ou, we must know how ou look likes? By default we can see a sample ou 'Domain Controllers', it looks difference with 'users' and 'computers' container right? We can deploy group policy to users or computers container. |
|||
= Further Samba-related Documentation = |
|||
1. To create an ou, as testing1 domain administrator, start -> run -> dsa.msc |
|||
2. right click testing1.org. |
|||
3. choose new -? organizationalunit |
|||
4. type 'oudemo' |
|||
5. Then you will see an new ou appear, with the name 'oudemo'. |
|||
6. You can drag user 'demo' into the new ou (Don't move other users! Unless you want to get stuck!) |
|||
7. Right Click the 'oudemo', you can click sub ou with method 3. |
|||
See [[User_Documentation|User Documentation]]. |
|||
Normaly we create ou base on total department we have, what branch we have and etc. Don't confuse between groups and ou, groups use to control the permission, ou use for deploy setting to all users/computers under it. |
|||
= Implementing Group Policy (GPO) into samba 4 domain = |
|||
Recently Samba 4 Active Directory had support group policy, and we can create the group policy on the fly. The basic ideal of group policy is:- |
|||
1. Group Policy have 2 kind of settings, computers and users. |
|||
2. Computer setting apply to computer, user setting apply to user |
|||
3. We link the group policy to particular ou, and the group policy will effect all computers/users under the ou. |
|||
1. To add a group policy, right click 'oudemo' ou->properties |
|||
2. Choose group policy |
|||
3. Press new, name as 'gpoudemo' |
|||
4. Press edit to edit the policy. |
|||
5. Here will demonstrate how to block user from access the control panel. Open the tree 'User Configuration'->'control paner'. |
|||
6. Double click prohibit access to the control panel |
|||
7. Press enable and then press ok. Now the all users under 'oudemo' won't able to access the control panel. |
|||
8. Make sure user demo is inside the 'oudemo'(You can drag and drop it). |
|||
9. Logout and login as user 'demo' |
|||
10. You'll find user demo not able to access control panel |
|||
* User configuration will effect once we logout and login. |
|||
* Computer configuration will effect once restart computer |
|||
To learn more how to manage, implementing organizational unit, group policy, active directory. Google for Windows 2003 Active Directory implementation. |
|||
---- |
|||
Thanks for great efford samba development team, |
|||
[[Category:Domain Control]] |
|||
Good luck everybody |
|||
[[Category:Active Directory]] |
|||
End :) |
Latest revision as of 15:02, 8 May 2024
Introduction
Starting from version 4.0 (released in 2012,) Samba is able to serve as an Active Directory (AD) domain controller (DC). Samba operates at the forest functional level of Windows Server 2008 R2 which is more than sufficient to manage sophisticated enterprises that use Windows 10/11 with strict compliance requirements (including NIST 800-171.)
Starting with Samba version 4.19, Samba supports setting a higher functional level. This is still a work in progress so it should not be used in a production environment. For more information, see the Samba 4.19.0 release notes. |
If you are installing Samba in a production environment, it is recommended to run two or more DCs for failover reasons, more detail on the provisioning of a failover DC can be found elsewhere on the wiki. This documentation describes how to set up Samba as the first DC to build a new AD forest. Additionally, use this documentation if you are migrating a Samba NT4 domain to Samba AD. To join Samba as an additional DC to an existing AD forest, see Joining a Samba DC to an Existing Active Directory.
Samba as an AD DC only supports:
- The integrated LDAP server as AD back end. For details, see the frequently asked question (FAQ) Does Samba AD DCs Support OpenLDAP or Other LDAP Servers as Back End?
- The Heimdal Kerberos Key Distribution Center (KDC).
- Samba provides experimental support for the MIT Kerberos KDC provided by your operating system if you run Samba 4.7 or later and has been built using the
--with-system-mitkrb5
option. In other cases Samba uses the Heimdal KDC included in Samba. For further details about Samba using the MIT KDC, and why it is experimental see Running a Samba AD DC with MIT Kerberos KDC.
- Hosting and Administering of Group Policy Objects to be used for enterprise fleet management
Installation of Samba and associated provisioning of a domain controller does not automatically translate into Group Policy functionality. Please keep this in mind, and expect to update this flag in the smb.conf
post provisioning
This tutorial assumes that this is a fresh installation of Samba on a fresh operating system installation. It is important to note that there is a distinction between installing of Samba and Provisioning of Samba. In general, the entire process of setting up a Samba domain controller consists of 5 steps which are relatively straight forward. These steps are as follows:
- Installation of Samba and associated packages
- Deletion of pre-configured Samba and Kerberos placeholder configuration files
- Provisioning of Samba using the automatic provisioning tool
- Editing of the
smb.conf
as needed (enabling of Group Policy and/or other features as needed) see Group Policy for more information - Any environmental configuration based on Unix/Linux Distribution
This page covers a lot of ground for Samba installations on both Unix and Linux systems. The installation process varies slightly based on environment, so expect to follow the linked web pages in multiple tabs throughout this read. For the remainder of this tutorial the following example information is used:
- Hostname =
DC1
- DC local IP Address =
10.99.0.1
- Authentication Domain =
SAMDOM.EXAMPLE.COM
- Top level Domain =
EXAMPLE.COM
Preparing the Installation
Fresh Installation
- Select a DNS domain for your AD forest. It is not recommended to use the top level domain for your organization. This is because the domain used during the installation of Samba will resolve to the domain controller. For Example: If your organization used
EXAMPLE.COM
as their domain and this was used during the Samba installation process, then the public facing website would no longer be accessible (assuming the publicly accessible website was not running on the DC, which it shouldn't!) It would be wise to define a subdomain for your Domain Controller to reside in. In this tutorialSAMDOM.EXAMPLE.COM
is used, however in a lab environment it is not necessary to own a publicly accessible domain and.INTERNAL
could hypothetically be used. The name will also be used as the AD Kerberos realm.
Make sure that you provision the AD using a DNS domain that will not need to be changed. Samba does not support renaming the AD DNS zone and Kerberos realm. Do not use .local
for the TLD, this is used by Avahi.- For additional information, see Active Directory Naming FAQ.
- Select a host name for your AD DC which consists of less than 15 characters (netbios limitation.) A fantastic hostname is
DC1
- Do not use NT4-only terms as host name, such as
PDC
orBDC
. These modes do not exist in an AD and cause confusion.
- Set a static IP address on the DC and make the associated reservation on your router. Important: The Samba domain controller will become your DNS resolver for all domain-joined workstations. As a result it may be required to assign this IP address outside of your DHCP pool
- Disable tools, such as
resolvconf
, that automatically update your/etc/resolv.conf
DNS resolver configuration file. AD DCs and domain members must use an DNS server that is able to resolve the AD DNS zones. (More information on this on the Distribution Specific Package Installation page)
- Verify that the
/etc/hosts
file on the DC correctly resolves the fully-qualified domain name (FQDN) and short host name to the LAN IP address of the DC. For example:
127.0.0.1 localhost 10.99.0.1 DC1.samdom.example.com DC1
- The host name and FQDN must not resolve to the
127.0.0.1
IP address or any other IP address than the one used on the LAN interface of the DC.
- Remove any existing
smb.conf
file. To list the path to the file:
# smbd -b | grep "CONFIGFILE" CONFIGFILE: /usr/local/samba/etc/samba/smb.conf
Only Applicable if Samba was Previously Installed
- If you previously ran a Samba installation on this host:
- Remove all Samba database files, such as
*.tdb
and*.ldb
files. To list the folders containing Samba databases:
- Remove all Samba database files, such as
# smbd -b | egrep "LOCKDIR|STATEDIR|CACHEDIR|PRIVATE_DIR" LOCKDIR: /usr/local/samba/var/lock/ STATEDIR: /usr/local/samba/var/locks/ CACHEDIR: /usr/local/samba/var/cache/ PRIVATE_DIR: /usr/local/samba/private/
- Starting with a clean environment helps to prevent confusion and ensures that no files from any previous Samba installation will be mixed with your new domain DC installation.
Installing Samba
Install a maintained Samba version. For details, see Samba Release Planning. |
Provisioning a Samba Active Directory
The AD provisioning requires root permissions to create files and set permissions. |
The Samba AD provisioning process creates the AD databases and adds initial records, such as the domain administrator account and required DNS entries. Samba comes with a built in command lined tool called samba-tool
which can be used to automatically configure your smb.conf
when ran in interactive mode.
If you are migrating a Samba NT4 domain to AD, skip this step and run the Samba classic upgrade. For details, see Migrating a Samba NT4 Domain to Samba AD (Classic Upgrade).
The samba-tool domain provision
command provides several parameters to use with the interactive and non-interactive setup. For details, see:
# samba-tool domain provision --help
When provisioning a new AD, it is recommended to enable the NIS extensions by passing the --use-rfc2307 parameter to the samba-tool domain provision command. There are no disadvantages to enabling the NIS extensions, but enabling them in an existing domain requires manually extending the AD schema. For further details about Unix attributes in AD, see:
|
Parameter Reference
Set the following parameters during the provisioning:
Interactive Mode Setting | Non-interactive Mode Parameter | Explanation |
---|---|---|
--use-rfc2307
|
--use-rfc2307
|
Enables the NIS extensions required for the ADUC Unix Attributes tab. |
Realm
|
--realm
|
Kerberos realm. The uppercase version of the AD DNS domain. For example: SAMDOM.EXAMPLE.COM .
|
Domain
|
--domain
|
NetBIOS domain name (Workgroup). This can be anything, but it must be one word, not longer than 15 characters and not containing a dot. It is recommended to use the first part of the AD DNS domain. For example: samdom . Do not use the computers short hostname.
|
Server Role
|
--server-role
|
Installs the domain controller DC role.
|
DNS backend
|
--dns-backend
|
Sets the DNS back end. The first DC in an AD must be installed using a DNS back end. Note that the BIND9_FLATFILE is not supported and will be removed in a future Samba version.
|
DNS forwarder IP address
|
not available | This setting is only available when using the SAMBA_INTERNAL DNS back end. For details, see Setting up a DNS Forwarder.
|
Administrator password
|
--adminpass
|
Sets the domain administrator password. If the password does not match the complexity requirements, the provisioning fails. For details, see Microsoft TechNet: Passwords must meet complexity requirements. |
Other parameters frequently used with the samba-tool domain provision
command:
--option="interfaces=lo eth0" --option="bind interfaces only=yes"
: If your server has multiple network interfaces, use these options to bind Samba to the specified interfaces. This enables thesamba-tool
command to register the correct LAN IP address in the directory during the join.
do NOT use NONE as the DNS backend, it is not supported and will be removed in a future Samba version. |
If using Bind as the DNS backend, do NOT use BIND9_FLATFILE , it is not supported and will be removed in a future Samba version. |
Once you have provisioned the first DC in an AD domain, do not provision any further DCs in the same domain, Join any further DCs. |
Provisioning Samba AD in Interactive Mode
As mentioned above, when run as root, samba-tool
will automatically configure your smb.conf
to build a domain controller. Interactive Mode will not automatically enable Group Policy support. However this can be added in afterwards by manually editing smb.conf
.
When following the instructions below, it may be helpful to have the Group Policy page open in a separate browser tab or window. |
The installation of Samba will create a smb.conf file that must be discarded prior to running the Provisioning Tool in Interactive mode, or else it will fail. On most Linux distributions this can be done by running:
# mv /etc/samba/smb.conf /etc/samba/smb.conf.initial |
With the existing smb.conf
file removed, provision a Samba AD interactively by running:
# samba-tool domain provision --use-rfc2307 --interactive Realm [SAMDOM.EXAMPLE.COM]: SAMDOM.EXAMPLE.COM Domain [SAMDOM]: SAMDOM Server Role (dc, member, standalone) [dc]: dc DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: SAMBA_INTERNAL DNS forwarder IP address (write 'none' to disable forwarding) [10.99.0.1]: 8.8.8.8 Administrator password: Passw0rd Retype password: Passw0rd Looking up IPv4 addresses Looking up IPv6 addresses No IPv6 address will be assigned Setting up share.ldb Setting up secrets.ldb Setting up the registry Setting up the privileges database Setting up idmap db Setting up SAM db Setting up sam.ldb partitions and settings Setting up sam.ldb rootDSE Pre-loading the Samba 4 and AD schema Adding DomainDN: DC=samdom,DC=example,DC=com Adding configuration container Setting up sam.ldb schema Setting up sam.ldb configuration data Setting up display specifiers Modifying display specifiers Adding users container Modifying users container Adding computers container Modifying computers container Setting up sam.ldb data Setting up well known security principals Setting up sam.ldb users and groups Setting up self join Adding DNS accounts Creating CN=MicrosoftDNS,CN=System,DC=samdom,DC=example,DC=com Creating DomainDnsZones and ForestDnsZones partitions Populating DomainDnsZones and ForestDnsZones partitions Setting up sam.ldb rootDSE marking as synchronized Fixing provision GUIDs A Kerberos configuration suitable for Samba 4 has been generated at /usr/local/samba/private/krb5.conf Setting up fake yp server settings Once the above files are installed, your Samba4 server will be ready to use Server Role: active directory domain controller Hostname: DC1 NetBIOS Domain: SAMDOM DNS Domain: samdom.example.com DOMAIN SID: S-1-5-21-2614513918-2685075268-614796884
The interactive provisioning mode supports passing further parameters to the samba-tool domain provision command. This enables you to modify parameters that are not part of the interactive setup. |
Provisioning Samba AD in Non-interactive Mode
For example, to provision a Samba AD non-interactively with the following settings:
- Server role:
dc
- NIS extensions enabled
- Internal DNS back end
- Kerberos realm and AD DNS zone:
samdom.example.com
- NetBIOS domain name:
SAMDOM
- Domain administrator password:
Passw0rd
# samba-tool domain provision --server-role=dc --use-rfc2307 --dns-backend=SAMBA_INTERNAL --realm=SAMDOM.EXAMPLE.COM --domain=SAMDOM --adminpass=Passw0rd
Setting up the AD DNS back end
Skip this step if you provisioned the DC using the SAMBA_INTERNAL
DNS back end.
- Set up the BIND DNS server and the
BIND9_DLZ
module. For details, see Setting up a BIND DNS Server.
- Start the BIND DNS server. For example:
# systemctl start named
- For details how to start services, see you distribution's documentation.
Configuring the DNS Resolver
Domain members in an AD use DNS to locate services, such as LDAP and Kerberos. For that, they need to use a DNS server that is able to resolve the AD DNS zone.
On your DC, set the AD DNS domain in the search
and the IP of your DC in the nameserver
parameter of the /etc/resolv.conf
file. For example:
search samdom.example.com nameserver 10.99.0.1
Configuring Kerberos
In an AD, Kerberos is used to authenticate users, machines, and services.
During the provisioning, Samba created a Kerberos configuration file for your DC. Copy this file to your operating system's Kerberos configuration. For instance, if you built Samba yourself:
# cp /usr/local/samba/private/krb5.conf /etc/krb5.conf
Your krb5.conf
path probably will be different, always use the path in the provision output. However, wherever Samba creates the krb5.conf
, you need to copy it to /etc/krb5.conf
.
Do not create a symbolic link to the the generated krb5.conf file. In Samba 4.7 and later, the /usr/local/samba/private/ directory is no longer accessible by other users than the root user. If the file is a symbolic link, other users are not able to read the file and, for example, dynamic DNS updates fail if you use the BIND_DLZ DNS back end. |
The pre-created Kerberos configuration uses DNS service (SRV) resource records to locate the KDC.
Testing your Samba AD DC
To start the samba
service manually, enter:
# samba
Samba does not provide System V init scripts, systemd
, upstart
, or other services configuration files.
- If you installed Samba using packages, use the script or service configuration file included in the package to start Samba.
- If you built Samba, see Managing the Samba AD DC Service.
Create a reverse zone
You can optionally add a reverse lookup zone.
# samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa -U Administrator Password for [administrator@SAMDOM.EXAMPLE.COM]: Zone 0.99.10.in-addr.arpa created successfully
If you need more than one reverse zone (multiple subnets), just run the above command again but with the data for the other subnet.
The reverse zone is directly live without restarting Samba or BIND.
You must start the Samba AD DC before you can add a reverse zone. |
Now that you have created a reversezone, it would be a good time to create the PTR
(reverse) dns record for the new DC.
For a DC with the FQDN of dc1.samdom.example.com
and the ipaddress of 10.99.0.1
, to add a record to the 0.99.10.in-addr.arpa
, you would run a command like this:
# samba-tool dns add <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa 1 PTR dc1.samdom.example.com -U Administrator Password for [administrator@SAMDOM.EXAMPLE.COM]: Record added successfully
The reverse records are not added automatically, you must add them manually, or set Windows computers to add them when updating their dns records. |
Verifying the File Server (Optional)
To list all shares provided by the DC:
Before Samba 4.11.0:
$ smbclient -L localhost -N Anonymous login successful Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] Sharename Type Comment --------- ---- ------- netlogon Disk sysvol Disk IPC$ IPC IPC Service (Samba x.y.z) Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] Server Comment --------- ------- Workgroup Master --------- -------
From Samba 4.11.0:
smbclient -L localhost -N Anonymous login successful Sharename Type Comment --------- ---- ------- sysvol Disk netlogon Disk IPC$ IPC IPC Service (Samba 4.12.6-Debian) SMB1 disabled -- no workgroup available
The netlogon and sysvol shares were auto-created during the provisioning and must exist on a DC. |
To verify authentication, connect to the netlogon
share using the domain administrator account:
$ smbclient //localhost/netlogon -UAdministrator -c 'ls' Enter Administrator's password: Domain=[SAMDOM] OS=[Unix] Server=[Samba x.y.z] . D 0 Tue Nov 1 08:40:00 2016 .. D 0 Tue Nov 1 08:40:00 2016 49386 blocks of size 524288. 42093 blocks available
If one or more tests fail, see Troubleshooting.
Verifying DNS (Optional)
To verify that your AD DNS configuration works correctly, query some DNS records:
- The tcp-based
_ldap
SRV record in the domain:
$ host -t SRV _ldap._tcp.samdom.example.com. _ldap._tcp.samdom.example.com has SRV record 0 100 389 dc1.samdom.example.com.
- The udp-based
_kerberos
SRV resource record in the domain:
$ host -t SRV _kerberos._udp.samdom.example.com. _kerberos._udp.samdom.example.com has SRV record 0 100 88 dc1.samdom.example.com.
- The A record of the domain controller:
$ host -t A dc1.samdom.example.com. dc1.samdom.example.com has address 10.99.0.1
- If you have created a reverse zone, the PTR record of the domain controller:
$ host -t PTR 10.99.0.1 1.0.99.10.in-addr.arpa domain name pointer dc1.samdom.example.com.
If one or more tests fail, see Troubleshooting.
Verifying Kerberos (Optional)
This is not explicitly required, but it is a good idea to verify that your Domain Controller's authentication mechanisms are operating as intended. To test this, login by requesting a Kerberos ticket for the Domain Administrator account:
$ kinit administrator Password for administrator@SAMDOM.EXAMPLE.COM:
If you do not pass the principal in the user@REALM
format to thekinit
command, the Kerberos realm is automatically appended.
Always enter the Kerberos realm in uppercase.
- List the cached Kerberos tickets:
$ klist Ticket cache: FILE:/tmp/krb5cc_0 Default principal: administrator@SAMDOM.EXAMPLE.COM Valid starting Expires Service principal 01.11.2016 08:45:00 12.11.2016 18:45:00 krbtgt/SAMDOM.EXAMPLE.COM@SAMDOM.EXAMPLE.COM renew until 02.11.2016 08:44:59
If one or more tests fail, see Troubleshooting.
Configuring Time Synchronization (Optional Depending on Use-Case)
Kerberos requires synchronized time on all domain members. For further details and how to set up the ntpd
or chrony
service, see Time Synchronization. However if Samba is being used as a domain controller to administer Group Policy, it is possible to define a Group Policy Object that synchronizes workstations with time.windows.com
post installation which simplifies this
Using the Domain Controller as a File Server (Optional)
Do not use an AD DC as a fileserver if you have multiple DC's. You should only use a DC as a fileserver, if it is the only Samba instance running in a domain. If you have multiple DC's, you should also set up Unix domain members and use them as fileservers. You should be aware that it is problematic to use a DC as a fileserver and can cause strange errors. |
While the Samba AD DC is able to provide file shares like all other installation modes, the Samba team does not recommend using a DC as a file server for the following reasons:
- For anything but the smallest organizations, having more than one DC is a really good backup measure, and makes upgrades safer
- It encourages upgrades of the DC to also be upgrades of the host OS every year or two, because there isn't complex data to transition or other services involved.
- This means upgrades can be done by installing fresh, and replicating in the changes, which is better tested in Samba, gains new features and avoids a number of lingering data corruption risks.
- The DC and file-server have different points at which an organization would wish to upgrade. The needs for new features on the DC and file server come at different times. Currently the AD DC is evolving rapidly to gain features, whereas the fileserver, after over 20 years, is quite rightly more conservative.
- mandatory smb signing is enforced on the DC.
If you do decide to use the Samba DC as a fileserver, please consider running a VM, on the DC, containing a separate Samba Unix domain member and use this instead.
If you must use the Samba DC as a fileserver, you should be aware that the auto-enabled acl_xattr
virtual file system (VFS) object enables you to only configure shares with Windows access control lists (ACL). Using POSIX ACLs with shares on a Samba DC does not work.
You should be aware that if wish to use a vfs object on a DC share e.g. recycle, you must not just set vfs objects = recycle
in the share. Doing this will turn off the default vfs objects dfs_samba4
and acl_xattr
. You must set vfs objects = dfs_samba4 acl_xattr recycle
.
To provide network shares with the full capabilities of Samba, set up a Samba domain member with file shares. For details, see:
If you only have a small domain (small office, home network) and do not want to follow the Samba team's recommendation and use the DC additionally as a file server, configure Winbindd before you start setting up shares. For details, see Configuring Winbindd on a Samba AD DC.
If you do use an AD DC as a fileserver, you must be aware that it can be problematic and can cause strange errors. |
If you do use an AD DC as a fileserver, do not add any of the 'idmap config' lines used on a Unix domain member. They will not work and will cause problems. |
If you do use an AD DC as a fileserver, You must set the permissions from Windows, do not attempt to use any of the old methods (force user etc) . They will not work correctly and will cause problems. |
Troubleshooting
For further details, see Samba AD DC Troubleshooting.
See User Documentation.