1 What's new in Samba 4 alpha9
2 ============================
4 Samba 4 is the ambitious next version of the Samba suite that is being
5 developed in parallel to the stable 3.0 series. The main emphasis in
6 this branch is support for the Active Directory logon protocols used
7 by Windows 2000 and above.
9 Samba4 alpha9 follows on from the alpha release series we have been
10 publishing since September 2007
15 Samba4 alpha9 is not a final Samba release. That is more a reference
16 to Samba4's lack of the features we expect you will need than a
17 statement of code quality, but clearly it hasn't seen a broad
18 deployment yet. If you were to upgrade Samba3 (or indeed Windows) to
19 Samba4, you would find many things work, but that other key features
20 you may have relied on simply are not there yet.
22 For example, while Samba 3.0 is an excellent member of a Active
23 Directory domain, Samba4 is happier as a domain controller, and it is
24 in this role where it has seen deployment into production.
26 Samba4 is subjected to an awesome battery of tests on an
27 automated basis, we have found Samba4 to be very stable in it's
28 behaviour. We have to recommend against upgrading production servers
29 from Samba 3 to Samba 4 at this stage, because there may be the features on
30 which you may rely that are not present, or the mapping of
31 your configuration and user database may not be complete.
33 If you are upgrading, or looking to develop, test or deploy Samba4, you should
34 backup all configuration and data.
39 Samba4 supports the server-side of the Active Directory logon environment
40 used by Windows 2000 and later, so we can do full domain join
41 and domain logon operations with these clients.
43 Our Domain Controller (DC) implementation includes our own built-in
44 LDAP server and Kerberos Key Distribution Center (KDC) as well as the
45 Samba3-like logon services provided over CIFS. We correctly generate
46 the infamous Kerberos PAC, and include it with the Kerberos tickets we
49 The new VFS features in Samba 4 adapts the filesystem on the server to
50 match the Windows client semantics, allowing Samba 4 to better match
51 windows behaviour and application expectations. This includes file
52 annotation information (in streams) and NT ACLs in particular. The
53 VFS is backed with an extensive automated test suite.
55 A new scripting interface has been added to Samba 4, allowing
56 Python programs to interface to Samba's internals.
58 The Samba 4 architecture is based around an LDAP-like database that
59 can use a range of modular backends. One of the backends supports
60 standards compliant LDAP servers (including OpenLDAP), and we are
61 working on modules to map between AD-like behaviours and this backend.
62 We are aiming for Samba 4 to be powerful frontend to large
68 In the time since Samba4 alpha8 was released in June 2009, Samba has
69 continued to evolve, but you may particularly notice these areas
70 (in no particular order):
72 Samba4 now includes the full set of user interface strings (display Specifiers)
73 required to have the Microsoft Management Console operate
75 LDB (the core Samba4 database library) has again been reworked for
78 Replication between Samba4 and Active Directory domains using the
79 native replication protocol (DRS) has been demonstrated.
81 Access Control Lists (in nTSecurityDescriptor) are now set correctly
82 on objects in the directory, based on the same rules as Windows 2008.
83 (Searches and modifications still use a simplistic administrator/not
84 administrator criteria)
86 These are just some of the user-visible highlights of the work done in
87 the past few months. More details of the work done 'under the hood'
88 can be found in our GIT history.
94 Those familiar with Samba 3 can find a list of user-visible changes
95 since that release series in the NEWS file.
100 - Domain member support is in it's infancy, and is not comparable to
101 the support found in Samba3.
103 - There is no printing support in the current release.
105 - There is no NetBIOS browsing support in the current release
107 - The Samba4 port of the CTDB clustering support is not yet complete
109 - Clock Synchronisation is critical. Many 'wrong password' errors are
110 actually due to Kerberos objecting to a clock skew between client
111 and server. (The NTP work in the previous alphas are partly to assist
114 - The DRS replication code often fails, and is very new
116 - Users upgrading existing databases to Samba4 should carefully
117 consult upgrading-samba4.txt. We have made a number of changes in
118 this release that should make it easier to upgrade in future.
119 Btw: there exists also a script under the "scripting/bin" directory of the
120 source distribution called "upgrade_from_s3" which should allow a step-up
121 from Samba3 to Samba4. It's not included yet in the binary distributions
122 since it's completely experimental!
124 - ACL are not set by default on shares created by the provision.
125 Work is underway on this subject and it should be fixed in Alpha10.
130 A short guide to setting up Samba 4 can be found in the howto.txt file
131 in root of the tarball.
133 DEVELOPMENT and FEEDBACK
134 ========================
136 Bugs can be filed at https://bugzilla.samba.org/ but please be aware
137 that many features are simply not expected to work at this stage.
139 The Samba Wiki at http://wiki.samba.org should detail some of these
142 Development and general discussion about Samba 4 happens mainly on
143 the #samba-technical IRC channel (on irc.freenode.net) and
144 the samba-technical mailing list (see http://lists.samba.org/ for