docs/howto/Group-Mapping.xml

   1 <?xml version="1.0" encoding="iso8859-1"?>
   2 <chapter id="groupmapping">
   3 <chapterinfo>
   4         &author.jht;
   5         <author>
   6                 <firstname>Jean François</firstname><surname>Micouleau</surname>
   7         </author>
   8         &author.jerry;
   9 </chapterinfo>
  10 <title>Group Mapping &smbmdash; MS Windows and UNIX</title>
  11
  12
  13         <para>
  14 <indexterm significance="preferred"><primary>groups</primary><secondary>mapping</secondary></indexterm>
  15         Starting with Samba-3, new group mapping functionality is available to create associations
  16         between Windows group SIDs and UNIX groups. The <command>groupmap</command> subcommand
  17         included with the &net; tool can be used to manage these associations.
  18         </para>
  19
  20         <para>
  21         The new facility for mapping NT Groups to UNIX system groups allows the administrator to decide
  22         which NT Domain Groups are to be exposed to MS Windows clients. Only those NT Groups that map
  23         to a UNIX group that has a value other than the default (<constant>-1</constant>) will be exposed
  24         in group selection lists in tools that access domain users and groups.
  25         </para>
  26
  27         <warning>
  28         <para>
  29         <indexterm><primary>domain admin group</primary></indexterm>
  30         The <parameter>domain admin group</parameter> parameter has been removed in Samba-3 and should no longer
  31         be specified in &smb.conf;. In Samba-2.2.x, this parameter was used to give the listed users membership in the
  32         <constant>Domain Admins</constant> Windows group which gave local admin rights on their workstations
  33         (in default configurations).
  34         </para>
  35         </warning>
  36
  37 <sect1>
  38 <title>Features and Benefits</title>
  39
  40         <para>
  41         Samba allows the administrator to create MS Windows NT4/200x group accounts and to
  42         arbitrarily associate them with UNIX/Linux group accounts.
  43         </para>
  44
  45         <para>
  46 <indexterm><primary>UID</primary></indexterm>
  47 <indexterm><primary>GID</primary></indexterm>
  48         Group accounts can be managed using the MS Windows NT4 or MS Windows 200x/XP Professional MMC tools.
  49         Appropriate interface scripts should be provided in &smb.conf; if it is desired that UNIX/Linux system
  50         accounts should be automatically created when these tools are used. In the absence of these scripts, and
  51         so long as <command>winbindd</command> is running, Samba group accounts that are created using these
  52         tools will be allocated UNIX UIDs/GIDs from the ID range specified by the
  53         <smbconfoption><name>idmap uid</name></smbconfoption>/<smbconfoption><name>idmap gid</name></smbconfoption>
  54         parameters in the &smb.conf; file.
  55         </para>
  56
  57         <figure id="idmap-sid2gid"><title>IDMAP: group SID to GID resolution.</title>
  58         <mediaobject>
  59         <imageobject role="latex"><imagedata fileref="howto/imagefiles/idmap-sid2gid" scale="50" scalefit="1"/></imageobject>
  60         <imageobject><imagedata fileref="howto/imagefiles/idmap-sid2gid.png" scale="50" scalefit="1"/></imageobject>
  61         </mediaobject>
  62         </figure>
  63
  64         <figure id="idmap-gid2sid"><title>IDMAP: GID resolution to matching SID.</title>
  65         <mediaobject>
  66         <imageobject role="latex"><imagedata fileref="howto/imagefiles/idmap-gid2sid" scale="50" scalefit="1"/></imageobject>
  67         <imageobject><imagedata fileref="howto/imagefiles/idmap-gid2sid.png" scale="50" scalefit="1"/></imageobject>
  68         </mediaobject>
  69         </figure>
  70
  71         <para>
  72         In both cases, when winbindd is not running, only locally resolvable groups can be recognized. Please refer to
  73         <link linkend="idmap-sid2gid">IDMAP: group SID to GID resolution</link> and <link linkend="idmap-gid2sid">IDMAP: GID resolution to matching SID</link>.
  74         The <command>net groupmap</command> is
  75         used to establish UNIX group to NT SID mappings as shown in <link linkend="idmap-store-gid2sid">IDMAP: storing group mappings</link>.
  76         </para>
  77
  78         <figure id="idmap-store-gid2sid"><title>IDMAP storing group mappings.</title>
  79         <mediaobject>
  80         <imageobject role="latex"><imagedata fileref="howto/imagefiles/idmap-store-gid2sid" scale="50" scalefit="1"/></imageobject>
  81         <imageobject><imagedata fileref="howto/imagefiles/idmap-store-gid2sid.png" scale="50" scalefit="1"/></imageobject>
  82         </mediaobject>
  83         </figure>
  84
  85
  86         <para>
  87         <indexterm><primary>groupadd</primary></indexterm>
  88         <indexterm><primary>groupdel</primary></indexterm>
  89         Administrators should be aware that where &smb.conf; group interface scripts make
  90         direct calls to the UNIX/Linux system tools (the shadow utilities, <command>groupadd</command>,
  91         <command>groupdel</command>, and <command>groupmod</command>), the resulting UNIX/Linux group names will be subject
  92         to any limits imposed by these tools. If the tool does not allow upper case characters
  93         or space characters, then the creation of an MS Windows NT4/200x style group of
  94         <ntgroup>Engineering Managers</ntgroup> will attempt to create an identically named
  95         UNIX/Linux group, an attempt that will of course fail.
  96         </para>
  97
  98
  99
 100         <para>
 101         <indexterm><primary>GID</primary></indexterm>
 102         <indexterm><primary>SID</primary></indexterm>
 103         There are several possible work-arounds for the operating system tools limitation. One
 104         method is to use a script that generates a name for the UNIX/Linux system group that
 105         fits the operating system limits, and that then just passes the UNIX/Linux group ID (GID)
 106         back to the calling Samba interface. This will provide a dynamic work-around solution.
 107         </para>
 108
 109         <para>
 110         Another work-around is to manually create a UNIX/Linux group, then manually create the
 111         MS Windows NT4/200x group on the Samba server and then use the <command>net groupmap</command>
 112         tool to connect the two to each other.
 113         </para>
 114
 115 </sect1>
 116
 117 <sect1>
 118 <title>Discussion</title>
 119
 120         <para>
 121         When installing <application>MS Windows NT4/200x</application> on a computer, the installation
 122         program creates default users and groups, notably the <constant>Administrators</constant> group,
 123         and gives that group privileges necessary privileges to perform essential system tasks,
 124         such as the ability to change the date and time or to kill (or close) any process running on the
 125         local machine.
 126         </para>
 127
 128         <para>
 129         <indexterm><primary>Administrator</primary></indexterm>
 130         The <constant>Administrator</constant> user is a member of the <constant>Administrators</constant> group, and thus inherits
 131         <constant>Administrators</constant> group privileges. If a <constant>joe</constant> user is created to be a member of the
 132         <constant>Administrators</constant> group, <constant>joe</constant> has exactly the same rights as the user,
 133         <constant>Administrator</constant>.
 134         </para>
 135
 136         <para>
 137         When an MS Windows NT4/200x/XP machine is made a Domain Member, the <quote>Domain Admins</quote> group of the
 138         PDC is added to the local <constant>Administrators</constant> group of the workstation. Every member of the
 139         <constant>Domain Administrators</constant> group inherits the rights of the local <constant>Administrators</constant> group when
 140         logging on the workstation.
 141         </para>
 142
 143         <para>
 144         The following steps describe how to make Samba PDC users members of the <constant>Domain Admins</constant> group?
 145         </para>
 146
 147         <orderedlist>
 148                 <listitem><para>
 149                 Create a UNIX group (usually in <filename>/etc/group</filename>), let's call it <constant>domadm</constant>.
 150                 </para></listitem>
 151
 152                 <listitem><para>
 153                 Add to this group the users that must be <quote>Administrators</quote>. For example,
 154                 if you want <constant>joe, john</constant> and <constant>mary</constant> to be administrators,
 155                 your entry in <filename>/etc/group</filename> will look like this:
 156                 </para>
 157
 158                 <para><programlisting>
 159                 domadm:x:502:joe,john,mary
 160                 </programlisting>
 161                 </para></listitem>
 162
 163                 <listitem><para>
 164                 Map this domadm group to the <quote>Domain Admins</quote> group by running the command:
 165                 </para>
 166
 167                 <para>
 168         <screen>
 169         &rootprompt;<userinput>net groupmap add ntgroup=<quote>Domain Admins</quote> unixgroup=domadm</userinput>
 170         </screen>
 171         </para>
 172
 173                 <para>
 174                 <indexterm><primary>Domain Admins group</primary></indexterm>
 175                 The quotes around <quote>Domain Admins</quote> are necessary due to the space in the group name.
 176                 Also make sure to leave no white-space surrounding the equal character (=).
 177                 </para></listitem>
 178         </orderedlist>
 179
 180         <para>
 181         Now <constant>joe, john</constant> and <constant>mary</constant> are domain administrators.
 182         </para>
 183
 184         <para>
 185         <indexterm><primary>groups</primary><secondary>domain</secondary></indexterm>
 186         It is possible to map any arbitrary UNIX group to any Windows NT4/200x group as well as
 187         making any UNIX group a Windows domain group. For example, if you wanted to include a
 188         UNIX group (e.g., acct) in an ACL on a local file or printer on a Domain Member machine,
 189         you would flag that group as a domain group by running the following on the Samba PDC:
 190         </para>
 191
 192         <para>
 193 <screen>
 194 &rootprompt;<userinput>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</userinput>
 195 </screen>
 196         </para>
 197
 198         <para>
 199         Be aware that the RID parameter is a unsigned 32-bit integer that should
 200         normally start at 1000. However, this RID must not overlap with any RID assigned
 201         to a user. Verification for this is done differently depending on the passdb backend
 202         you are using. Future versions of the tools may perform the verification automatically,
 203         but for now the burden is on you.
 204         </para>
 205
 206         <sect2>
 207         <title>Important Administrative Information</title>
 208
 209         <para>
 210         Administrative rights are necessary in two specific forms:
 211         </para>
 212
 213         <orderedlist>
 214                 <listitem><para>For Samba-3 Domain Controllers and
 215                                 Domain Member Servers/Clients.</para></listitem>
 216                 <listitem><para>To manage Domain Member Windows workstations.</para></listitem>
 217         </orderedlist>
 218
 219         <para>
 220         Administrative tasks on UNIX/Linux systems, such as adding users or groups, requires <constant>root</constant>
 221         level privilege. The addition of a Windows client to a Samba Domain involves the addition of a user account
 222         for the Windows client.
 223         </para>
 224
 225         <para>
 226         Many UNIX administrators continue to request the Samba Team make it possible to add Windows workstations, or
 227         to ability to add/delete or modify user accounts, without requiring <constant>root</constant> privileges.
 228         Such a request violates every understanding of basic UNIX system security.
 229         </para>
 230
 231         <para>
 232         There is no safe way to provide access on a UNIX/Linux system without providing <constant>root</constant>
 233         level privilege. Provision of <constant>root</constant> privileges can be done wither by logging onto
 234         the Domain as the user <constant>root</constant>, or by permitting particular users to use a UNIX account
 235         that is a member of the UNIX group that has a GID=0 as the primary group in the <filename>/etc/passwd</filename>
 236         database. Users of such accounts can use tools like the NT4 Domain User Manager, and the NT4 Domain Server
 237         Manager to manage user and group accounts as well as Domain Member server and client accounts. This level
 238         of privilege is also needed to manage share level ACLs.
 239         </para>
 240
 241         <para>
 242         Administrative tasks on a Windows Domain Member workstation, can be done by anyone who is a member of the
 243         <constant>Domain Admins</constant> group. This group can be mapped to any convenient UNIX group.
 244         </para>
 245
 246         </sect2>
 247
 248         <sect2>
 249         <title>Default Users, Groups and Relative Identifiers</title>
 250
 251         <para>
 252 <indexterm><primary>Relative Identifier</primary><see>RID</see></indexterm>
 253 <indexterm><primary>RID</primary></indexterm>
 254         When first installed, Microsoft Windows NT4/200x/XP are pre-configured with certain User, Group, and
 255         Alias entities. Each has a well-known Relative Identifier (RID). These must be preserved for continued
 256         integrity of operation. Samba must be provisioned with certain essential Domain Groups that require
 257         the appropriate RID value. When Samba-3 is configured to use <constant>tdbsam</constant> the essential
 258         Domain Groups are automatically created. It is the LDAP administrators' responsibility to create
 259         (provision) the default NT Groups.
 260         </para>
 261
 262         <para>
 263         Each essential Domain Group must be assigned its respective well-known RID. The default Users, Groups,
 264         Aliases, and RIDs are shown in <link linkend="WKURIDS">Well-Known User Default RIDs</link> table.
 265         </para>
 266
 267         <para><note>
 268         When the <parameter>passdb backend</parameter> uses LDAP (<constant>ldapsam</constant>) it is the
 269         administrators' responsibility to create the essential Domain Groups, and to assign each its default RID.
 270         </note></para>
 271
 272         <para>
 273         It is permissible to create any Domain Group that may be necessary, just make certain that the essential
 274         Domain Groups (well known) have been created and assigned its default RID. Other groups you create may
 275         be assigned any arbitrary RID you care to use.
 276         </para>
 277
 278         <para>
 279         Be sure to map each Domain Group to a UNIX system group. That is the only way to ensure that the group
 280         will be available for use as an NT Domain Group.
 281         </para>
 282
 283         <para>
 284         <table frame="all" id="WKURIDS">
 285         <title>Well-Known User Default RIDs</title>
 286                 <tgroup cols="4" align="left">
 287                         <colspec align="left"/>
 288                         <colspec align="left"/>
 289                         <colspec align="left"/>
 290                         <colspec align="center"/>
 291                         <thead>
 292                                 <row>
 293                                         <entry>Well-Known Entity</entry>
 294                                         <entry>RID</entry>
 295                                         <entry>Type</entry>
 296                                         <entry>Essential</entry>
 297                                 </row>
 298                         </thead>
 299                         <tbody>
 300                                 <row>
 301                                         <entry>Domain Administrator</entry>
 302                                         <entry>500</entry>
 303                                         <entry>User</entry>
 304                                         <entry>No</entry>
 305                                 </row>
 306                                 <row>
 307                                         <entry>Domain Guest</entry>
 308                                         <entry>501</entry>
 309                                         <entry>User</entry>
 310                                         <entry>No</entry>
 311                                 </row>
 312                                 <row>
 313                                         <entry>Domain KRBTGT</entry>
 314                                         <entry>502</entry>
 315                                         <entry>User</entry>
 316                                         <entry>No</entry>
 317                                 </row>
 318                                 <row>
 319                                         <entry>Domain Admins</entry>
 320                                         <entry>512</entry>
 321                                         <entry>Group</entry>
 322                                         <entry>Yes</entry>
 323                                 </row>
 324                                 <row>
 325                                         <entry>Domain Users</entry>
 326                                         <entry>513</entry>
 327                                         <entry>Group</entry>
 328                                         <entry>Yes</entry>
 329                                 </row>
 330                                 <row>
 331                                         <entry>Domain Guests</entry>
 332                                         <entry>514</entry>
 333                                         <entry>Group</entry>
 334                                         <entry>Yes</entry>
 335                                 </row>
 336                                 <row>
 337                                         <entry>Domain Computers</entry>
 338                                         <entry>515</entry>
 339                                         <entry>Group</entry>
 340                                         <entry>No</entry>
 341                                 </row>
 342                                 <row>
 343                                         <entry>Domain Controllers</entry>
 344                                         <entry>516</entry>
 345                                         <entry>Group</entry>
 346                                         <entry>No</entry>
 347                                 </row>
 348                                 <row>
 349                                         <entry>Domain Certificate Admins</entry>
 350                                         <entry>517</entry>
 351                                         <entry>Group</entry>
 352                                         <entry>No</entry>
 353                                 </row>
 354                                 <row>
 355                                         <entry>Domain Schema Admins</entry>
 356                                         <entry>518</entry>
 357                                         <entry>Group</entry>
 358                                         <entry>No</entry>
 359                                 </row>
 360                                 <row>
 361                                         <entry>Domain Enterprise Admins</entry>
 362                                         <entry>519</entry>
 363                                         <entry>Group</entry>
 364                                         <entry>No</entry>
 365                                 </row>
 366                                 <row>
 367                                         <entry>Domain Policy Admins</entry>
 368                                         <entry>520</entry>
 369                                         <entry>Group</entry>
 370                                         <entry>No</entry>
 371                                 </row>
 372                                 <row>
 373                                         <entry>Builtin Admins</entry>
 374                                         <entry>544</entry>
 375                                         <entry>Alias</entry>
 376                                         <entry>No</entry>
 377                                 </row>
 378                                 <row>
 379                                         <entry>Builtin users</entry>
 380                                         <entry>545</entry>
 381                                         <entry>Alias</entry>
 382                                         <entry>No</entry>
 383                                 </row>
 384                                 <row>
 385                                         <entry>Builtin Guests</entry>
 386                                         <entry>546</entry>
 387                                         <entry>Alias</entry>
 388                                         <entry>No</entry>
 389                                 </row>
 390                                 <row>
 391                                         <entry>Builtin Power Users</entry>
 392                                         <entry>547</entry>
 393                                         <entry>Alias</entry>
 394                                         <entry>No</entry>
 395                                 </row>
 396                                 <row>
 397                                         <entry>Builtin Account Operators</entry>
 398                                         <entry>548</entry>
 399                                         <entry>Alias</entry>
 400                                         <entry>No</entry>
 401                                 </row>
 402                                 <row>
 403                                         <entry>Builtin System Operators</entry>
 404                                         <entry>549</entry>
 405                                         <entry>Alias</entry>
 406                                         <entry>No</entry>
 407                                 </row>
 408                                 <row>
 409                                         <entry>Builtin Print Operators</entry>
 410                                         <entry>550</entry>
 411                                         <entry>Alias</entry>
 412                                         <entry>No</entry>
 413                                 </row>
 414                                 <row>
 415                                         <entry>Builtin Backup Operators</entry>
 416                                         <entry>551</entry>
 417                                         <entry>Alias</entry>
 418                                         <entry>No</entry>
 419                                 </row>
 420                                 <row>
 421                                         <entry>Builtin Replicator</entry>
 422                                         <entry>552</entry>
 423                                         <entry>Alias</entry>
 424                                         <entry>No</entry>
 425                                 </row>
 426                                 <row>
 427                                         <entry>Builtin RAS Servers</entry>
 428                                         <entry>553</entry>
 429                                         <entry>Alias</entry>
 430                                         <entry>No</entry>
 431                                 </row>
 432                         </tbody>
 433                 </tgroup>
 434         </table>
 435         </para>
 436
 437         </sect2>
 438
 439         <sect2>
 440         <title>Example Configuration</title>
 441
 442                 <para>
 443                 You can list the various groups in the mapping database by executing
 444                 <command>net groupmap list</command>. Here is an example:
 445                 </para>
 446
 447 <indexterm><primary>net</primary><secondary>groupmap</secondary></indexterm>
 448
 449                 <para>
 450 <screen>
 451 &rootprompt; <userinput>net groupmap list</userinput>
 452 Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
 453 Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
 454 Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
 455 </screen>
 456                 </para>
 457
 458                 <para>
 459                 For complete details on <command>net groupmap</command>, refer to the net(8) man page.
 460                 </para>
 461
 462         </sect2>
 463
 464 </sect1>
 465
 466 <sect1>
 467 <title>Configuration Scripts</title>
 468
 469         <para>
 470         Everyone needs tools. Some of us like to create our own, others prefer to use canned tools
 471         (i.e., prepared by someone else for general use).
 472         </para>
 473
 474         <sect2>
 475         <title>Sample &smb.conf; Add Group Script</title>
 476
 477                 <para>
 478                 A script to create complying group names for use by the Samba group interfaces
 479                 is provided in <link linkend="smbgrpadd.sh">smbgrpadd.sh</link>.
 480                 </para>
 481
 482 <indexterm><primary>smbgrpadd.sh</primary></indexterm>
 483                 <para>
 484 <example id="smbgrpadd.sh">
 485         <title>smbgrpadd.sh</title>
 486 <programlisting>
 487
 488 #!/bin/bash
 489
 490 # Add the group using normal system groupadd tool.
 491 groupadd smbtmpgrp00
 492
 493 thegid=`cat /etc/group | grep smbtmpgrp00 | cut -d ":" -f3`
 494
 495 # Now change the name to what we want for the MS Windows networking end
 496 cp /etc/group /etc/group.bak
 497 cat /etc/group.bak | sed "s/smbtmpgrp00/$1/g" > /etc/group
 498
 499 # Now return the GID as would normally happen.
 500 echo $thegid
 501 exit 0
 502 </programlisting>
 503 </example>
 504 </para>
 505
 506                 <para>
 507                 The &smb.conf; entry for the above script would be something like that in <link linkend="smbgrpadd">the following example</link>.
 508 <smbconfexample id="smbgrpadd">
 509 <title>Configuration of &smb.conf; for the add group script.</title>
 510 <smbconfsection>[global]</smbconfsection>
 511 <member>...</member>
 512 <smbconfoption><name>add group script</name><value>/path_to_tool/smbgrpadd.sh &quot;%g&quot;</value></smbconfoption>
 513 <member>...</member>
 514 </smbconfexample>
 515                 </para>
 516
 517         </sect2>
 518
 519         <sect2>
 520         <title>Script to Configure Group Mapping</title>
 521
 522         <para>
 523                 In our example we have created a UNIX/Linux group called <ntgroup>ntadmin</ntgroup>.
 524                 Our script will create the additional groups <ntgroup>Orks</ntgroup>, <ntgroup>Elves</ntgroup>, and <ntgroup>Gnomes</ntgroup>.
 525                 It is a good idea to save this shell script for later re-use just in case you ever need to rebuild your mapping database.
 526                 For the sake of convenience we elect to save this script as a file called <filename>initGroups.sh</filename>.
 527                 This script is given in <link linkend="set-group-map">intGroups.sh</link>.
 528         </para>
 529
 530 <para>
 531 <indexterm><primary>initGroups.sh</primary></indexterm>
 532 <example id="set-group-map">
 533         <title>Script to Set Group Mapping</title>
 534 <programlisting>
 535 #!/bin/bash
 536
 537 net groupmap modify ntgroup="Domain Admins" unixgroup=ntadmin
 538 net groupmap modify ntgroup="Domain Users" unixgroup=users
 539 net groupmap modify ntgroup="Domain Guests" unixgroup=nobody
 540
 541 groupadd Orks
 542 groupadd Elves
 543 groupadd Gnomes
 544
 545 net groupmap add ntgroup="Orks"   unixgroup=Orks   type=d
 546 net groupmap add ntgroup="Elves"  unixgroup=Elves  type=d
 547 net groupmap add ntgroup="Gnomes" unixgroup=Gnomes type=d
 548 </programlisting>
 549 </example>
 550 </para>
 551
 552         <para>
 553         Of course it is expected that the administrator will modify this to suit local needs.
 554         For information regarding the use of the <command>net groupmap</command> tool please
 555         refer to the man page.
 556         </para>
 557
 558         </sect2>
 559
 560 </sect1>
 561
 562 <sect1>
 563 <title>Common Errors</title>
 564
 565 <para>
 566 At this time there are many little surprises for the unwary administrator. In a real sense
 567 it is imperative that every step of automated control scripts must be carefully tested
 568 manually before putting them into active service.
 569 </para>
 570
 571         <sect2>
 572         <title>Adding Groups Fails</title>
 573
 574                 <para>
 575                 This is a common problem when the <command>groupadd</command> is called directly
 576                 by the Samba interface script for the <smbconfoption><name>add group script</name></smbconfoption> in
 577                 the &smb.conf; file.
 578                 </para>
 579
 580                 <para>
 581                 The most common cause of failure is an attempt to add an MS Windows group account
 582                 that has either an upper case character and/or a space character in it.
 583                 </para>
 584
 585                 <para>
 586                 There are three possible work-arounds. First, use only group names that comply
 587                 with the limitations of the UNIX/Linux <command>groupadd</command> system tool.
 588                 Second, it involves the use of the script mentioned earlier in this chapter, and
 589                 third is the option is to manually create a UNIX/Linux group account that can substitute
 590                 for the MS Windows group name, then use the procedure listed above to map that group
 591                 to the MS Windows group.
 592                 </para>
 593
 594         </sect2>
 595
 596         <sect2>
 597         <title>Adding MS Windows Groups to MS Windows Groups Fails</title>
 598
 599         <indexterm><primary>groups</primary><secondary>nested</secondary></indexterm>
 600
 601                 <para>
 602                 Samba-3 does not support nested groups from the MS Windows control environment.
 603                 </para>
 604
 605         </sect2>
 606
 607         <sect2>
 608         <title>Adding <emphasis>Domain Users</emphasis> to the <emphasis>Power Users</emphasis> Group</title>
 609
 610                 <para><quote>
 611                 What must I do to add Domain Users to the Power Users group?
 612                 </quote></para>
 613
 614 <indexterm><primary>Domain Users group</primary></indexterm>
 615
 616                 <para>
 617                 The Power Users group is a group that is local to each Windows 200x/XP Professional workstation.
 618                 You cannot add the Domain Users group to the Power Users group automatically, it must be done on
 619                 each workstation by logging in as the local workstation <emphasis>administrator</emphasis> and
 620                 then using the following procedure:
 621                 </para>
 622
 623                 <procedure>
 624                         <step><para>
 625                         Click <guimenu>Start -> Control Panel -> Users and Passwords</guimenu>.
 626                         </para></step>
 627
 628                         <step><para>
 629                         Click the <guimenuitem>Advanced</guimenuitem> tab.
 630                         </para></step>
 631
 632                         <step><para>
 633                         Click the <guibutton>Advanced</guibutton> button.
 634                         </para></step>
 635
 636                         <step><para>
 637                         Click <constant>Groups</constant>.
 638                         </para></step>
 639
 640                         <step><para>
 641                         Double click <constant>Power Users</constant>. This will launch the panel to add users or groups
 642                         to the local machine <constant>Power Uses</constant> group.
 643                         </para></step>
 644
 645                         <step><para>
 646                         Click the <guibutton>Add</guibutton> button.
 647                         </para></step>
 648
 649                         <step><para>
 650                         Select the domain from which the <constant>Domain Users</constant> group is to be added.
 651                         </para></step>
 652
 653                         <step><para>
 654                         Double click the <constant>Domain Users</constant> group.
 655                         </para></step>
 656
 657                         <step><para>
 658                         Click the <guibutton>Ok</guibutton> button. If a logon box is presented during this process
 659                         please remember to enter the connect as <constant>DOMAIN\UserName</constant>. i.e., For the
 660                         domain <constant>MIDEARTH</constant> and the user <constant>root</constant> enter
 661                         <constant>MIDEARTH\root</constant>.
 662                         </para></step>
 663                 </procedure>
 664         </sect2>
 665
 666 </sect1>
 667
 668 </chapter>