1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
What's new in Samba 4.0 beta5
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
all the technology found in both the Samba4 alpha series and the
stable 3.x series. The primary additional features over Samba 3.6 are
support for the Active Directory logon protocols used by Windows 2000
and above.
WARNINGS
========
Samba 4.0 beta5 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
to upgrade existing Samba 3.x releases to) and the AD domain
controller work previously known as 'samba4'.
Samba 4.0 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 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
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 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.
Our Domain Controller (DC) implementation includes our own built-in
LDAP server and Kerberos Key Distribution Center (KDC) as well as the
Samba3-like logon services provided over CIFS. We correctly generate
the infamous Kerberos PAC, and include it with the Kerberos tickets we
issue.
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 beta4
=====================
For a list of changes since beta4, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
$ git log samba-4.0.0beta4..samba-4.0.0beta5
Some major user-visible changes include:
- The issue with beta4 being unable to build with a released version of
ldb has been resolved.
- The two parameter tables for our two smb.conf parsing engines have
been merged. This removes the ugly (but harmless) "unknown
parameter xxx" warnings, particularly from the smbd child process.
- Major issues have been fixed in conflict and missing/deleted parent
handling in or DRS replication engine.
- Safety improvements to prevent corruption of read-write replicas
by manual replication from a read-only replica.
- Improvements to dbcheck to correct incorrect instanceType values from
the above and to relocate objects with missing parents.
- smbd no longer places all accounts in the 'Domain Users' of the AD
domain to which it is joined
- AES support in NETLOGON Schannel
- DCE/RPC timeout handling no longer crashes
- "socket address" is now "nbt client socket address" as it only
controls the binding of the NetBIOS client, not other protocols.
See 'bind interfaces only = yes'. This parameter is also now depricated.
- nmbd now always binds to it's broadcast sockets explicitly, rather
than just relying on the socket address above.
Less visible, but important changes under the hood include:
- Continued work to support SMB2 and SMB3
- Continued work to use async IO to improve file server performance.
- Patches to ensure that talloc_tos() and talloc_stackframe() are
always used correctly.
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.
- Modifying of group policies by members of the Domain Administrators
group is not possible with the s3fs file server, only with the ntvfs
file server. This is due to the underlying POSIX ACL not being set
at provision time.
- For similar reasons, sites with ACLs stored by the ntvfs file server
may wish to continue to use that file server implementation, as a
posix ACL will similarly not be set in this case.
- 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 replication 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 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
and server. (The NTP work in the previous alphas are partly to assist
with this problem).
- The DRS replication code may fail. Please contact the team if you
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
=============================
A short guide to setting up Samba 4 as an AD DC can be found on the wiki:
http://wiki.samba.org/index.php/Samba4/HOWTO
#######################################
Reporting bugs & Development Discussion
#######################################
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
be filed under the Samba 4.0 product in the project's Bugzilla
database (https://bugzilla.samba.org/).
======================================================================
== Our Code, Our Bugs, Our Responsibility.
== The Samba Team
======================================================================
|
