Update as a result of major surgery.

(This used to be commit a2fe0f409e4ab1c33fa2ae43a8594f3944ad3e31)

1 files changed, 39 insertions, 1 deletions

diff --git a/docs/Samba-Guide/SBE-UpgradingSamba.xml b/docs/Samba-Guide/SBE-UpgradingSamba.xml
index 23507e722a..0100a34aa5 100644
--- a/docs/Samba-Guide/SBE-UpgradingSamba.xml
+++ b/docs/Samba-Guide/SBE-UpgradingSamba.xml
@@ -221,6 +221,22 @@ precaution was on the side of the victor.
 	</para></note>
 
 	<para>
+	<indexterm><primary>domain controller</primary></indexterm>
+	<indexterm><primary>PDC</primary></indexterm>
+	<indexterm><primary>BDC</primary></indexterm>
+	<indexterm><primary>domain SID</primary></indexterm>
+	<indexterm><primary>hostname</primary></indexterm>
+	<indexterm><primary>computer name</primary></indexterm>
+	<indexterm><primary>netbios name</primary></indexterm>
+	<indexterm><primary>stand-alone server</primary></indexterm>
+	<indexterm><primary>SAS</primary></indexterm>
+	<indexterm><primary>SID</primary></indexterm>
+	In Samba-3 on a domain controller (PDC or BDC), the domain name controls the domain
+	SID. On all prior versions the hostname (computer name, or netbios name) controlled
+	the SID. On a stand-alone server (SAS) the hostname still controls the SID.
+	</para>
+
+	<para>
 	<indexterm><primary>net</primary><secondary>getlocalsid</secondary></indexterm>
 	<indexterm><primary>net</primary><secondary>setlocalsid</secondary></indexterm>
 	The local machine SID can be backed up using this procedure (Samba-3):
@@ -373,6 +389,13 @@ Num local groups: 0
 	<title>Location of config files</title>
 
 	<para>
+	The Samba-Team has maintained a constant default location for all Samba control files
+	throughout the life of the project. People who have produced binary packages of Samba
+	have varied the location of the Samba control files. This has led to some confusion
+	for network administrators.
+	</para>
+
+	<para>
 	<indexterm><primary>directory</primary></indexterm>
 	The Samba 1.9.x &smb.conf; file may be found either in the <filename>/etc</filename>
 	directory or in <filename>/usr/local/samba/lib</filename>.
@@ -1102,9 +1125,24 @@ back to searching the 'ldap suffix' in some cases.
 		preserve all file ownership and permissions as well as any POSIX ACLs that
 		may have been created on the old server.
 		</para></listitem>
-
 	</itemizedlist>
 
+	<para>
+	When replacing a Samba domain controller (PDC or BDC) that uses LDAP, the new server
+	need simply be configured to use the LDAP directory, and for the rest it should just
+	work. The domain SID is obtained from the LDAP directory as part of the first connect
+	to the LDAP directory server.
+	</para>
+
+	<para>
+	All Samba servers, other than one that uses LDAP, depend on the tdb files, and in
+	particular the <filename>secrets.tdb</filename> file. So long as the tdb files are
+	all in place, the &smb.conf; file is preserved, and either the hostname is identical
+	or the <parameter>netbios name</parameter> is set to the original server name, Samba
+	should correctly pick up the original SID, and preserve all other settings. It is
+	sound advice to validate this before turning the system over to users.
+	</para>
+
 	</sect3>
 
 	</sect2>