Changeset 988 for vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml

Timestamp:

Nov 24, 2016, 1:14:11 PM (9 years ago)

Author:

Silvan Scherrer

Message:

Samba Server: update vendor to version 4.4.3

File:

• vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml (modified) (9 diffs)

vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml

@@ -18 +18 @@
 The Microsoft Windows operating system has a number of features that impose specific challenges
 to interoperability with the operating systems on which Samba is implemented. This chapter deals
-explicitly with the mechanisms Samba-3 (version 3.0.8 and later) uses to overcome one of the
+explicitly with the mechanisms Samba (version 3.0.8 and later) uses to overcome one of the
 key challenges in the integration of Samba servers into an MS Windows networking environment.
 This chapter deals with identity mapping (IDMAP) of Windows security identifiers (SIDs)
@@ -121 +121 @@
         <indexterm><primary>SID</primary></indexterm>
         <indexterm><primary>Active Directory</primary></indexterm>
-        Samba-3 can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that
-        are compatible with Windows NT4. Samba-3 file and print sharing protocols are compatible with
+        Samba can act as a Windows NT4 PDC or BDC, thereby providing domain control protocols that
+        are compatible with Windows NT4. Samba file and print sharing protocols are compatible with
         all versions of MS Windows products. Windows NT4, as with MS Active Directory,
         extensively makes use of Windows SIDs.
@@ -131 +131 @@
         <indexterm><primary>UID</primary></indexterm>
         <indexterm><primary>GID</primary></indexterm>
-        Samba-3 domain member servers and clients must interact correctly with MS Windows SIDs. Incoming
+        Samba domain member servers and clients must interact correctly with MS Windows SIDs. Incoming
         Windows SIDs must be translated to local UNIX UIDs and GIDs. Outgoing information from the Samba
         server must provide to MS Windows clients and servers appropriate SIDs.
@@ -236 +236 @@
                                 is an appliance like file server on which no local accounts are configured and
                                 winbind is used to obtain account credentials from the domain controllers for the
-                                domain. The domain control can be provided by Samba-3, MS Windows NT4, or MS Windows
+                                domain. The domain control can be provided by Samba, MS Windows NT4, or MS Windows
                                 Active Directory.
                                 </para>
@@ -453 +453 @@
         <para>
         IDMAP information can be written directly to the LDAP server so long as all domain controllers
-        have access to the master (writable) LDAP server. Samba-3 at this time does not handle LDAP redirects
+        have access to the master (writable) LDAP server. Samba at this time does not handle LDAP redirects
         in the IDMAP backend. This means that it is is unsafe to use a slave (replicate) LDAP server with
         the IDMAP facility.
@@ -596 +596 @@
 <smbconfoption name="winbind use default domain">Yes</smbconfoption>
 <smbconfoption name="winbind nested groups">Yes</smbconfoption>
-<smbconfoption name="printer admin">"BUTTERNET\Domain Admins"</smbconfoption>
 </smbconfblock>
 </example>
@@ -729 +728 @@
 <smbconfoption name="winbind enum groups">No</smbconfoption>
 <smbconfoption name="winbind nested groups">Yes</smbconfoption>
-<smbconfoption name="printer admin">"Domain Admins"</smbconfoption>
 </smbconfblock>
 </example>
@@ -822 +820 @@
         <indexterm><primary>ADAM</primary></indexterm>
         <indexterm><primary>ADS</primary></indexterm>
-        The storage of IDMAP information in LDAP can be used with both NT4/Samba-3-style domains and
+        The storage of IDMAP information in LDAP can be used with both NT4/Samba-style domains and
         ADS domains. OpenLDAP is a commonly used LDAP server for this purpose, although any
         standards-complying LDAP server can be used. It is therefore possible to deploy this IDMAP
@@ -858 +856 @@
         <para>
         <indexterm><primary>realm</primary></indexterm>
-        In the case of an NT4 or Samba-3-style domain the <parameter>realm</parameter> is not used, and the
+        In the case of an NT4 or Samba-style domain the <parameter>realm</parameter> is not used, and the
         command used to join the domain is <command>net rpc join</command>. The above example also demonstrates
         advanced error-reporting techniques that are documented in <link linkend="dbglvl">Reporting Bugs</link>.