There will be an introduction then jump to the lab

Active Directory

From the outset, Active Directory is, simplifying for the sake of the material, a directory service that maintains data about users' logins, passwords, group memberships and permissions, access expiration times, forcing password renewals and other mechanisms hated by users. Active Directory It is an interesting solution that allows centralized and automated management of users working mainly under the control of Windows series of all kinds. Important TIP to work with Active Directory in a simple way can not Windows Home series. Since the Proffesional version. Active Directory itself works under the control of Windows server series. Such a solution works the more the more users there are in the organization. Because imagine having to change passwords on email, laptop and other systems on a regular basis. The alternative is just to use Active Directory as a central point for maintaining information about users, passwords and their rights to services, etc. That is, we change the password on the computer pinned to the domain and it changes on all integrated systems. Cool right? And why am I just talking about this in the context of TrueNAS? Well, that's why TrueNAS can also be synchronized with Active Directory, which will make it unnecessary to manage users directly in TrueNAS. That is, if we already have Active Directory configured and working somewhere, we just plug in TrueNAS and the domain users can automatically use network resources with the proper rights or group rights to which they belong. Because, after all, that's what it's all about so that users can access what they should and not what they shouldn't.
And that's what it will be all about.

Lab

Regarding the lab, I will show how to do it on the example of TrueNAS-SCALE-22.02.4 and TrueNAS CORE 13.0-U2. I wanted to show on both because, however, they differ a little intefacem besides that Truenas CORE for October 2022 seems to be the leader but SCALE is gaining momentum and becoming more and more interesting. Admittedly, in my opinion it is still slightly immature, I do not mean that it is unstable, absolutely not. I mean the little things, the underdevelopment of the menu, etc. I still know that there are difficulties with advanced network setup for Docker. I also see that with each update the little things are eliminated and it becomes more mature. Cool because I'm a fan of Debian and containerization, and I really like that this setup is landing and being dynamically developed in TrueNAS and, back on topic, in Microsoft's corner will be Windows Server 2016 as supporting us Active Directory server. Informatively this Windows is purely for testing we do not use it, I know it is old. Generally at our place we do not use Windows server. Yes we support it for Customers but we rather not push it.

A few additional notes about the installation itself that are worth mentioning because they can save us unnecessary time later, and since I have already wasted it, why should you. The basis of this configuration is a well-functioning Active Directory if it does not work there is no point in going further - it will not work. Go back correct and come back to TrueNAS. This material will absolutely not be about Active Directory configuration.

From basic tips

For Active Directory to work properly it must be the DNS server for the entire network. Including, not obviously, itself. All computers on the network, TrueNAS and the server itself must have the Active Directory server's IP set as DNS.
Next thing the user we will use to log TrueNAS em into the domain must be added to the domain administrators groups.
In addition, another catch, if you had static users configured and they had access to files, then when TrueNAS is added to access those users will lose access to those files.

I haven't found any simple solution to let you use static users after logging into the domain. If you have found a way to do this let me know in the comments.

I INVITE YOU TO WATCH