1 <chapter id="upgrading-to-3.0">
6 <pubdate>June 30, 2003</pubdate>
9 <title>Upgrading from Samba-2.x to Samba-3.0.0</title>
13 <title>New Features in Samba-3</title>
21 Active Directory support. This release is able to join a ADS realm
22 as a member server and authenticate users using LDAP/kerberos.
26 Unicode support. Samba will now negotiate UNICODE on the wire and
27 internally there is now a much better infrastructure for multi-byte
28 and UNICODE character sets.
32 New authentication system. The internal authentication system has
33 been almost completely rewritten. Most of the changes are internal,
34 but the new auth system is also very configurable.
38 New filename mangling system. The filename mangling system has been
39 completely rewritten. An internal database now stores mangling maps
40 persistently. This needs lots of testing.
44 New "net" command. A new "net" command has been added. It is
45 somewhat similar to the "net" command in windows. Eventually we
46 plan to replace a bunch of other utilities (such as smbpasswd)
47 with subcommands in "net", at the moment only a few things are
52 Samba now negotiates NT-style status32 codes on the wire. This
53 improves error handling a lot.
57 Better Windows 2000/XP/2003 printing support including publishing
58 printer attributes in active directory
62 New loadable RPC modules
66 New dual-daemon winbindd support (-B) for better performance
70 Support for migrating from a Windows NT 4.0 domain to a Samba
71 domain and maintaining user, group and domain SIDs
75 Support for establishing trust relationships with Windows NT 4.0
80 Initial support for a distributed Winbind architecture using
81 an LDAP directory for storing SID to uid/gid mappings
85 Major updates to the Samba documentation tree.
89 Plus lots of other improvements!
95 <title>Configuration Parameter Changes</title>
98 This section contains a brief listing of changes to smb.conf options
99 in the 3.0.0 release. Please refer to the smb.conf(5) man page for
100 complete descriptions of new or modified parameters.
104 <title>Removed Parameters</title>
106 <para>(order alphabetically):</para>
109 <listitem><para>admin log </para></listitem>
110 <listitem><para>alternate permissions </para></listitem>
111 <listitem><para>character set </para></listitem>
112 <listitem><para>client codepage </para></listitem>
113 <listitem><para>code page directory </para></listitem>
114 <listitem><para>coding system </para></listitem>
115 <listitem><para>domain admin group </para></listitem>
116 <listitem><para>domain guest group </para></listitem>
117 <listitem><para>force unknown acl user </para></listitem>
118 <listitem><para>nt smb support </para></listitem>
119 <listitem><para>post script </para></listitem>
120 <listitem><para>printer driver </para></listitem>
121 <listitem><para>printer driver file </para></listitem>
122 <listitem><para>printer driver location </para></listitem>
123 <listitem><para>status </para></listitem>
124 <listitem><para>total print jobs </para></listitem>
125 <listitem><para>use rhosts </para></listitem>
126 <listitem><para>valid chars </para></listitem>
127 <listitem><para>vfs options </para></listitem>
133 <title>New Parameters</title>
135 <para>(new parameters have been grouped by function):</para>
137 <para>Remote management</para>
140 <listitem><para>abort shutdown script </para></listitem>
141 <listitem><para>shutdown script </para></listitem>
144 <para>User and Group Account Management</para>
147 <listitem><para>add group script </para></listitem>
148 <listitem><para>add machine script </para></listitem>
149 <listitem><para>add user to group script </para></listitem>
150 <listitem><para>algorithmic rid base </para></listitem>
151 <listitem><para>delete group script </para></listitem>
152 <listitem><para>delete user from group script </para></listitem>
153 <listitem><para>passdb backend </para></listitem>
154 <listitem><para>set primary group script </para></listitem>
157 <para>Authentication</para>
160 <listitem><para>auth methods </para></listitem>
161 <listitem><para>ads server </para></listitem>
162 <listitem><para>realm </para></listitem>
165 <para>Protocol Options</para>
168 <listitem><para>client lanman auth </para></listitem>
169 <listitem><para>client NTLMv2 auth </para></listitem>
170 <listitem><para>client schannel </para></listitem>
171 <listitem><para>client signing </para></listitem>
172 <listitem><para>client use spnego </para></listitem>
173 <listitem><para>disable netbios </para></listitem>
174 <listitem><para>ntlm auth </para></listitem>
175 <listitem><para>paranoid server security </para></listitem>
176 <listitem><para>server schannel </para></listitem>
177 <listitem><para>smb ports </para></listitem>
178 <listitem><para>use spnego </para></listitem>
181 <para>File Service</para>
184 <listitem><para>get quota command </para></listitem>
185 <listitem><para>hide special files </para></listitem>
186 <listitem><para>hide unwriteable files </para></listitem>
187 <listitem><para>hostname lookups </para></listitem>
188 <listitem><para>kernel change notify </para></listitem>
189 <listitem><para>mangle prefix </para></listitem>
190 <listitem><para>msdfs proxy </para></listitem>
191 <listitem><para>set quota command </para></listitem>
192 <listitem><para>use sendfile </para></listitem>
193 <listitem><para>vfs objects </para></listitem>
196 <para>Printing</para>
199 <listitem><para>max reported print jobs </para></listitem>
203 <para>UNICODE and Character Sets</para>
206 <listitem><para>display charset </para></listitem>
207 <listitem><para>dos charset </para></listitem>
208 <listitem><para>unicode </para></listitem>
209 <listitem><para>unix charset </para></listitem>
212 <para>SID to uid/gid Mappings</para>
215 <listitem><para>idmap backend </para></listitem>
216 <listitem><para>idmap gid </para></listitem>
217 <listitem><para>idmap only </para></listitem>
218 <listitem><para>idmap uid </para></listitem>
224 <listitem><para>ldap delete dn </para></listitem>
225 <listitem><para>ldap group suffix </para></listitem>
226 <listitem><para>ldap idmap suffix </para></listitem>
227 <listitem><para>ldap machine suffix </para></listitem>
228 <listitem><para>ldap passwd sync </para></listitem>
229 <listitem><para>ldap trust ids </para></listitem>
230 <listitem><para>ldap user suffix </para></listitem>
233 <para>General Configuration</para>
236 <listitem><para>preload modules </para></listitem>
237 <listitem><para>privatedir </para></listitem>
243 <title>Modified Parameters (changes in behavior):</title>
246 <listitem><para>encrypt passwords (enabled by default) </para></listitem>
247 <listitem><para>mangling method (set to 'hash2' by default) </para></listitem>
248 <listitem><para>passwd chat </para></listitem>
249 <listitem><para>passwd program </para></listitem>
250 <listitem><para>restrict anonymous (integer value) </para></listitem>
251 <listitem><para>security (new 'ads' value) </para></listitem>
252 <listitem><para>strict locking (enabled by default) </para></listitem>
253 <listitem><para>winbind cache time (increased to 5 minutes) </para></listitem>
254 <listitem><para>winbind uid (deprecated in favor of 'idmap uid') </para></listitem>
255 <listitem><para>winbind gid (deprecated in favor of 'idmap gid') </para></listitem>
263 <title>New Functionality</title>
266 <title>Databases</title>
269 This section contains brief descriptions of any new databases
270 introduced in Samba 3.0. Please remember to backup your existing
271 ${lock directory}/*tdb before upgrading to Samba 3.0. Samba will
272 upgrade databases as they are opened (if necessary), but downgrading
273 from 3.0 to 2.2 is an unsupported path.
277 <table frame='all'><title>TDB File Descriptions</title>
279 <colspec align="left"/>
280 <colspec align="justify"/>
281 <colspec align="left"/>
284 <entry align="left">Name</entry>
285 <entry align="justify">Description</entry>
286 <entry align="center">Backup?</entry>
291 <entry>account_policy</entry>
292 <entry>User policy settings</entry>
296 <entry>gencache</entry>
297 <entry>Generic caching db</entry>
301 <entry>group_mapping</entry>
302 <entry><para>Mapping table from Windows groups/SID to unix groups</para></entry>
307 <entry><para>new ID map table from SIDS to UNIX uids/gids</para></entry>
311 <entry>namecache</entry>
312 <entry>Name resolution cache entries</entry>
316 <entry>netlogon_unigrp</entry>
317 <entry><para>Cache of universal group membership obtained when operating
318 as a member of a Windows domain</para></entry>
322 <entry>printing/*.tdb</entry>
323 <entry><para>Cached output from 'lpq command' created on a per print
324 service basis</para></entry>
329 <entry>registry</entry>
330 <entry><para>Read-only samba registry skeleton that provides support for
331 exporting various db tables via the winreg RPCs</para></entry>
341 <title>Changes in Behavior</title>
344 The following issues are known changes in behavior between Samba 2.2 and
345 Samba 3.0 that may affect certain installations of Samba.
350 When operating as a member of a Windows domain, Samba 2.2 would
351 map any users authenticated by the remote DC to the 'guest account'
352 if a uid could not be obtained via the getpwnam() call. Samba 3.0
353 rejects the connection as NT_STATUS_LOGON_FAILURE. There is no
354 current work around to re-establish the 2.2 behavior.
358 When adding machines to a Samba 2.2 controlled domain, the
359 'add user script' was used to create the UNIX identity of the
360 machine trust account. Samba 3.0 introduces a new 'add machine
361 script' that must be specified for this purpose. Samba 3.0 will
362 not fall back to using the 'add user script' in the absence of
363 an 'add machine script'
370 <title>Charsets</title>
373 You might experience problems with special characters when communicating with old DOS
374 clients. Codepage support has changed in samba 3.0. Read the chapter
375 <link linkend="unicode">Unicode support</link> for details.
381 <title>Passdb Backends and Authentication</title>
384 There have been a few new changes that Samba administrators should be
385 aware of when moving to Samba 3.0.
390 Encrypted passwords have been enabled by default in order to
391 inter-operate better with out-of-the-box Windows client
392 installations. This does mean that either (a) a samba account
393 must be created for each user, or (b) 'encrypt passwords = no'
394 must be explicitly defined in smb.conf.
398 Inclusion of new <smbconfoption><name>security</name><value>ads</value></smbconfoption> option for integration
399 with an Active Directory domain using the native Windows
400 Kerberos 5 and LDAP protocols.
405 Samba 3.0 also includes the possibility of setting up chains
406 of authentication methods
407 (<smbconfoption><name>auth methods</name></smbconfoption>) and account
409 (<smbconfoption><name>passdb backend</name></smbconfoption>).
410 Please refer to the &smb.conf;
411 man page and <link linkend="passdb"/> for details. While both parameters assume sane default
412 values, it is likely that you will need to understand what the
413 values actually mean in order to ensure Samba operates correctly.
417 Certain functions of the smbpasswd(8) tool have been split between the
418 new smbpasswd(8) utility, the net(8) tool, and the new pdbedit(8)
419 utility. See the respective man pages for details.
425 <title>Charsets</title>
428 You might experience problems with special characters when communicating with old DOS
429 clients. Codepage support has changed in samba 3.0. Read the chapter
430 <link linkend="unicode">Unicode support</link> for details.
439 This section outlines the new features affecting Samba / LDAP integration.
443 <title>New Schema</title>
446 A new object class (sambaSamAccount) has been introduced to replace
447 the old sambaAccount. This change aids us in the renaming of attributes
448 to prevent clashes with attributes from other vendors. There is a
449 conversion script (examples/LDAP/convertSambaAccount) to modify and LDIF
450 file to the new schema.
457 &prompt;ldapsearch .... -b "ou=people,dc=..." > old.ldif
458 &prompt;convertSambaAccount <DOM SID> old.ldif new.ldif
462 The <DOM SID> can be obtained by running 'net getlocalsid <DOMAINNAME>
463 on the Samba PDC as root.
467 The old sambaAccount schema may still be used by specifying the
468 "ldapsam_compat" passdb backend. However, the sambaAccount and
469 associated attributes have been moved to the historical section of
470 the schema file and must be uncommented before use if needed.
471 The 2.2 object class declaration for a sambaAccount has not changed
472 in the 3.0 samba.schema file.
476 Other new object classes and their uses include:
481 sambaDomain - domain information used to allocate rids
482 for users and groups as necessary. The attributes are added
483 in 'ldap suffix' directory entry automatically if
484 an idmap uid/gid range has been set and the 'ldapsam'
485 passdb backend has been selected.
489 sambaGroupMapping - an object representing the
490 relationship between a posixGroup and a Windows
491 group/SID. These entries are stored in the 'ldap
492 group suffix' and managed by the 'net groupmap' command.
496 sambaUnixIdPool - created in the 'ldap idmap suffix' entry
497 automatically and contains the next available 'idmap uid' and
502 sambaIdmapEntry - object storing a mapping between a
503 SID and a UNIX uid/gid. These objects are created by the
504 idmap_ldap module as needed.
511 <title>New Suffix for Searching</title>
514 The following new smb.conf parameters have been added to aid in directing
515 certain LDAP queries when 'passdb backend = ldapsam://...' has been
520 <listitem><para>ldap suffix - used to search for user and computer accounts</para></listitem>
521 <listitem><para>ldap user suffix - used to store user accounts</para></listitem>
522 <listitem><para>ldap machine suffix - used to store machine trust accounts</para></listitem>
523 <listitem><para>ldap group suffix - location of posixGroup/sambaGroupMapping entries</para></listitem>
524 <listitem><para>ldap idmap suffix - location of sambaIdmapEntry objects</para></listitem>
528 If an 'ldap suffix' is defined, it will be appended to all of the
529 remaining sub-suffix parameters. In this case, the order of the suffix
530 listings in smb.conf is important. Always place the 'ldap suffix' first
535 Due to a limitation in Samba's smb.conf parsing, you should not surround
536 the DN's with quotation marks.
542 <title>IdMap LDAP support</title>
545 Samba 3.0 supports an ldap backend for the idmap subsystem. The
546 following options would inform Samba that the idmap table should be
547 stored on the directory server onterose in the "ou=idmap,dc=plainjoe,
552 <smbconfsection>[global]</smbconfsection>
554 <smbconfoption><name>idmap backend</name><value>ldap:ldap://onterose/</value></smbconfoption>
555 <smbconfoption><name>ldap idmap suffix</name><value>ou=idmap,dc=plainjoe,dc=org</value></smbconfoption>
556 <smbconfoption><name>idmap uid</name><value>40000-50000</value></smbconfoption>
557 <smbconfoption><name>idmap gid</name><value>40000-50000</value></smbconfoption>
561 This configuration allows winbind installations on multiple servers to
562 share a uid/gid number space, thus avoiding the interoperability problems
563 with NFS that were present in Samba 2.2.