upgrading-to-3.0.html [plain text]
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.61.2"><link rel="home" href="index.html" title="Samba HOWTO Collection"><link rel="up" href="migration.html" title="Part IV. Migration and Updating"><link rel="previous" href="migration.html" title="Part IV. Migration and Updating"><link rel="next" href="NT4Migration.html" title="Chapter 31. Migration from NT4 PDC to Samba-3 PDC"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="migration.html">Prev</a> </td><th width="60%" align="center">Part IV. Migration and Updating</th><td width="20%" align="right"> <a accesskey="n" href="NT4Migration.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="upgrading-to-3.0"></a>Chapter 30. Upgrading from Samba-2.x to Samba-3.0.0</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">June 30, 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="upgrading-to-3.0.html#id2968933">Quick Migration Guide</a></dt><dt><a href="upgrading-to-3.0.html#id2969045">New Features in Samba-3</a></dt><dt><a href="upgrading-to-3.0.html#id2969204">Configuration Parameter Changes</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2969226">Removed Parameters</a></dt><dt><a href="upgrading-to-3.0.html#id2969358">New Parameters</a></dt><dt><a href="upgrading-to-3.0.html#id2969774">Modified Parameters (Changes in Behavior):</a></dt></dl></dd><dt><a href="upgrading-to-3.0.html#id2969855">New Functionality</a></dt><dd><dl><dt><a href="upgrading-to-3.0.html#id2969862">Databases</a></dt><dt><a href="upgrading-to-3.0.html#id2970117">Changes in Behavior</a></dt><dt><a href="upgrading-to-3.0.html#id2970194">Passdb Backends and Authentication</a></dt><dt><a href="upgrading-to-3.0.html#id2970343">LDAP</a></dt></dl></dd></dl></div><p>
This chapter deals exclusively with the differences between Samba-3.0.0 and Samba-2.2.8a.
It points out where configuration parameters have changed, and provides a simple guide for
the move from 2.2.x to 3.0.0.
</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2968933"></a>Quick Migration Guide</h2></div></div><div></div></div><p>
Samba-3.0.0 default behavior should be approximately the same as Samba-2.2.x.
The default behavior when the new parameter <a class="indexterm" name="id2968946"></a>passdb backend
is not defined in the <tt class="filename">smb.conf</tt> file provides the same default behavior as Samba-2.2.x
with <a class="indexterm" name="id2968963"></a>encrypt passwords = Yes, and
will use the <tt class="filename">smbpasswd</tt> database.
</p><p>
So why say that <span class="emphasis"><em>behavior should be approximately the same as Samba-2.2.x?</em></span> Because
Samba-3.0.0 can negotiate new protocols, such as support for native Unicode, that may result in
differing protocol code paths being taken. The new behavior under such circumstances is not
exactly the same as the old one. The good news is that the domain and machine SIDs will be
preserved across the upgrade.
</p><p>
If the Samba-2.2.x system was using an LDAP backend, and there is no time to update the LDAP
database, then make sure that <a class="indexterm" name="id2969001"></a>passdb backend = ldapsam_compat
is specified in the <tt class="filename">smb.conf</tt> file. For the rest, behavior should remain more or less the same.
At a later date, when there is time to implement a new Samba-3 compatible LDAP backend, it is possible
to migrate the old LDAP database to the new one through use of the <b class="command">pdbedit</b>.
See <a href="passdb.html#pdbeditthing" title="The pdbedit Command">The <span class="emphasis"><em>pdbedit</em></span> Command</a>.
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969045"></a>New Features in Samba-3</h2></div></div><div></div></div><p>
The major new features are:
</p><div class="orderedlist"><ol type="1"><li><p>
Active Directory support. This release is able to join an ADS realm
as a member server and authenticate users using LDAP/Kerberos.
</p></li><li><p>
Unicode support. Samba will now negotiate Unicode on the wire and
internally there is a much better infrastructure for multi-byte
and Unicode character sets.
</p></li><li><p>
New authentication system. The internal authentication system has
been almost completely rewritten. Most of the changes are internal,
but the new authoring system is also very configurable.
</p></li><li><p>
New filename mangling system. The filename mangling system has been
completely rewritten. An internal database now stores mangling maps
persistently.
</p></li><li><p>
New “<span class="quote"><span class="emphasis"><em>net</em></span></span>” command. A new “<span class="quote"><span class="emphasis"><em>net</em></span></span>” command has been added. It is
somewhat similar to the “<span class="quote"><span class="emphasis"><em>net</em></span></span>” command in Windows. Eventually, we
plan to replace a bunch of other utilities (such as smbpasswd)
with subcommands in “<span class="quote"><span class="emphasis"><em>net</em></span></span>”.
</p></li><li><p>
Samba now negotiates NT-style status32 codes on the wire. This
considerably improves error handling.
</p></li><li><p>
Better Windows 200x/XP printing support including publishing
printer attributes in Active Directory.
</p></li><li><p>
New loadable RPC modules for passdb backends and character sets.
</p></li><li><p>
New default dual-daemon winbindd support for better performance.
</p></li><li><p>
Support for migrating from a Windows NT 4.0 domain to a Samba
domain and maintaining user, group and domain SIDs.
</p></li><li><p>
Support for establishing trust relationships with Windows NT 4.0
Domain Controllers.
</p></li><li><p>
Initial support for a distributed Winbind architecture using
an LDAP directory for storing SID to UID/GID mappings.
</p></li><li><p>
Major updates to the Samba documentation tree.
</p></li><li><p>
Full support for client and server SMB signing to ensure
compatibility with default Windows 2003 security settings.
</p></li></ol></div><p>
Plus lots of other improvements!
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969204"></a>Configuration Parameter Changes</h2></div></div><div></div></div><p>
This section contains a brief listing of changes to <tt class="filename">smb.conf</tt> options
in the 3.0.0 release. Please refer to the smb.conf(5) man page for
complete descriptions of new or modified parameters.
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969226"></a>Removed Parameters</h3></div></div><div></div></div><p>(Ordered Alphabetically):</p><div class="itemizedlist"><ul type="disc"><li><p>admin log </p></li><li><p>alternate permissions </p></li><li><p>character set </p></li><li><p>client codepage </p></li><li><p>code page directory </p></li><li><p>coding system </p></li><li><p>domain admin group </p></li><li><p>domain guest group </p></li><li><p>force unknown acl user </p></li><li><p>nt smb support </p></li><li><p>post script </p></li><li><p>printer driver </p></li><li><p>printer driver file </p></li><li><p>printer driver location </p></li><li><p>status </p></li><li><p>stip dot </p></li><li><p>total print jobs </p></li><li><p>use rhosts </p></li><li><p>valid chars </p></li><li><p>vfs options </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969358"></a>New Parameters</h3></div></div><div></div></div><p>(New parameters have been grouped by function):</p><p>Remote Management</p><div class="itemizedlist"><ul type="disc"><li><p>abort shutdown script </p></li><li><p>shutdown script </p></li></ul></div><p>User and Group Account Management:</p><div class="itemizedlist"><ul type="disc"><li><p>add group script </p></li><li><p>add machine script </p></li><li><p>add user to group script </p></li><li><p>algorithmic rid base </p></li><li><p>delete group script </p></li><li><p>delete user from group script </p></li><li><p>passdb backend </p></li><li><p>set primary group script </p></li></ul></div><p>Authentication:</p><div class="itemizedlist"><ul type="disc"><li><p>auth methods </p></li><li><p>realm </p></li></ul></div><p>Protocol Options:</p><div class="itemizedlist"><ul type="disc"><li><p>client lanman auth </p></li><li><p>client NTLMv2 auth </p></li><li><p>client schannel </p></li><li><p>client signing </p></li><li><p>client use spnego </p></li><li><p>disable netbios </p></li><li><p>ntlm auth </p></li><li><p>paranoid server security </p></li><li><p>server schannel </p></li><li><p>server signing </p></li><li><p>smb ports </p></li><li><p>use spnego </p></li></ul></div><p>File Service:</p><div class="itemizedlist"><ul type="disc"><li><p>get quota command </p></li><li><p>hide special files </p></li><li><p>hide unwritable files </p></li><li><p>hostname lookups </p></li><li><p>kernel change notify </p></li><li><p>mangle prefix </p></li><li><p>map acl inherit </p></li><li><p>msdfs proxy </p></li><li><p>set quota command </p></li><li><p>use sendfile </p></li><li><p>vfs objects </p></li></ul></div><p>Printing:</p><div class="itemizedlist"><ul type="disc"><li><p>max reported print jobs </p></li></ul></div><p>Unicode and Character Sets:</p><div class="itemizedlist"><ul type="disc"><li><p>display charset </p></li><li><p>dos charset </p></li><li><p>unicode </p></li><li><p>UNIX charset </p></li></ul></div><p>SID to UID/GID Mappings:</p><div class="itemizedlist"><ul type="disc"><li><p>idmap backend </p></li><li><p>idmap gid </p></li><li><p>idmap uid </p></li><li><p>winbind enable local accounts </p></li><li><p>winbind trusted domains only </p></li><li><p>template primary group </p></li><li><p>enable rid algorithm </p></li></ul></div><p>LDAP:</p><div class="itemizedlist"><ul type="disc"><li><p>ldap delete dn </p></li><li><p>ldap group suffix </p></li><li><p>ldap idmap suffix </p></li><li><p>ldap machine suffix </p></li><li><p>ldap passwd sync </p></li><li><p>ldap user suffix </p></li></ul></div><p>General Configuration:</p><div class="itemizedlist"><ul type="disc"><li><p>preload modules </p></li><li><p>privatedir </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969774"></a>Modified Parameters (Changes in Behavior):</h3></div></div><div></div></div><div class="itemizedlist"><ul type="disc"><li><p>encrypt passwords (enabled by default) </p></li><li><p>mangling method (set to hash2 by default) </p></li><li><p>passwd chat </p></li><li><p>passwd program </p></li><li><p>password server </p></li><li><p>restrict anonymous (integer value) </p></li><li><p>security (new ads value) </p></li><li><p>strict locking (enabled by default) </p></li><li><p>winbind cache time (increased to 5 minutes) </p></li><li><p>winbind uid (deprecated in favor of idmap uid) </p></li><li><p>winbind gid (deprecated in favor of idmap gid) </p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2969855"></a>New Functionality</h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2969862"></a>Databases</h3></div></div><div></div></div><p>
This section contains brief descriptions of any new databases
introduced in Samba-3. Please remember to backup your existing
${lock directory}/*tdb before upgrading to Samba-3. Samba will
upgrade databases as they are opened (if necessary), but downgrading
from 3.0 to 2.2 is an unsupported path.
</p><p>
The new tdb files are described in <a href="upgrading-to-3.0.html#tdbfiledesc" title="Table 30.1. TDB File Descriptions">the next table</a>.
</p><div class="table"><a name="tdbfiledesc"></a><p class="title"><b>Table 30.1. TDB File Descriptions</b></p><table summary="TDB File Descriptions" border="1"><colgroup><col align="left"><col align="justify"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="justify">Description</th><th align="center">Backup?</th></tr></thead><tbody><tr><td align="left">account_policy</td><td align="justify">User policy settings</td><td align="left">yes</td></tr><tr><td align="left">gencache</td><td align="justify">Generic caching db</td><td align="left">no</td></tr><tr><td align="left">group_mapping</td><td align="justify"><p>Mapping table from Windows groups/SID to UNIX groups</p></td><td align="left">yes</td></tr><tr><td align="left">idmap</td><td align="justify"><p>new ID map table from SIDS to UNIX UIDs/GIDs</p></td><td align="left">yes</td></tr><tr><td align="left">namecache</td><td align="justify">Name resolution cache entries</td><td align="left">no</td></tr><tr><td align="left">netlogon_unigrp</td><td align="justify"><p>Cache of universal group membership obtained when operating
as a member of a Windows domain</p></td><td align="left">no</td></tr><tr><td align="left">printing/*.tdb</td><td align="justify"><p>Cached output from `lpq command' created on a per print
service basis</p></td><td align="left">no</td></tr><tr><td align="left">registry</td><td align="justify"><p>Read-only Samba registry skeleton that provides support for
exporting various db tables via the winreg RPCs</p></td><td align="left">no</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2970117"></a>Changes in Behavior</h3></div></div><div></div></div><p>
The following issues are known changes in behavior between Samba-2.2 and
Samba-3 that may affect certain installations of Samba.
</p><div class="orderedlist"><ol type="1"><li><p>
When operating as a member of a Windows domain, Samba-2.2 would
map any users authenticated by the remote DC to the “<span class="quote"><span class="emphasis"><em>guest account</em></span></span>”
if a uid could not be obtained via the getpwnam() call. Samba-3
rejects the connection as NT_STATUS_LOGON_FAILURE. There is no
current work around to re-establish the Samba-2.2 behavior.
</p></li><li><p>
When adding machines to a Samba-2.2 controlled domain, the
“<span class="quote"><span class="emphasis"><em>add user script</em></span></span>” was used to create the UNIX identity of the
Machine Trust Account. Samba-3 introduces a new “<span class="quote"><span class="emphasis"><em>add machine
script</em></span></span>” that must be specified for this purpose. Samba-3 will
not fall back to using the “<span class="quote"><span class="emphasis"><em>add user script</em></span></span>” in the absence of
an “<span class="quote"><span class="emphasis"><em>add machine script</em></span></span>”.
</p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2970194"></a>Passdb Backends and Authentication</h3></div></div><div></div></div><p>
There have been a few new changes that Samba administrators should be
aware of when moving to Samba-3.
</p><div class="orderedlist"><ol type="1"><li><p>
Encrypted passwords have been enabled by default in order to
interoperate better with out-of-the-box Windows client
installations. This does mean that either (a) a Samba account
must be created for each user, or (b) “<span class="quote"><span class="emphasis"><em>encrypt passwords = no</em></span></span>”
must be explicitly defined in <tt class="filename">smb.conf</tt>.
</p></li><li><p>
Inclusion of new <a class="indexterm" name="id2970244"></a>security = ads option for integration
with an Active Directory domain using the native Windows Kerberos 5 and LDAP protocols.
</p></li></ol></div><p>
Samba-3 also includes the possibility of setting up chains
of authentication methods
(<a class="indexterm" name="id2970262"></a>auth methods) and account
storage backends
(<a class="indexterm" name="id2970271"></a>passdb backend).
Please refer to the <tt class="filename">smb.conf</tt>
man page and <a href="passdb.html" title="Chapter 11. Account Information Databases">Account Information Databases</a>, for details. While both parameters assume sane default
values, it is likely that you will need to understand what the
values actually mean in order to ensure Samba operates correctly.
</p><p>
<a class="indexterm" name="id2970305"></a>
Certain functions of the <b class="command">smbpasswd</b> tool have been split between the
new <b class="command">smbpasswd</b> utility, the <b class="command">net</b> tool and the new <b class="command">pdbedit</b>
utility. See the respective man pages for details.
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2970343"></a>LDAP</h3></div></div><div></div></div><p>
This section outlines the new features effecting Samba/LDAP integration.
</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2970356"></a>New Schema</h4></div></div><div></div></div><p>
A new object class (sambaSamAccount) has been introduced to replace
the old sambaAccount. This change aids us in the renaming of attributes
to prevent clashes with attributes from other vendors. There is a
conversion script (examples/LDAP/convertSambaAccount) to modify an LDIF
file to the new schema.
</p><p>
Example:
</p><pre class="screen">
<tt class="prompt">$ </tt>ldapsearch .... -LLL -b "ou=people,dc=..." > old.ldif
<tt class="prompt">$ </tt>convertSambaAccount --sid <DOM SID> --input old.ldif --output new.ldif
</pre><p>
The <DOM SID> can be obtained by running
</p><pre class="screen">
<tt class="prompt">$ </tt><b class="userinput"><tt>net getlocalsid <DOMAINNAME></tt></b>
</pre><p>
on the Samba PDC as root.
</p><p>
The old sambaAccount schema may still be used by specifying the
<i class="parameter"><tt>ldapsam_compat</tt></i> passdb backend. However, the sambaAccount and
associated attributes have been moved to the historical section of
the schema file and must be uncommented before use if needed.
The Samba-2.2 object class declaration for a sambaAccount has not changed
in the Samba-3 samba.schema file.
</p><p>
Other new object classes and their uses include:
</p><div class="itemizedlist"><ul type="disc"><li><p>
sambaDomain domain information used to allocate RIDs
for users and groups as necessary. The attributes are added
in “<span class="quote"><span class="emphasis"><em>ldap suffix</em></span></span>” directory entry automatically if
an idmap UID/GID range has been set and the “<span class="quote"><span class="emphasis"><em>ldapsam</em></span></span>”
passdb backend has been selected.
</p></li><li><p>
sambaGroupMapping an object representing the
relationship between a posixGroup and a Windows
group/SID. These entries are stored in the “<span class="quote"><span class="emphasis"><em>ldap
group suffix</em></span></span>” and managed by the “<span class="quote"><span class="emphasis"><em>net groupmap</em></span></span>” command.
</p></li><li><p>
sambaUNIXIdPool created in the “<span class="quote"><span class="emphasis"><em>ldap idmap suffix</em></span></span>” entry
automatically and contains the next available “<span class="quote"><span class="emphasis"><em>idmap UID</em></span></span>” and
“<span class="quote"><span class="emphasis"><em>idmap GID</em></span></span>”.
</p></li><li><p>
sambaIdmapEntry object storing a mapping between a
SID and a UNIX UID/GID. These objects are created by the
idmap_ldap module as needed.
</p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2970545"></a>New Suffix for Searching</h4></div></div><div></div></div><p>
The following new smb.conf parameters have been added to aid in directing
certain LDAP queries when <i class="parameter"><tt>passdb backend = ldapsam://...</tt></i> has been
specified.
</p><div class="itemizedlist"><ul type="disc"><li><p>ldap suffix used to search for user and computer accounts.</p></li><li><p>ldap user suffix used to store user accounts.</p></li><li><p>ldap machine suffix used to store Machine Trust Accounts.</p></li><li><p>ldap group suffix location of posixGroup/sambaGroupMapping entries.</p></li><li><p>ldap idmap suffix location of sambaIdmapEntry objects.</p></li></ul></div><p>
If an <i class="parameter"><tt>ldap suffix</tt></i> is defined, it will be appended to all of the
remaining sub-suffix parameters. In this case, the order of the suffix
listings in smb.conf is important. Always place the <i class="parameter"><tt>ldap suffix</tt></i> first
in the list.
</p><p>
Due to a limitation in Samba's <tt class="filename">smb.conf</tt> parsing, you should not surround
the DNs with quotation marks.
</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2970654"></a>IdMap LDAP Support</h4></div></div><div></div></div><p>
Samba-3 supports an ldap backend for the idmap subsystem. The
following options inform Samba that the idmap table should be
stored on the directory server onterose in the "ou=idmap,dc=quenya,dc=org" partition.
</p><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><i class="parameter"><tt>[global]</tt></i></td></tr><tr><td>...</td></tr><tr><td><i class="parameter"><tt>
idmap backend = ldap:ldap://onterose/</tt></i></td></tr><tr><td><i class="parameter"><tt>
ldap idmap suffix = ou=idmap,dc=quenya,dc=org</tt></i></td></tr><tr><td><i class="parameter"><tt>
idmap uid = 40000-50000</tt></i></td></tr><tr><td><i class="parameter"><tt>
idmap gid = 40000-50000</tt></i></td></tr></table><p>
This configuration allows Winbind installations on multiple servers to
share a UID/GID number space, thus avoiding the interoperability problems
with NFS that were present in Samba-2.2.
</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="migration.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="migration.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="NT4Migration.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Part IV. Migration and Updating </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 31. Migration from NT4 PDC to Samba-3 PDC</td></tr></table></div></body></html>