More stuffing, this turkey will soon be done.

(This used to be commit 4c1c75ae224eb138a71058472b25f9c22b61b349)

diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.xml b/docs/docbook/projdoc/Samba-PDC-HOWTO.xml
index fa479d73aef6d8452cbe9c39d9ef19f6cdc8e613..39d8eb6fc57cff8e326867f3ebd9a40b16a772ea 100644 (file)
--- a/docs/docbook/projdoc/Samba-PDC-HOWTO.xml
+++ b/docs/docbook/projdoc/Samba-PDC-HOWTO.xml
@@ -287,6 +287,22 @@ be revised to duely reflect all configuration and management requirements.
 <sect2>
 <title>Preparing for Domain Control</title>
 
+<para>
+There are two ways that MS Windows machines may interact with each other, with other servers,
+and with Domain Controllers: Either as <empahsis>Stand-Alone</emphasis> systems, more commonly
+called <empasis>Workgroup members</emphasis>, or as full participants in a security system,
+more commonly called <emphasis>Domain Members</emphasis>.
+</para>
+
+<para>
+It should be noted that <emphasis>Workgroup membership</emphasis> involve no special configuration
+other than the machine being configured so that the network configuration has a commonly used name
+for it's workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this
+mode of configuration there are NO machine trust accounts and any concept of "membership" as such
+is limited to the fact that all machines appear in the network neighbourhood to be logically
+groupped together.
+</para>
+
 <para>
 The following are necessary for configuring Samba-3 as an MS Windows NT4 style PDC for MS Windows
 NT4 / 200x / XP clients.