diff options
| author | John Terpstra <jht@samba.org> | 2005-04-14 08:45:39 +0000 |
|---|---|---|
| committer | Gerald W. Carter <jerry@samba.org> | 2008-04-23 08:46:27 -0500 |
| commit | 5176976f679d4454b9bb268b88992db76f24e3e6 (patch) | |
| tree | 40cb1fb34080ff47fa337faeb15cb005b4f5d37c /docs/Samba-Guide | |
| parent | ee196f0e3bba1f619549278977522aca918adfc2 (diff) | |
| download | samba-5176976f679d4454b9bb268b88992db76f24e3e6.tar.gz samba-5176976f679d4454b9bb268b88992db76f24e3e6.tar.bz2 samba-5176976f679d4454b9bb268b88992db76f24e3e6.zip | |
Another update.
(This used to be commit 2d9d6e99073f67341c5fe0f10d13b7ff9ee39a22)
Diffstat (limited to 'docs/Samba-Guide')
| -rw-r--r-- | docs/Samba-Guide/SBE-UpgradingSamba.xml | 43 |
1 files changed, 41 insertions, 2 deletions
diff --git a/docs/Samba-Guide/SBE-UpgradingSamba.xml b/docs/Samba-Guide/SBE-UpgradingSamba.xml index db3a4b72f9..192a4d51cc 100644 --- a/docs/Samba-Guide/SBE-UpgradingSamba.xml +++ b/docs/Samba-Guide/SBE-UpgradingSamba.xml @@ -797,7 +797,7 @@ the procedure outlined above. </sect3> - <sect2> + <sect3> <title>Updating from Samba Versions between 3.0.6 and 3.0.10</title> <para> @@ -856,15 +856,54 @@ back to searching the 'ldap suffix' in some cases. </para> </sect3> - </sect2> <sect2> <title>Migrating Samba-3 to a New Server</title> <para> + The two most likely candidates for replacement of a server are + domain member servers and domain controllers. Each needs to be + handled slightly differently. + </para> + + <sect3> + <title>Replacing a Domain Member Server</title> + + <para> + Replacement of a domain member server (DMS) should be done + using the same procedure as outlined in <link linkend="unixclients"/>. + </para> + + <para> + Usually the new server will be introduced with a temporary name. After + the old server data has been migrated to the new server it is customary + that the new server will be renamed to that of the old server. This will + change its SID and will necessitate re-joining to the domain. </para> + <para> + Following a change of hostname (netbios name) it is a good idea on all servers to + shutdown the Samba <command>smbd, nmbd</command> and <command>winbindd</command> + services, delete the <filename>wins.dat</filename> and <filename>browse.dat</filename> + files, then restart Samba. This will ensure that the old name and IP address + information is no longer able to interfere with name to IP address resolution. + If this is not done, there can be temporary name resolution problems. These + problems usually clear within 45 minutes of a name change, but can persist for + a longer period of time. + </para> + + </sect3> + + <sect3> + <title>Replacing a Domain Controller</title> + + <para> + This information will be added within 24 hours. JJJ. + </para> + + </sect3> + </sect2> <sect2> |