Hi @Vitor_Hugo_Barbosa
Thank you for this howto. I am curious why you choose PBIS-Open to join your linux client to Samba4AD? IMO it is introducing extra (unnecessary?) packages because PBIS-Open uses a mandatory agent on every client.
Why not using a more traditional option and install realmd sssd oddjob oddjob-mkhomedir adcli samba-common-tools packages so you don’t need a 3rd party agent?
I remember I used PBIS-Open in the past on an LTSP environment with a Zentyal host.
Also a concern is the ‘other services’ provided by BeyondTrust. Those don’t seem to be opensource? So when you start with PBIS-Open, you will run into non free software sooner or later…
Looking through the documentation, I must say that decent docs on joining a NethServer Samba4AD is lacking. In the documentation I only find creation of users and homedirs and groups etc… but device accounts are completely neglected.
@support_team @docs_team @dev_team Can we start an extra chapter adding device accounts to Samba4AD account provider. With explanation of different approaches (SSSD vs WindBind vs PBIS-Open) and how to manage them.
If we want to be a viable alternative for Windows Server, IMO this should be added.