Windows and Linux Integration Series, part 1. This part compares the main approaches and helps you pick one before you join the first host. Later parts cover DNS and time, POSIX attributes in Active Directory, joining AlmaLinux and the other RHEL derivatives with realmd and SSSD or with Winbind, sudo and automount from AD, kerberized NFS, Samba as a file and print server, and joining Solaris 10 and 11.
Most shops that run Windows and Linux together already have Active Directory. Users already have accounts there, file servers already grant access by AD group, and nobody wants a second password just to log in to a Linux box. This series is about that coexistence: joining Red Hat Enterprise Linux and its derivatives, and Solaris, to the AD you already run, then using that same identity for SSH, sudo, automount, Samba shares, printers and Kerberized NFS.
It is not a guide to replacing Active Directory with OpenLDAP and a standalone MIT Kerberos KDC. Those tools are the right target when you are ready to leave AD, and they show up later in this series only as a hybrid option (a trust or a side-by-side realm). Until then, AD remains the identity source and the KDC.
The rest of this post is a decision guide. You will see the recommended client stacks, an honest comparison, the ID-mapping choice that has to be made early, a lab layout used for the rest of the series, the commands that discover and join a domain, and the checks that tell you the join actually worked. Each later post goes deep on one topic.
Applies to: AlmaLinux 10, Red Hat Enterprise Linux 10, Rocky Linux 10 and Oracle Linux 10, joined to Windows Server 2019, 2022 or 2025 domain controllers. The same realmd and SSSD (or Winbind) flow is the documented path on RHEL 8 and 9, with package and option differences noted in later posts. Solaris coverage in this series is Oracle Solaris 11.4 and Solaris 10. Commands and option meanings below were checked against Red Hat’s RHEL 10 guide Integrating RHEL systems directly with Windows Active Directory, chapter 6 of Planning Identity Management, Red Hat’s Using Samba as a server, Microsoft’s guidance on Identity Management for UNIX after Windows Server 2016, and Oracle’s Solaris 11.4 Kerberos and LDAP documentation.
Lab layout used in this series
Examples use the DNS domain corp.example.com and the Kerberos realm CORP.EXAMPLE.COM. Substitute your own AD DNS name; the realm is almost always the domain in upper case. Do not mix this lab with the example.lan OpenLDAP lab from the OpenLDAP series unless you have deliberately built a trust between them.
| Host | IP | Role |
|---|---|---|
dc1.corp.example.com | 192.168.10.10 | Windows Server 2022/2025 domain controller, DNS, KDC |
dc2.corp.example.com | 192.168.10.11 | Second DC / DNS / KDC |
rhel1.corp.example.com | 192.168.10.20 | AlmaLinux 10 test join (realmd + SSSD) |
files1.corp.example.com | 192.168.10.21 | AlmaLinux 10 Samba file and print member (Winbind) |
nfs1.corp.example.com | 192.168.10.22 | AlmaLinux 10 NFS server using AD Kerberos |
sol11.corp.example.com | 192.168.10.30 | Oracle Solaris 11.4 |
sol10.corp.example.com | 192.168.10.31 | Solaris 10 |
Every Linux and Solaris host in this lab must use the AD DNS servers, must have a correct A and PTR record (or a name that matches what you join), and must keep time within a few minutes of the domain controllers. Kerberos fails in ways that look like a bad password when the clock is wrong. Part 2 covers DNS, chrony and the port list in detail. The short version is: if realm discover corp.example.com cannot find the domain, fix DNS before you touch sssd.conf.
What you are deciding
Direct integration means the Unix host is a computer in the AD domain. It has a machine account, a keytab, and it asks a DC for users, groups and tickets. Users log in with their AD credentials. There is no intermediate FreeIPA or OpenLDAP server required.
You still have several choices, and mixing them carelessly is how you end up with one UID on the login server and a different UID on the file server:
- Which client stack talks to AD: SSSD (usually enrolled with realmd and adcli) or Samba Winbind.
- Where POSIX UIDs and GIDs come from: computed from the AD SID, or read from RFC2307 attributes stored in AD (
uidNumber,gidNumberand friends). - What the host is for: a login or application server, a Samba file or print server, an NFS server, or a Solaris box. The right stack is not the same for all of those.
- How far you centralize policy: local
sudoersand autofs maps, or schema extensions in AD so sudo rules and automount maps live next to the user objects.
Red Hat’s current recommendation, as of RHEL 10, is clear and this series follows it. Use SSSD for most AD-joined RHEL systems. Use Winbind on members that will run Samba as a file or print server. Red Hat supports Samba in the domain-member server role only with winbindd, not with SSSD, because SSSD does not provide the Windows ACL and NTLM fallback behavior Samba needs in that role. You can still use SSSD on all of the ordinary login hosts, and Winbind only on files1, as long as both sides agree on how UIDs are assigned.
The ID mapping choice (make this first)
Windows identifies accounts by SID. Linux and Solaris identify them by UID and GID. Something has to translate. This translation has to be stable: the same person must get the same UID on every Unix host that shares files, or NFS and local POSIX permissions will not mean what you think they mean.
Option A: algorithmic (automatic) ID mapping
SSSD’s default for an AD domain is to compute a UID and GID from the SID (ldap_id_mapping = true). When SSSD first sees a domain it assigns that domain an ID range. The algorithm is stable, so a given SID becomes the same UID on every SSSD client that uses the same mapping. You do not have to populate Unix attributes in AD, and new users work as soon as they exist in the directory.
The limitation is that the numbers only line up with software that uses the same algorithm. Winbind with a rid or autorid backend will produce different IDs. Solaris will not invent the same numbers either. If every Unix client is SSSD on RHEL-family systems, automatic mapping is the least work and it is a solid default. If you also have Samba, NFS clients, or Solaris that must see the same ownership, do not start with automatic mapping and try to bolt consistent IDs on later.
Option B: RFC2307 POSIX attributes in Active Directory
Active Directory can store the POSIX attributes themselves: uidNumber, gidNumber, unixHomeDirectory, loginShell, and related fields. These attributes have been in the AD schema since Windows Server 2003 R2. Microsoft removed the Identity Management for UNIX (IDMU) role and the “UNIX Attributes” tab from Active Directory Users and Computers starting with Windows Server 2016. The attributes were not removed. You edit them with the Attribute Editor (enable Advanced Features in ADUC), with PowerShell, or with an export such as the one in Export Active Directory to LDIF file.
To use those values with SSSD, disable automatic mapping at join time or afterwards:
# Join and read uidNumber/gidNumber from AD instead of inventing IDs
realm join --automatic-id-mapping=no corp.example.com
# If the host is already joined, set this in the domain section of /etc/sssd/sssd.conf,
# then clear the cache so old invented IDs cannot linger:
# ldap_id_mapping = false
rm -f /var/lib/sss/db/*
systemctl restart sssd
Every user and group you care about must then have unique, in-range IDs in AD, and the GID on a user must correspond to a group that also exists. If the attributes are published in the global catalog, lookups are faster; otherwise SSSD falls back to LDAP on each DC. The payoff is that SSSD, Winbind with idmap config CORP : backend = ad, NFS, and Solaris can all honor the same numbers. That is the right default when this series talks about mixed Samba, NFS and Solaris environments. Part 5 and part 6 go through attribute population and the Samba backends in detail.
Approach 1: realmd and SSSD (default for RHEL-family login hosts)
SSSD is the recommended client for joining a RHEL-family system directly to AD when the host is not going to be a Samba file or print server. realmd discovers the domain from DNS SRV records and writes the configuration; under the hood it calls adcli to create the computer account and keytab. An earlier, CentOS-oriented walk-through is still live at Join CentOS/RedHat to Active Directory Domain; this series updates that path for AlmaLinux 10 and then goes well beyond the join itself.
Install the tools, confirm that DNS can see the domain, then join. You need a user who can create computer objects in the target OU (Domain Admins works; a delegated join account is better, and is the subject of part 4):
dnf install samba-common-tools realmd oddjob oddjob-mkhomedir sssd adcli krb5-workstation
realm discover corp.example.com
A successful discovery looks like this (the package list is what realmd will pull in if it is missing):
corp.example.com
type: kerberos
realm-name: CORP.EXAMPLE.COM
domain-name: corp.example.com
configured: no
server-software: active-directory
client-software: sssd
required-package: oddjob
required-package: oddjob-mkhomedir
required-package: sssd
required-package: adcli
required-package: samba-common
realm join --verbose corp.example.com
# or, to store POSIX IDs in AD and have SSSD use them:
realm join --verbose --automatic-id-mapping=no corp.example.com
realmd edits /etc/sssd/sssd.conf, enables the oddjob home-directory helper, and starts SSSD. A typical domain section after a default join looks like this (comments added):
[sssd]
domains = corp.example.com
config_file_version = 2
services = nss, pam
[domain/corp.example.com]
ad_domain = corp.example.com
krb5_realm = CORP.EXAMPLE.COM
realmd_tags = manages-system joined-with-adcli
cache_credentials = True
id_provider = ad
access_provider = ad
krb5_store_password_if_offline = True
default_shell = /bin/bash
use_fully_qualified_names = True
fallback_homedir = /home/%u@%d
# ldap_id_mapping = True # default; omit or set false if you joined with --automatic-id-mapping=no
By default use_fully_qualified_names is true, so the user is jdoe@corp.example.com rather than jdoe. That avoids collisions with local accounts and is worth leaving on until you have a naming policy. realm permit and the access-control posts later in the series tighten who can log in; do not treat a successful join as “every AD user is now a login user on this host.”
Pros
- Red Hat’s recommended path for direct integration, and the one realmd uses by default.
- One daemon for AD, and later for FreeIPA or a generic LDAP/Kerberos source if you change direction.
- Cached credentials for offline or branch use, plus a mature sudo provider and autofs provider.
- Access control via filters or, with care, AD Group Policy settings that SSSD understands.
- Straightforward SSH logins and, in a later post, GSSAPI single sign-on with AD tickets.
Cons
- Not the supported identity backend when this host is a Samba file or print server on RHEL.
- Direct SSSD integration is a single AD forest by default; more than one forest takes extra domain configuration.
- Automatic ID mapping will not match Winbind or Solaris unless you switch to RFC2307 attributes (or accept different IDs on those systems).
- Policy that Windows administrators expect to live in GPOs (sudo, mounts, SSH settings) is only partly honored; a lot of it still belongs in SSSD, sudoers, autofs or Ansible.
Approach 2: adcli without realmd
adcli is the tool realmd already uses to create the computer account, update the keytab and talk to AD over LDAP and Kerberos. You can call it yourself for scripted joins, for putting the computer in a specific OU, and later for keytab rotation (alongside msktutil and net ads keytab; see the Kerberos keytabs post for the MIT-KDC form of the same idea). You still have to configure SSSD or Winbind yourself. For day-to-day interactive joins, realmd is less error-prone. For automation, part 8 and the Ansible post go through adcli directly.
adcli info corp.example.com
adcli join --domain-ou=OU=Linux,DC=corp,DC=example,DC=com corp.example.com
adcli show-computer rhel1.corp.example.com
Approach 3: realmd and Samba Winbind (file and print members)
Winbind is Samba’s AD client. It should be the identity service on any RHEL-family host whose job is to export shares or printers with smbd. Join it with realmd, but tell realmd to use Samba as the membership software and Winbind as the client:
dnf install realmd oddjob oddjob-mkhomedir sssd adcli krb5-workstation samba-common-tools samba-winbind samba
mv /etc/samba/smb.conf /etc/samba/smb.conf.bak # if a leftover config exists
realm join --membership-software=samba --client-software=winbind corp.example.com
realmd writes a domain-member /etc/samba/smb.conf, points Name Service Switch at Winbind, adjusts PAM, and enables the winbind service. winbindd must be running before smbd, or domain users are not visible to the file service. Do not also enable SSSD as the NSS source on the same host and hope the two stay in sync; pick one client stack per machine.
Older share-setup posts on this site, including Configure Samba Share For Domain Authentication and Create Windows Share Oracle Linux, are still useful for the share layout itself. This series will redo the member-server join and ID mapping on AlmaLinux 10, then cover Windows ACLs, drive maps and printing.
Pros
- The supported RHEL path for a Samba file or print server: Windows ACL support and NTLM fallback work the way smbd expects.
- Familiar to Windows administrators (computer account,
net ads testjoin, tools likesmbcacls). - idmap backends can follow RFC2307 attributes in AD, or compute IDs from the RID when you do not want to manage uidNumber.
- The same host can be the print server, using CUPS and Samba’s spoolss, which is how many Windows clients still expect to print. See also Share a CUPS printer with Windows over IPP.
Cons
- A weaker fit than SSSD for sudo-from-LDAP, autofs-from-LDAP, and some of the access-control features later in this series.
- Multi-forest setups generally need bidirectional trusts for full user information.
- If login hosts use SSSD automatic mapping and the file server uses Winbind
rid, ownership on disk will not match. Agree on RFC2307, or accept that this host is isolated. - You are running more moving parts (
winbindd,smbd,nmbdif you still need it) than a plain SSSD login server.
Approaches this series mentions but does not lead with
Legacy LDAP clients (nss-pam-ldapd, pam_ldap, nss_ldap on Linux)
Pointing nsswitch at raw LDAP against AD, with a simple bind and no machine account, is how a lot of Unix-to-AD integration was done fifteen years ago. It still works in narrow cases, but you lose proper Kerberos machine credentials, offline caching, and a lot of the access control SSSD and Winbind handle. This series does not recommend it for RHEL 8, 9 or 10. Solaris 10 still uses ldapclient in a carefully configured form, which is a different topic and gets its own posts.
Samba as an AD domain controller
Samba can be the Active Directory, not only join one. That is a reasonable choice for a lab, a small office that does not want to run Windows Server, or a domain you fully control. It is not a drop-in replacement for every Microsoft AD feature, and it is a different project from “join my AlmaLinux file server to the existing corporate forest.” Part 42 covers when a Samba AD DC is enough and where it stops. Until then, the rest of the series assumes Microsoft DCs at dc1 and dc2.
Indirect integration: FreeIPA or MIT Kerberos plus OpenLDAP, with a trust
If the Unix estate is large, you may want Linux-native policy (HBAC, sudo, host groups, a Unix CA) while Windows users still live in AD. The usual form is a FreeIPA (RHEL Identity Management) forest trust to AD, or a standalone MIT Kerberos plus OpenLDAP realm with a carefully built cross-realm trust. Clients then join the Unix realm, not AD directly. That is still integration, and it is the bridge to a later migration, but it is more moving parts than this series’ default. Part 43 covers it. TLS for a directory you run yourself is already documented in Configure OpenLDAP TLS and LDAPS on AlmaLinux 10.
Commercial agents
Products such as PBIS (Beyond Trust), Centrify/Delinea and Quest offer a supported agent, a Windows console for Unix attributes, and often a smoother path for Solaris and older Unix. They are a valid choice, especially if you already own them. This series uses the tools that ship with RHEL and Solaris so you can see the moving parts, not because an agent is never justified.
Samba file services, print services and Kerberized NFS
Once identity works, the reason you joined the domain is usually data and printers.
Samba as a file server. files1 is an AD member with Winbind. Shares can be home directories, departmental shares, or data that Windows clients map as a drive letter. Permissions can be POSIX, or Windows ACLs stored in vfs_acl_xattr and edited from Windows or with smbcacls. Getting the ACL model wrong is the usual source of “it looks open from Linux and denied from Windows” tickets. Parts 28 to 32 walk through member configuration, idmap, share design, ACLs and the Windows client side. For the opposite direction, mounting a Windows share on Linux, see Mounting Windows Share on CentOS and Forcefully Unmount a CIFS/Samba Share for the older mount/umount mechanics; a later post covers sec=krb5 and cifs.upcall on AlmaLinux 10.
Samba as a print server. CUPS holds the queues; Samba publishes them to Windows over the print spooler RPC (spoolss), and modern clients can also use IPP. Share a CUPS UNIX printer with Windows over IPP is the IPP path already on this site. This series adds the AD-joined Samba print-server path, including point-and-print and driver gotchas, in parts 33 and 34.
Kerberized NFS, with AD as the KDC. You do not need a second Kerberos realm to use sec=krb5, krb5i (integrity) or krb5p (privacy) on NFS. AD already is a KDC. The NFS server needs an nfs/nfs1.corp.example.com@CORP.EXAMPLE.COM service principal and a keytab, the clients need to be domain members (or at least Kerberos clients of the same realm), and rpc.gssd has to be running. This is the right way to mount home directories and project data when you do not want NFS to trust a client by IP alone. Parts 23 to 25 cover the modes, the principals and the mount. For mounts that already hang, the troubleshooting in Troubleshoot Stuck and Hung NFS Mounts on AlmaLinux 10 still applies. NFSv4 ACLs versus Windows ACLs get their own comparison in part 26, because they are not the same model.
sudo and automount from Active Directory
Two policies are worth calling out now, because both have a “quick” form and a “correct for a fleet” form.
sudo. The quick form is a line in /etc/sudoers.d/ad-admins that grants rights to an AD group. It works, it is easy to audit on a single host, and it does not require a schema change. An older LDAP-group variant is in Configure LDAP group for SUDO CentOS 6. The fleet form is to load the sudo schema into AD (the sudoRole object class: sudoUser, sudoHost, sudoCommand, sudoOption and related attributes) and let the SSSD sudo provider deliver rules to every joined host. That is more work up front and is the right design once you have more than a handful of servers. Parts 16 and 17 cover both, including the limits of each.
automount. The quick form is a local /etc/auto.master and local maps, or the style in Configure AutoMount CentOS 7. The correct form for a fleet, and the one this series will spend time on, is to extend the AD schema with RFC2307bis automount objects (automountMap and automount) and to let the SSSD autofs provider feed autofs. Some sites prefer the older NIS-style nisMap / nisObject classes, which AD can also hold; that is a valid alternative and gets its own post. Either way, the maps live in the directory next to the users, not in a copy of auto.home on every machine.
POSIX ACLs on files that groups from a directory must reach are a related topic; Setfacl using LDAP Groups is the earlier worked example.
Joining Solaris 10 and Solaris 11 to Active Directory
Solaris is not configured with realmd. The tools are different, and they deserve their own posts rather than a paragraph at the end of a Linux join guide.
On Oracle Solaris 11.4, Kerberos enrollment against a Microsoft KDC is:
/usr/sbin/kclient -T ms_ad
Starting client setup
---------------------------------------------------
Attempting to join 'SOL11' to the 'CORP.EXAMPLE.COM' domain.
Password for Administrator@CORP.EXAMPLE.COM:
Forest name found: corp.example.com
Looking for local KDCs, DCs and global catalog servers (SVR RRs).
Setting up /etc/krb5/krb5.conf
Creating the machine account in AD via LDAP.
---------------------------------------------------
Setup COMPLETE.
That makes the host a Kerberos client of AD and creates the machine account. Name service integration (so getent passwd returns AD users, not only Kerberos principals) is a second step: join SMB in domain mode with smbadm join, then run nscfg adldap, which configures the LDAP client to use SASL/GSSAPI against AD and updates the name-service switch. Solaris can also export SMB shares as a domain member. Parts 35 to 37 follow Oracle’s documented sequence and the places it surprises Linux administrators.
On Solaris 10 the same ideas show up as more manual editing: /etc/krb5/krb5.conf, pam_krb5 in pam.conf, kclient where the installed release provides it, and ldapclient / nss_ldap pointed at AD with the RFC2307 attributes populated. Automount and kerberized NFS against the AD KDC are possible, and they are easier if you already chose POSIX attributes in AD so the UID on Solaris is the UID on Linux. Parts 38 to 40 are one topic each, because a combined “Solaris” post would skip the parts that actually break.
A practical starting sequence
If you are standing this up for the first time, do not begin by editing smb.conf or loading a sudo schema. Work in this order:
- Fix DNS and time on a single AlmaLinux 10 test host (
rhel1). The host must resolvecorp.example.com, the DC names, and its own name the way AD will see it.chronyc trackingshould show a small offset from the same time source the DCs use (part 2). - Decide the ID strategy before the first join. All-SSSD login fleet with no shared Unix file system: automatic mapping is fine. Any mix of Samba, NFS and Solaris that must share ownership: populate
uidNumberandgidNumberin AD and disable automatic mapping (parts 5 and 6). - Join
rhel1with realmd and SSSD (part 7). Leave production file servers alone until the test host looks right. - Verify with the commands in the next section. Confirm a non-privileged AD user can SSH, and that a user who should be denied is denied.
- Only then join a Samba member with Winbind, add sudo and automount, stand up kerberized NFS, or start on Solaris. Each of those is easier when you already trust
idandkliston a simple host.
Verification
After a realmd + SSSD join, these commands should succeed. Sample output below is what you want to see for a user jdoe in corp.example.com. If you disabled automatic mapping, the UID and GID must match the attributes in AD, not a number SSSD invented.
realm list
corp.example.com
type: kerberos
realm-name: CORP.EXAMPLE.COM
domain-name: corp.example.com
configured: kerberos-member
server-software: active-directory
client-software: sssd
login-formats: %U@corp.example.com
login-policy: allow-realm-logins
id jdoe@corp.example.com
uid=10001(jdoe@corp.example.com) gid=10001(jdoe@corp.example.com) groups=10001(jdoe@corp.example.com),10011(linux-admins@corp.example.com)
getent passwd jdoe@corp.example.com
jdoe@corp.example.com:*:10001:10001:Jane Doe:/home/jdoe@corp.example.com:/bin/bash
kinit jdoe@CORP.EXAMPLE.COM
klist
Ticket cache: KCM:0
Default principal: jdoe@CORP.EXAMPLE.COM
Valid starting Expires Service principal
11/21/2026 16:05:12 11/22/2026 02:05:12 krbtgt/CORP.EXAMPLE.COM@CORP.EXAMPLE.COM
The ticket cache may show as KCM, as a FILE cache under /tmp, or as a KEYRING; klist prints whichever is the default on that host. Also confirm that the computer account exists in AD (Active Directory Users and Computers, or adcli show-computer rhel1.corp.example.com), that ssh -l jdoe@corp.example.com rhel1 opens a session and creates a home directory, and that timedatectl / chronyc tracking still look sane. For a Winbind member, add net ads testjoin, wbinfo -u and wbinfo -g, and only then start smbd.
Troubleshooting the first join
Most failed first joins are not SSSD bugs. Work through this table before you start rewriting configuration files. Part 19 is the full troubleshooting post.
| Symptom | Likely cause | What to check |
|---|---|---|
realm discover finds nothing | The host is not using AD DNS, or SRV records are missing | dig _ldap._tcp.corp.example.com SRV and _kerberos._tcp.corp.example.com SRV; /etc/resolv.conf |
| Join fails with a clock-skew or “Cannot authenticate” error | Time differs by more than about five minutes | chronyc tracking on Linux; w32time on the DCs; NTP allowed through the firewall |
| Join fails at the computer-account step | The join user cannot create objects in the target OU, or a stale computer account exists | Delegation on the OU; delete or reset the old computer object if you are re-joining the same name |
Join works, but id user@domain returns nothing | SSSD cannot reach LDAP/GC, or POSIX attributes are required but missing | journalctl -u sssd; if ldap_id_mapping = false, check uidNumber and gidNumber |
Login works on rhel1 but file ownership is wrong on files1 | Different ID mapping on SSSD and Winbind | Do not mix automatic SSSD IDs with Winbind rid on a shared tree; move both to RFC2307 or one algorithm |
| Kerberos works, LDAP simple binds fail from some networks | LDAP signing, LDAPS, or a blocked port 389/3268 | Prefer Kerberos/SASL; part 46 covers LDAPS to AD |
Solaris kclient cannot find DCs | DNS or UDP/TCP 88 from the Solaris host | The same SRV records; /etc/resolv.conf and kclient logs |
Comparison
| Approach | Best fit | ID mapping | Avoid when |
|---|---|---|---|
| realmd + SSSD | RHEL-family login, app and general servers | Automatic (default) or RFC2307 | The host’s main job is Samba file or print service on RHEL |
| adcli + hand-built SSSD | Scripted joins, custom OUs, keytab maintenance | Same as SSSD | You only need an interactive join; use realmd |
| realmd + Winbind | Samba file and print members | ad (RFC2307), rid or autorid | You need SSSD’s sudo and autofs providers on this same NSS stack |
| RFC2307 attributes in AD | Mixed SSSD, Samba, NFS and Solaris | uidNumber/gidNumber are the source of truth | You will not maintain unique IDs for every Unix-facing account |
| Kerberized NFS (AD KDC) | Unix-to-Unix data with AD credentials | Must match the clients’ UID scheme | You only serve Windows clients; use Samba |
| Solaris 11.4 kclient + nscfg adldap | Solaris 11 in an AD forest | Honor AD POSIX attributes | You expected realmd; it is not there |
| Solaris 10 Kerberos + ldapclient | Remaining Solaris 10 estate | Honor AD POSIX attributes | You can move the host to 11.4 first; the 11.4 path is cleaner |
| Samba AD DC | A domain you own, or a lab, with no Microsoft DC requirement | Its own AD schema, optional RFC2307 | You must join an existing corporate Microsoft forest as just another DC without a migration plan |
| FreeIPA or MIT KDC + OpenLDAP, with a trust | Large Unix estate that needs Linux-native policy, still using AD users | Plan the ID ranges up front | You only have a few Linux servers; direct join is simpler |
Prerequisites for the rest of the series
You can read the later posts in any order, but the work itself wants a short baseline:
- A supported AD forest (Windows Server 2019, 2022 or 2025 DCs are assumed) with working DNS SRV records for LDAP and Kerberos.
- Network permission from Unix hosts to the DCs on the usual ports (DNS, Kerberos 88 and 464, LDAP 389, SMB 445, RPC, Global Catalog 3268; the full list is in part 2).
- A join account that can create computer objects in a dedicated OU, rather than using Domain Admin on a daily basis.
- A written decision on ID mapping, even if the decision is “automatic mapping, SSSD only, no shared Unix file systems.”
- For RFC2307: a unique UID/GID plan that does not collide with local system accounts (stay at 10000 and above unless you already have a scheme).
- Root or sudo on the Unix hosts, and a change window for the first join so a bad
nsswitch.confis not a remote lockout. Keep a local account that can still log in.
How the series is organized
Weekly posts follow this order. Part 2 starts with the unglamorous prerequisites, because that is where joins actually fail. Then POSIX attributes and ID mapping, then the RHEL-family joins (SSSD, adcli, Winbind), SSSD in depth, SSH, access control, sudo, keytabs and troubleshooting. Automount from AD comes next, then kerberized NFS and CIFS clients, then Samba file and print, then Solaris 11 and Solaris 10. The later posts cover trusts, a Samba AD DC, a FreeIPA or MIT Kerberos hybrid, Ansible automation, UID consistency, LDAPS, computer-account hygiene, offline credentials, logging, hardening and a checklist.
Existing material this series will keep pointing at, rather than rewriting, includes the MIT Kerberos KDC, keytabs, primary and replica KDCs and Kerberos client posts (useful background, even though AD is the KDC here), the OpenLDAP install, users and groups and TLS posts, and the Samba, autofs, sudo and NFS articles already linked above.
What is next
Part 2 is the prerequisite pass: point the host at AD DNS, set the hostname and PTR the way the computer account will be named, sync time with chrony against the same source the domain controllers use, and open the ports SSSD and Winbind actually need. Once that is done, realm discover should return a domain on the first try, and the joins in parts 7 through 9 become the easy step.
