It is worth noting that Centrify does have additional functionality, though this can be provided by separate configuration management. This could probably be dealt with via proper monitoring if you care to put the effort into it. There's very infrequent service failure that requires someone with root or other local account to go in and bounce winbindd. I have personally used WinBind fairly reliably for authentication.
CENTRIFY SAMBA INTEGRATION GUIDE UPDATE
Should this link go stale, please let me know and I'll update the answer accordingly. It was published for the Summit last week. This document (corrected) is hot off the press seems to focus on the new features of Red Hat Enterprise Linux (RHEL) 7. (This material should certainly be current and relevant.) I hate to post this as an answer, but it's really just too much material to transfer into the answer field. In March 2014, Red Hat published a reference architecture for integrating Red Hat Enterprise Server with Active Directory. How do you handle this in your environment? The customer wants to use Winbind, but everything I see from the Red Hat side points to the use of SSSD. That makes it really difficult to rely on if it may break forward-compatibility. LDAP, Samba Client, Kerberos, or non-Microsoft options. Remote Server Administration Tools (RSAT) is deprecated. The Server for Network Information Service (NIS) Tools option of The benefit of having this role installed is the presence of this GUI, while allows easy one-step administration of user attributes.
CENTRIFY SAMBA INTEGRATION GUIDE WINDOWS
And I'm told that this feature is deprecated is no longer present in Windows Server 2012 R2. I'm working with a new installation where the domain controllers are Windows 2008 R2 Core systems and do not have the ability to add the Identity Management for Unix role feature. Red Hat also seemed to back the SSSD approach, so that's been fine for my use.
This worked until RHEL6, where the lack of maintenance on NSLCD and memory resource management issues forced a change to SSSD. The last few installations I've done had the Microsoft Identity Management for Unix role feature added to a Windows 2008 R2 server and NSLCD on the Linux side (for RHEL5). The commercial solutions like Centrify and Likewise always worked, but seemed unnecessary, since this capability is baked into the OS. Winbind always seemed terrible and unreliable.
Microsoft Windows Services for Unix (SFU)
I'm not quite sure which method currently has the most momentum. Over the years since my first attempts with integration in 2004, it seems like the best-practices around this have shifted. What is the common wisdom in 2014 about Active Directory authentication/integration for Linux servers and modern Windows Server operating systems (CentOS/RHEL-focused)?
0 kommentar(er)
