Distribution-specific Package Installation: Difference between revisions

From SambaWiki
mNo edit summary
 
(19 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Introduction =
= Introduction =


The following is a distribution-specific list of commands to install Samba. There is a distinct difference between installing Samba, and provisioning/configuring of Samba. This page covers the installation-only, and is intended to be a short detour away from [[Setting_up_Samba_as_an_Active_Directory_Domain_Controller|Setting up Samba as an Active Directory Domain Controller]] page.
The following is a distribution-specific list of commands to install Samba.


Note, that the list of commands is neither provided nor actively verified by the Samba team. If you see any missing packages or incorrect package names, please update the command or send the information to the [https://lists.samba.org/mailman/listinfo/samba Samba mailing list].
Note, that the list of commands is neither provided nor actively verified by the Samba team. If you see any missing packages or incorrect package names, please update the command or send the information to the [https://lists.samba.org/mailman/listinfo/samba Samba mailing list].


As a reminder, the following information about the domain and domain controller applies to these examples:


* Hostname = <code>DC1</code>

* DC local IP Address = <code>10.99.0.1</code>
* Authentication Domain = <code>SAMDOM.EXAMPLE.COM</code>
* Top level Domain = <code>EXAMPLE.COM</code>




= Red Hat Enterprise Linux / CentOS / Scientific Linux =
= Red Hat Enterprise Linux / CentOS / Scientific Linux =


== Version 7 ==
== Version 7 and 8 ==


# yum install samba
# yum install samba


Because of the missing MIT Kerberos support in Samba, you can not use the Samba packages provided by Red Hat Enterprise Linux 7 as a Samba AD DC. As alternative:
The <code>samba</code> package only supports Samba as a domain member and NT4 PDC or BDC. Red Hat does not provide packages for running Samba as an AD DC. As an alternative:
* build Samba. For details, see [[Build_Samba_from_Source|Build Samba from Source]].
* Build Samba. For details, see [[Build_Samba_from_Source|Build Samba from Source]].
* use 3rd-party packages with AD support from a trusted source.
* Use 3rd-party packages with AD support from a trusted source.




== Version 6 ==
== Version 6 ==
Line 25: Line 27:
# yum install samba4
# yum install samba4


Because of the missing MIT Kerberos support in Samba, you can not use the Samba packages provided by Red Hat Enterprise Linux 7 as a Samba AD DC. As alternative:
The <code>samba4</code> package only supports Samba as a domain member and NT4 PDC or BDC. Red Hat does not provide packages for running Samba as an AD DC. As an alternative:
* build Samba. For details, see [[Build_Samba_from_Source|Build Samba from Source]].
* Build Samba. For details, see [[Build_Samba_from_Source|Build Samba from Source]].
* use 3rd-party packages with AD support from a trusted source.
* Use 3rd-party packages with AD support from a trusted source.






= Debian =
= Debian/Ubuntu =


# apt-get install samba acl attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user
# apt-get install acl attr samba winbind libpam-winbind libnss-winbind krb5-config krb5-user dnsutils python3-setproctitle


Note: For a DC you do not need libpam-winbind libnss-winbind libpam-krb5, unless you require AD users to login
* Note1: A DC only requires the libpam-winbind and libnss-winbind packages if your AD users will login to the DC.


* Note2: A samba DC usually serves as a domain NTP server, to do this you will also need to install an NTP server, either <code>ntp</code> or <code>chrony</code>. However is it not explicitly necessary for domain-joined machines to share a common NTP server, though it is best practice. If you do not wish to install and maintain an NTP server, you can define a Group Policy Object that synchronizes workstations with <code>time.windows.com</code> post installation. If you do want to install either package, they can be installed via:
= Ubuntu =


# apt-get install ntp
# apt-get install samba attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user


Or
Note: For a DC you do not need libpam-winbind libnss-winbind libpam-krb5, unless you require AD users to login

# apt-get install chrony

For details about time synchronization, see [[Time_Synchronisation|Time Synchronization]].




Line 49: Line 55:
# pkg install net/samba44
# pkg install net/samba44


Note: If you want to use the '''idmap_ad''' Winbind back end (on e.g. an AD Member Server), you have to build the port by hand and select the '''EXP_MODULES''' configuration option!
Note: If you want to use the <code>idmap_ad</code> Winbind back end (on e.g. an AD Member Server), you have to build the port by hand and select the '''EXP_MODULES''' configuration option!

= SUSE Linux Enterprise / openSUSE =

# zypper install samba samba-winbind samba-ad-dc

Latest revision as of 19:34, 29 March 2023

Introduction

The following is a distribution-specific list of commands to install Samba. There is a distinct difference between installing Samba, and provisioning/configuring of Samba. This page covers the installation-only, and is intended to be a short detour away from Setting up Samba as an Active Directory Domain Controller page.

Note, that the list of commands is neither provided nor actively verified by the Samba team. If you see any missing packages or incorrect package names, please update the command or send the information to the Samba mailing list.

As a reminder, the following information about the domain and domain controller applies to these examples:

  • Hostname = DC1
  • DC local IP Address = 10.99.0.1
  • Authentication Domain = SAMDOM.EXAMPLE.COM
  • Top level Domain = EXAMPLE.COM


Red Hat Enterprise Linux / CentOS / Scientific Linux

Version 7 and 8

# yum install samba

The samba package only supports Samba as a domain member and NT4 PDC or BDC. Red Hat does not provide packages for running Samba as an AD DC. As an alternative:

  • Build Samba. For details, see Build Samba from Source.
  • Use 3rd-party packages with AD support from a trusted source.

Version 6

# yum install samba4

The samba4 package only supports Samba as a domain member and NT4 PDC or BDC. Red Hat does not provide packages for running Samba as an AD DC. As an alternative:

  • Build Samba. For details, see Build Samba from Source.
  • Use 3rd-party packages with AD support from a trusted source.


Debian/Ubuntu

# apt-get install acl attr samba winbind libpam-winbind libnss-winbind krb5-config krb5-user dnsutils python3-setproctitle
  • Note1: A DC only requires the libpam-winbind and libnss-winbind packages if your AD users will login to the DC.
  • Note2: A samba DC usually serves as a domain NTP server, to do this you will also need to install an NTP server, either ntp or chrony. However is it not explicitly necessary for domain-joined machines to share a common NTP server, though it is best practice. If you do not wish to install and maintain an NTP server, you can define a Group Policy Object that synchronizes workstations with time.windows.com post installation. If you do want to install either package, they can be installed via:
# apt-get install ntp

Or

# apt-get install chrony

For details about time synchronization, see Time Synchronization.


FreeBSD

# pkg install net/samba44

Note: If you want to use the idmap_ad Winbind back end (on e.g. an AD Member Server), you have to build the port by hand and select the EXP_MODULES configuration option!

SUSE Linux Enterprise / openSUSE

# zypper install samba samba-winbind samba-ad-dc