From 790038380f2f3af5537f569f2b5a1e40370f4585 Mon Sep 17 00:00:00 2001 From: Andrew Bartlett Date: Wed, 27 Feb 2013 22:27:14 +1100 Subject: [PATCH] WHATSNEW: clarify that being a domian member is a fully supported part of Samba 4.0 --- WHATSNEW.txt | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/WHATSNEW.txt b/WHATSNEW.txt index b594e0e..1351bba 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -189,10 +189,16 @@ KNOWN ISSUES headers at compile time) is known to cause errors when dealing with non-ASCII characters. -- Domain member support in the 'samba' binary is in it's infancy, and - is not comparable to the support found in winbindd. As such, do not - use the 'samba' binary (provided for the AD server) on a member - server. +- Samba requires that administrators use different binaries for + different server roles. For example, because domain member support + in the 'samba' binary is in it's infancy, and is not comparable to + the support found in winbindd, we only support using this in + conjunction with the ntvfs file server, in support of the CIFS + proxy, or in support of OpenChange. In all other use cases, + including standalone servers, domain member servers and classic + domain controllers, the same 'smbd', 'nmbd' and 'winbindd' binaries + found in Samba 3.x are to be used, and remain fully supported. A + start-up check is in place to enforce these rules. - There is no NetBIOS browsing support (network neighbourhood) available for the AD domain controller. (Support in nmbd and smbd -- 1.7.11.7