-What's new in Samba 4 alpha21
+What's new in Samba 4 beta2
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
WARNINGS
========
-Samba4 alpha21 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 the best of all of Samba's
technology parts, both a file server (that you can reasonably expect
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 with --use-ntvfs to obtain the previous default file
-server. Existing installations will be unaffected at this stage.
+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. We now use the
+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.
instability, as we learn about the real-world interactions between
these two key components.
-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.
+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 alpha20
+
+CHANGES SINCE beta1
=====================
-For a list of changes since alpha20, 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 samba-4.0.0alpha20..samba-4.0.0alpha21
+$ git log samba-4.0.0beta1..samba-4.0.0beta2
Some major user-visible changes include:
-For installations that do not need an AD Domain controller, we can now
-build using MIT Kerberos from the local system. This is important for
-some distributors. This is enabled with the new --with-system-mitkrb5
-configure option. A synonym is the new --without-ad-dc option.
+The default file server for EXISTING USERS has changed to s3fs. To
+continue to use ntvfs, you must set in your smb.conf:
+
+ server services = +smb -s3fs
+ dcerpc endpoint servers = +winreg +srvsvc
+
+samba-tool dbcheck will now upgrade older databases that are missing
+GUIDs in the schema partition.
-The 's3fs' effort has moved to a new stage, with this now being the
-default mode of operation for new provisions.
+The 'samba-tool domain samba3upgrade' command is now called
+'samba-tool domain classicupgrade' and now creates users and groups
+with the posixAccount objectClass and uidNumber and gidNumber values.
-The BIND 9 DLZ plugin has had some stability improvements under BIND reloads.
+The new 'idmap_ldb:use rfc2307' parameter allows these values to be
+used instead of the idmap.ldb, where found in the directory.
-The 'samba-tool domain samba3upgrade' tool will now generally import
-all group members, and correctly imports domain password policies.
+Work has continued to make Samba more portable to a wide variety of
+Unix-like systems, and to support --without-ad-dc on systems lacking a
+modern MIT krb5.
-Some major but less visible changes include:
+Less visible, but very importantly, the work has continued in restructuring
+the smbd file server to implement SMB3.
-Continued early implementation work on the SMB 2.2 protocol client and server as
-the team improves and develops support these new protocols.
+The TDB2 database library has been changed to ntdb, but will not be
+the default db layer for the 4.0 release. We will continue to use tdb1.
KNOWN ISSUES
============
-- We are making this alpha release to gain real-world use of the 's3fs'
+- 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 expect some rough edges: in particular, there are
+ Users should still expect some rough edges: in particular, there are
warnings about invalid parameters from the two respective parameter
parsing engines.
-- There have been improvements to FreeBSD support, but more work is
- still required to finish this effort
+- 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
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
+
RUNNING Samba 4.0 as an AD DC
=============================
git.samba.org / metze / samba / wip.git / blobdiff