-What's new in Samba 4 alpha16
+What's new in Samba 4 beta2
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
support for the Active Directory logon protocols used by Windows 2000
and above.
+
WARNINGS
========
-Samba4 alpha16 is not a final Samba release, however we are now making
+Samba4 beta2 is not a final Samba release, however we are now making
good progress towards a Samba 4.0 release, of which this is a preview.
-Be aware the this release contains both the technology of Samba 3.6
-(that you can reasonably expect to upgrade existing Samba 3.x releases
-to) and the AD domain controller work previously known as 'samba4'.
-No migration path is currently provided between these two sets of
-technology. These missing migration paths will be the focus of
-development between now and a Samba 4.0 release.
-
-While binaries for the stable file server are provided in this
-release, for a stable, supported file server, Samba3 domain or AD
-domain member installation, please run a Samba 3.x release, as we are
-still bedding down the new single build system.
+Be aware the this release contains the best of all of Samba's
+technology parts, both a file server (that you can reasonably expect
+to upgrade existing Samba 3.x releases to) and the AD domain
+controller work previously known as 'samba4'.
Samba4 is subjected to an awesome battery of tests on an automated
basis, we have found Samba 4.0 to be very stable in it's behavior.
However, we still recommend against upgrading production servers from
-Samba 3.x release to Samba 4.0 alpha at this stage.
+Samba 3.x release to Samba 4.0 beta at this stage.
+
+In particular note that the new default configuration 's3fs' may have
+different stability characteristics compared with our previous default
+file server. We are making this release so that we can find and fix
+any of these issues that arise in the real world. New AD DC
+installations can provision or join with --use-ntvfs to obtain the
+previous default file server. See below how to continue using ntvfs
+in an existing installation.
If you are upgrading, or looking to develop, test or deploy Samba 4.0
-alpha releases, you should backup all configuration and data.
+beta releases, you should backup all configuration and data.
+
+
+UPGRADING
+=========
+
+Users upgrading from Samba 3.x domain controllers and wanting to use
+Samba 4.0 as an AD DC should use the 'samba-tool domain
+classicupgrade' command. See the wiki for more details:
+https://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO
+
+Users upgrading from Samba 4.0 alpha and beta releases since alpha15
+should run 'samba-tool dbcheck --cross-ncs --fix'. Users upgrading
+from earlier alpha releases should contact the team for advice.
+
NEW FEATURES
============
-Samba 4.0 alpha supports the server-side of the Active Directory logon
+Samba 4.0 beta supports the server-side of the Active Directory logon
environment used by Windows 2000 and later, so we can do full domain
join and domain logon operations with these clients.
the infamous Kerberos PAC, and include it with the Kerberos tickets we
issue.
-Samba 4.0 alpha ships with two distinct file servers. The file server
-from the Samba 3.x series is 'smbd', and works with the binaries users
-would expect from that series (nmbd, winbindd, smbpasswd).
-
-Samba 4.0 also ships with a new file server, which is tuned to match
-the requirements of an AD domain controller. Users should not use the
-file server in the 'samba' binary for non-DC related tasks.
-
-A new scripting interface has been added to Samba 4, allowing Python
-programs to interface to Samba's internals, and many tools and
+Samba 4.0 beta ships with two distinct file servers. We now use the
+file server from the Samba 3.x series 'smbd' for all file serving by
+default. For pure file server work, the binaries users would expect
+from that series (nmbd, winbindd, smbpasswd) continue to be available.
+
+Samba 4.0 also ships with the 'NTVFS' file server. This file server
+is what was used in all previous alpha releases of Samba 4.0, and is
+tuned to match the requirements of an AD domain controller. We
+continue to support this, not only to provide continuity to
+installations that have deployed it as part of an AD DC, but also as a
+running example of the NT-FSA architecture we expect to move smbd to in
+the longer term.
+
+As mentioned above, this change to the default file server may cause
+instability, as we learn about the real-world interactions between
+these two key components.
+
+As DNS is an integral part of Active Directory, we also provide a DNS
+solution, using the BIND DLZ mechanism in versions 9.8 and 9.9.
+During the provision, a configuration file will be generated for bind
+to make it use this plugin. We also have a project to provide a
+minimal internal DNS server from within the Samba process, for easier
+'out of the box' configuration. Note however that this is not yet
+complete (pending addition of secure DNS update support).
+
+To provide accurate timestamps to Windows clients, we integrate with
+the NTP project to provide secured NTP replies.
+
+Finally, a new scripting interface has been added to Samba 4, allowing
+Python programs to interface to Samba's internals, and many tools and
internal workings of the DC code is now implemented in python.
-CHANGES SINCE alpha15
+CHANGES SINCE beta1
=====================
-For a list of changes since alpha 15, please see the git log.
+For a list of changes since beta1, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log release-4-0-0alpha15..release-4-0-0alpha16
+$ git log samba-4.0.0beta1..samba-4.0.0beta2
-The biggest user-visible change is that binaries from the Samba 3.x
-series of development are now built and installed. These binaries
-(smbd, nmbd, winbindd, net, testparm, etc) operate much as they do in
-the Samba 3.6 release candidates.
+Some major user-visible changes include:
-CHANGES
-=======
+The default file server for EXISTING USERS has changed to s3fs. To
+continue to use ntvfs, you must set in your smb.conf:
-smb.conf changes
-----------------
+ server services = +smb -s3fs
+ dcerpc endpoint servers = +winreg +srvsvc
- Parameter Name Description Default
- -------------- ----------- -------
- announce version Removed
- announce as Removed
+samba-tool dbcheck will now upgrade older databases that are missing
+GUIDs in the schema partition.
-Those familiar with Samba 3 can find a list of user-visible changes
-between the two technology sets provided in the NEWS file.
KNOWN ISSUES
============
+- This release makes the s3fs file server the default, as this is the
+ file server combination we will use for the Samba 4.0 release.
+ Users should still expect some rough edges: in particular, there are
+ warnings about invalid parameters from the two respective parameter
+ parsing engines.
+
+- Replication of DNS data from one AD server to another may not work.
+ The DNS data used by the internal DNS server and bind9_dlz is stored
+ in an application partition in our directory. The replicaton of
+ this partition is not yet reliable.
+
+- Replication may fail on FreeBSD due to getaddrinfo() rejecting names
+ containing _. A workaround will be in the next beta.
+
+- upgradeprovision should not be run when upgrading to this release
+ from a recent release. No important database format changes have
+ been made since alpha16.
+
+- Installation on systems without a system iconv (and developer
+ 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.
-- There is no printing support in the 'samba' binary (use smbd instead)
-
-- There is no NetBIOS browsing support in the 'samba' binary (use nmbd
- and smbd instead)
+- There is no NetBIOS browsing support (network neighbourhood) in the
+ 'samba' binary (use nmbd and smbd instead)
- Clock Synchronisation is critical. Many 'wrong password' errors are
actually due to Kerberos objecting to a clock skew between client
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
-- Users upgrading existing databases to Samba4 should carefully
- consult upgrading-samba4.txt. We have made a number of changes in
- this release that should make it easier to upgrade in future.
- Btw: there exists also a script under the "setup" directory of the
- source distribution called "upgrade_from_s3" which should allow a step-up
- from Samba3 to Samba4. It's not included yet in the binary distributions
- since it's completely experimental!
RUNNING Samba 4.0 as an AD DC
=============================
git.samba.org / kai / samba-autobuild / .git / blobdiff