From f0bf4b1f535020927251ebb4d9c5a473ab6ccaf0 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 6 May 2003 23:57:37 +0000 Subject: More stuffing, this turkey will soon be done. (This used to be commit 4c1c75ae224eb138a71058472b25f9c22b61b349) --- docs/docbook/projdoc/Samba-PDC-HOWTO.xml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'docs/docbook/projdoc') diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.xml b/docs/docbook/projdoc/Samba-PDC-HOWTO.xml index fa479d73ae..39d8eb6fc5 100644 --- 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. Preparing for Domain Control + +There are two ways that MS Windows machines may interact with each other, with other servers, +and with Domain Controllers: Either as Stand-Alone systems, more commonly +called Workgroup members, or as full participants in a security system, +more commonly called Domain Members. + + + +It should be noted that Workgroup membership 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. + + The following are necessary for configuring Samba-3 as an MS Windows NT4 style PDC for MS Windows NT4 / 200x / XP clients. -- cgit