source: branches/samba-3.5.x/docs/htmldocs/Samba3-HOWTO/rights.html

Last change on this file was 739, checked in by Silvan Scherrer, 13 years ago

Samba Server 3.5: update branche to 3.5.19
File size: 30.2 KB
Line 
1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 15. User Rights and Privileges</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="idmapper.html" title="Chapter 14. Identity Mapping (IDMAP)"><link rel="next" href="AccessControls.html" title="Chapter 16. File, Directory, and Share Access Controls"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 15. User Rights and Privileges</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="idmapper.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="AccessControls.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 15. User Rights and Privileges"><div class="titlepage"><div><div><h2 class="title"><a name="rights"></a>Chapter 15. User Rights and Privileges</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>&gt;</code></p></div></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="rights.html#id374718">Rights Management Capabilities</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id374982">Using the <span class="quote">&#8220;<span class="quote">net rpc rights</span>&#8221;</span> Utility</a></span></dt><dt><span class="sect2"><a href="rights.html#id375298">Description of Privileges</a></span></dt><dt><span class="sect2"><a href="rights.html#id375589">Privileges Suppored by Windows 2000 Domain Controllers</a></span></dt></dl></dd><dt><span class="sect1"><a href="rights.html#id376032">The Administrator Domain SID</a></span></dt><dt><span class="sect1"><a href="rights.html#id376197">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="rights.html#id376203">What Rights and Privileges Will Permit Windows Client Administration?</a></span></dt></dl></dd></dl></div><p>
2<a class="indexterm" name="id374461"></a>
3<a class="indexterm" name="id374468"></a>
4<a class="indexterm" name="id374474"></a>
5<a class="indexterm" name="id374481"></a>
6The administration of Windows user, group, and machine accounts in the Samba
7domain-controlled network necessitates interfacing between the MS Windows
8networking environment and the UNIX operating system environment. The right
9(permission) to add machines to the Windows security domain can be assigned
10(set) to non-administrative users both in Windows NT4 domains and
11Active Directory domains.
12</p><p>
13<a class="indexterm" name="id374494"></a>
14<a class="indexterm" name="id374501"></a>
15<a class="indexterm" name="id374508"></a>
16<a class="indexterm" name="id374515"></a>
17The addition of Windows NT4/2kX/XPPro machines to the domain necessitates the
18creation of a machine account for each machine added. The machine account is
19a necessity that is used to validate that the machine can be trusted to permit
20user logons.
21</p><p>
22<a class="indexterm" name="id374527"></a>
23<a class="indexterm" name="id374534"></a>
24<a class="indexterm" name="id374541"></a>
25<a class="indexterm" name="id374548"></a>
26<a class="indexterm" name="id374554"></a>
27<a class="indexterm" name="id374561"></a>
28Machine accounts are analogous to user accounts, and thus in implementing them on a UNIX machine that is
29hosting Samba (i.e., on which Samba is running), it is necessary to create a special type of user account.
30Machine accounts differ from normal user accounts in that the account name (login ID) is terminated with a
31<code class="literal">$</code> sign. An additional difference is that this type of account should not ever be able to
32log into the UNIX environment as a system user and therefore is set to have a shell of
33<code class="literal">/bin/false</code> and a home directory of <code class="literal">/dev/null.</code> The machine
34account is used only to authenticate domain member machines during start-up. This security measure
35is designed to block man-in-the-middle attempts to violate network integrity.
36</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
37<a class="indexterm" name="id374596"></a>
38<a class="indexterm" name="id374602"></a>
39<a class="indexterm" name="id374609"></a>
40<a class="indexterm" name="id374616"></a>
41<a class="indexterm" name="id374623"></a>
42Machine (computer) accounts are used in the Windows NT OS family to store security
43credentials for domain member servers and workstations. When the domain member
44starts up, it goes through a validation process that includes an exchange of
45credentials with a domain controller. If the domain member fails to authenticate
46using the credentials known for it by domain controllers, the machine will be refused
47all access by domain users. The computer account is essential to the way that MS
48Windows secures authentication.
49</p></div><p>
50<a class="indexterm" name="id374637"></a>
51<a class="indexterm" name="id374644"></a>
52<a class="indexterm" name="id374651"></a>
53<a class="indexterm" name="id374658"></a>
54The creation of UNIX system accounts has traditionally been the sole right of
55the system administrator, better known as the <code class="constant">root</code> account.
56It is possible in the UNIX environment to create multiple users who have the
57same UID. Any UNIX user who has a UID=0 is inherently the same as the
58<code class="constant">root</code> account user.
59</p><p>
60<a class="indexterm" name="id374677"></a>
61<a class="indexterm" name="id374684"></a>
62<a class="indexterm" name="id374691"></a>
63<a class="indexterm" name="id374698"></a>
64All versions of Samba call system interface scripts that permit CIFS function
65calls that are used to manage users, groups, and machine accounts
66in the UNIX environment. All versions of Samba up to and including version 3.0.10
67required the use of a Windows administrator account that unambiguously maps to
68the UNIX <code class="constant">root</code> account to permit the execution of these
69interface scripts. The requirement to do this has understandably met with some
70disdain and consternation among Samba administrators, particularly where it became
71necessary to permit people who should not possess <code class="constant">root</code>-level
72access to the UNIX host system.
73</p><div class="sect1" title="Rights Management Capabilities"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id374718"></a>Rights Management Capabilities</h2></div></div></div><p>
74<a class="indexterm" name="id374726"></a>
75<a class="indexterm" name="id374733"></a>
76<a class="indexterm" name="id374740"></a>
77<a class="indexterm" name="id374746"></a>
78Samba 3.0.11 introduced support for the Windows privilege model. This model
79allows certain rights to be assigned to a user or group SID. In order to enable
80this feature, <a class="link" href="smb.conf.5.html#ENABLEPRIVILEGES" target="_top">enable privileges = yes</a>
81must be defined in the <em class="parameter"><code>global</code></em> section of the <code class="filename">smb.conf</code> file.
82</p><p>
83<a class="indexterm" name="id374783"></a>
84<a class="indexterm" name="id374790"></a>
85<a class="indexterm" name="id374796"></a>
86Currently, the rights supported in Samba-3 are listed in <a class="link" href="rights.html#rp-privs" title="Table 15.1. Current Privilege Capabilities">&#8220;Current Privilege Capabilities&#8221;</a>.
87The remainder of this chapter explains how to manage and use these privileges on Samba servers.
88</p><a class="indexterm" name="id374812"></a><a class="indexterm" name="id374819"></a><a class="indexterm" name="id374826"></a><a class="indexterm" name="id374833"></a><a class="indexterm" name="id374840"></a><a class="indexterm" name="id374846"></a><div class="table"><a name="rp-privs"></a><p class="title"><b>Table 15.1. Current Privilege Capabilities</b></p><div class="table-contents"><table summary="Current Privilege Capabilities" border="1"><colgroup><col align="right"><col align="left"></colgroup><thead><tr><th align="left">Privilege</th><th align="left">Description</th></tr></thead><tbody><tr><td align="right"><p>SeMachineAccountPrivilege</p></td><td align="left"><p>Add machines to domain</p></td></tr><tr><td align="right"><p>SePrintOperatorPrivilege</p></td><td align="left"><p>Manage printers</p></td></tr><tr><td align="right"><p>SeAddUsersPrivilege</p></td><td align="left"><p>Add users and groups to the domain</p></td></tr><tr><td align="right"><p>SeRemoteShutdownPrivilege</p></td><td align="left"><p>Force shutdown from a remote system</p></td></tr><tr><td align="right"><p>SeDiskOperatorPrivilege</p></td><td align="left"><p>Manage disk share</p></td></tr><tr><td align="right"><p>SeTakeOwnershipPrivilege</p></td><td align="left"><p>Take ownership of files or other objects</p></td></tr></tbody></table></div></div><br class="table-break"><div class="sect2" title="Using the &#8220;net rpc rights&#8221; Utility"><div class="titlepage"><div><div><h3 class="title"><a name="id374982"></a>Using the <span class="quote">&#8220;<span class="quote">net rpc rights</span>&#8221;</span> Utility</h3></div></div></div><p>
89<a class="indexterm" name="id374993"></a>
90<a class="indexterm" name="id375000"></a>
91<a class="indexterm" name="id375007"></a>
92<a class="indexterm" name="id375014"></a>
93<a class="indexterm" name="id375020"></a>
94There are two primary means of managing the rights assigned to users and groups
95on a Samba server. The <code class="literal">NT4 User Manager for Domains</code> may be
96used from any Windows NT4, 2000, or XP Professional domain member client to
97connect to a Samba domain controller and view/modify the rights assignments.
98This application, however, appears to have bugs when run on a client running
99Windows 2000 or later; therefore, Samba provides a command-line utility for
100performing the necessary administrative actions.
101</p><p>
102The <code class="literal">net rpc rights</code> utility in Samba 3.0.11 has three new subcommands:
103</p><div class="variablelist"><dl><dt><span class="term">list [name|accounts]</span></dt><dd><p>
104<a class="indexterm" name="id375058"></a>
105<a class="indexterm" name="id375069"></a>
106<a class="indexterm" name="id375076"></a>
107<a class="indexterm" name="id375083"></a>
108 When called with no arguments, <code class="literal">net rpc list</code>
109 simply lists the available rights on the server. When passed
110 a specific user or group name, the tool lists the privileges
111 currently assigned to the specified account. When invoked using
112 the special string <code class="constant">accounts</code>,
113 <code class="literal">net rpc rights list</code> returns a list of all
114 privileged accounts on the server and the assigned rights.
115 </p></dd><dt><span class="term">grant &lt;user&gt; &lt;right [right ...]&gt;</span></dt><dd><p>
116<a class="indexterm" name="id375117"></a>
117<a class="indexterm" name="id375124"></a>
118<a class="indexterm" name="id375131"></a>
119<a class="indexterm" name="id375138"></a>
120 When called with no arguments, this function is used to assign
121 a list of rights to a specified user or group. For example,
122 to grant the members of the Domain Admins group on a Samba domain controller,
123 the capability to add client machines to the domain, one would run:
124</p><pre class="screen">
125<code class="prompt">root# </code> net -S server -U domadmin rpc rights grant \
126 'DOMAIN\Domain Admins' SeMachineAccountPrivilege
127</pre><p>
128 The following syntax has the same result:
129<a class="indexterm" name="id375160"></a>
130</p><pre class="screen">
131<code class="prompt">root# </code> net rpc rights grant 'DOMAIN\Domain Admins' \
132 SeMachineAccountPrivilege -S server -U domadmin
133</pre><p>
134 More than one privilege can be assigned by specifying a
135 list of rights separated by spaces. The parameter 'Domain\Domain Admins'
136 must be quoted with single ticks or using double-quotes to prevent
137 the backslash and the space from being interpreted by the system shell.
138 </p></dd><dt><span class="term">revoke &lt;user&gt; &lt;right [right ...]&gt;</span></dt><dd><p>
139 This command is similar in format to <code class="literal">net rpc rights grant</code>. Its
140 effect is to remove an assigned right (or list of rights) from a user or group.
141 </p></dd></dl></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
142<a class="indexterm" name="id375209"></a>
143<a class="indexterm" name="id375216"></a>
144<a class="indexterm" name="id375223"></a>
145You must be connected as a member of the Domain Admins group to be able to grant or revoke privileges assigned
146to an account. This capability is inherent to the Domain Admins group and is not configurable. There are no
147default rights and privileges, except the ability for a member of the Domain Admins group to assign them.
148This means that all administrative rights and privileges (other than the ability to assign them) must be
149explicitly assigned, even for the Domain Admins group.
150</p></div><p>
151<a class="indexterm" name="id375237"></a>
152<a class="indexterm" name="id375244"></a>
153<a class="indexterm" name="id375250"></a>
154<a class="indexterm" name="id375257"></a>
155By default, no privileges are initially assigned to any account because certain actions will be performed as
156root once smbd determines that a user has the necessary rights. For example, when joining a client to a
157Windows domain, <em class="parameter"><code>add machine script</code></em> must be executed with superuser rights in most
158cases. For this reason, you should be very careful about handing out privileges to accounts.
159</p><p>
160<a class="indexterm" name="id375275"></a>
161<a class="indexterm" name="id375282"></a>
162<a class="indexterm" name="id375289"></a>
163Access as the root user (UID=0) bypasses all privilege checks.
164</p></div><div class="sect2" title="Description of Privileges"><div class="titlepage"><div><div><h3 class="title"><a name="id375298"></a>Description of Privileges</h3></div></div></div><p>
165<a class="indexterm" name="id375306"></a>
166<a class="indexterm" name="id375313"></a>
167<a class="indexterm" name="id375320"></a>
168The privileges that have been implemented in Samba-3.0.11 are shown below. It is possible, and likely, that
169additional privileges may be implemented in later releases of Samba. It is also likely that any privileges
170currently implemented but not used may be removed from future releases as a housekeeping matter, so it is
171important that the successful as well as unsuccessful use of these facilities should be reported on the Samba
172mailing lists.
173</p><div class="variablelist"><dl><dt><span class="term">SeAddUsersPrivilege</span></dt><dd><p>
174<a class="indexterm" name="id375341"></a>
175<a class="indexterm" name="id375348"></a>
176<a class="indexterm" name="id375355"></a>
177 This right determines whether or not smbd will allow the
178 user to create new user or group accounts via such tools
179 as <code class="literal">net rpc user add</code> or
180 <code class="literal">NT4 User Manager for Domains.</code>
181 </p></dd><dt><span class="term">SeDiskOperatorPrivilege</span></dt><dd><p>
182<a class="indexterm" name="id375385"></a>
183<a class="indexterm" name="id375391"></a>
184<a class="indexterm" name="id375398"></a>
185 Accounts that possess this right will be able to execute
186 scripts defined by the <code class="literal">add/delete/change</code>
187 share command in <code class="filename">smb.conf</code> file as root. Such users will
188 also be able to modify the ACL associated with file shares
189 on the Samba server.
190 </p></dd><dt><span class="term">SeMachineAccountPrivilege</span></dt><dd><p>
191<a class="indexterm" name="id375428"></a>
192<a class="indexterm" name="id375435"></a>
193<a class="indexterm" name="id375442"></a>
194 This right controls whether or not the user can join client
195 machines to a Samba-controlled domain.
196 </p></dd><dt><span class="term">SePrintOperatorPrivilege</span></dt><dd><p>
197<a class="indexterm" name="id375460"></a>
198<a class="indexterm" name="id375467"></a>
199<a class="indexterm" name="id375474"></a>
200<a class="indexterm" name="id375480"></a>
201<a class="indexterm" name="id375487"></a>
202 This privilege operates identically to the <a class="link" href="smb.conf.5.html#PRINTERADMIN" target="_top">printer admin</a>
203 option in the <code class="filename">smb.conf</code> file (see section 5 man page for <code class="filename">smb.conf</code>)
204 except that it is a global right (not on a per-printer basis).
205 Eventually the smb.conf option will be deprecated and administrative
206 rights to printers will be controlled exclusively by this right and
207 the security descriptor associated with the printer object in the
208 <code class="filename">ntprinters.tdb</code> file.
209 </p></dd><dt><span class="term">SeRemoteShutdownPrivilege</span></dt><dd><p>
210<a class="indexterm" name="id375537"></a>
211<a class="indexterm" name="id375544"></a>
212<a class="indexterm" name="id375550"></a>
213 Samba provides two hooks for shutting down or rebooting
214 the server and for aborting a previously issued shutdown
215 command. Since this is an operation normally limited by
216 the operating system to the root user, an account must possess this
217 right to be able to execute either of these hooks.
218 </p></dd><dt><span class="term">SeTakeOwnershipPrivilege</span></dt><dd><p>
219<a class="indexterm" name="id375570"></a>
220<a class="indexterm" name="id375577"></a>
221 This right permits users to take ownership of files and directories.
222 </p></dd></dl></div></div><div class="sect2" title="Privileges Suppored by Windows 2000 Domain Controllers"><div class="titlepage"><div><div><h3 class="title"><a name="id375589"></a>Privileges Suppored by Windows 2000 Domain Controllers</h3></div></div></div><p>
223 For reference purposes, a Windows NT4 Primary Domain Controller reports support for the following
224 privileges:
225<a class="indexterm" name="id375598"></a>
226<a class="indexterm" name="id375604"></a>
227<a class="indexterm" name="id375611"></a>
228<a class="indexterm" name="id375618"></a>
229<a class="indexterm" name="id375625"></a>
230<a class="indexterm" name="id375632"></a>
231<a class="indexterm" name="id375639"></a>
232<a class="indexterm" name="id375646"></a>
233<a class="indexterm" name="id375653"></a>
234<a class="indexterm" name="id375659"></a>
235<a class="indexterm" name="id375666"></a>
236<a class="indexterm" name="id375673"></a>
237<a class="indexterm" name="id375680"></a>
238<a class="indexterm" name="id375687"></a>
239<a class="indexterm" name="id375694"></a>
240<a class="indexterm" name="id375701"></a>
241<a class="indexterm" name="id375708"></a>
242<a class="indexterm" name="id375714"></a>
243<a class="indexterm" name="id375721"></a>
244<a class="indexterm" name="id375728"></a>
245<a class="indexterm" name="id375735"></a>
246<a class="indexterm" name="id375742"></a>
247<a class="indexterm" name="id375749"></a>
248</p><pre class="screen">
249 SeCreateTokenPrivilege Create a token object
250 SeAssignPrimaryTokenPrivilege Replace a process level token
251 SeLockMemoryPrivilege Lock pages in memory
252 SeIncreaseQuotaPrivilege Increase quotas
253 SeMachineAccountPrivilege Add workstations to domain
254 SeTcbPrivilege Act as part of the operating system
255 SeSecurityPrivilege Manage auditing and security log
256 SeTakeOwnershipPrivilege Take ownership of files or other objects
257 SeLoadDriverPrivilege Load and unload device drivers
258 SeSystemProfilePrivilege Profile system performance
259 SeSystemtimePrivilege Change the system time
260SeProfileSingleProcessPrivilege Profile single process
261SeIncreaseBasePriorityPrivilege Increase scheduling priority
262 SeCreatePagefilePrivilege Create a pagefile
263 SeCreatePermanentPrivilege Create permanent shared objects
264 SeBackupPrivilege Back up files and directories
265 SeRestorePrivilege Restore files and directories
266 SeShutdownPrivilege Shut down the system
267 SeDebugPrivilege Debug programs
268 SeAuditPrivilege Generate security audits
269 SeSystemEnvironmentPrivilege Modify firmware environment values
270 SeChangeNotifyPrivilege Bypass traverse checking
271 SeRemoteShutdownPrivilege Force shutdown from a remote system
272</pre><p>
273 And Windows 200x/XP Domain Controllers and workstations reports to support the following privileges:
274<a class="indexterm" name="id375785"></a>
275<a class="indexterm" name="id375792"></a>
276<a class="indexterm" name="id375799"></a>
277<a class="indexterm" name="id375806"></a>
278<a class="indexterm" name="id375813"></a>
279<a class="indexterm" name="id375820"></a>
280<a class="indexterm" name="id375826"></a>
281<a class="indexterm" name="id375833"></a>
282<a class="indexterm" name="id375840"></a>
283<a class="indexterm" name="id375847"></a>
284<a class="indexterm" name="id375854"></a>
285<a class="indexterm" name="id375861"></a>
286<a class="indexterm" name="id375868"></a>
287<a class="indexterm" name="id375874"></a>
288<a class="indexterm" name="id375881"></a>
289<a class="indexterm" name="id375888"></a>
290<a class="indexterm" name="id375895"></a>
291<a class="indexterm" name="id375902"></a>
292<a class="indexterm" name="id375909"></a>
293<a class="indexterm" name="id375916"></a>
294<a class="indexterm" name="id375922"></a>
295<a class="indexterm" name="id375929"></a>
296<a class="indexterm" name="id375936"></a>
297<a class="indexterm" name="id375943"></a>
298<a class="indexterm" name="id375950"></a>
299<a class="indexterm" name="id375957"></a>
300<a class="indexterm" name="id375964"></a>
301<a class="indexterm" name="id375970"></a>
302<a class="indexterm" name="id375977"></a>
303</p><pre class="screen">
304 SeCreateTokenPrivilege Create a token object
305 SeAssignPrimaryTokenPrivilege Replace a process level token
306 SeLockMemoryPrivilege Lock pages in memory
307 SeIncreaseQuotaPrivilege Increase quotas
308 SeMachineAccountPrivilege Add workstations to domain
309 SeTcbPrivilege Act as part of the operating system
310 SeSecurityPrivilege Manage auditing and security log
311 SeTakeOwnershipPrivilege Take ownership of files or other objects
312 SeLoadDriverPrivilege Load and unload device drivers
313 SeSystemProfilePrivilege Profile system performance
314 SeSystemtimePrivilege Change the system time
315SeProfileSingleProcessPrivilege Profile single process
316SeIncreaseBasePriorityPrivilege Increase scheduling priority
317 SeCreatePagefilePrivilege Create a pagefile
318 SeCreatePermanentPrivilege Create permanent shared objects
319 SeBackupPrivilege Back up files and directories
320 SeRestorePrivilege Restore files and directories
321 SeShutdownPrivilege Shut down the system
322 SeDebugPrivilege Debug programs
323 SeAuditPrivilege Generate security audits
324 SeSystemEnvironmentPrivilege Modify firmware environment values
325 SeChangeNotifyPrivilege Bypass traverse checking
326 SeRemoteShutdownPrivilege Force shutdown from a remote system
327 SeUndockPrivilege Remove computer from docking station
328 SeSyncAgentPrivilege Synchronize directory service data
329 SeEnableDelegationPrivilege Enable computer and user accounts to
330 be trusted for delegation
331 SeManageVolumePrivilege Perform volume maintenance tasks
332 SeImpersonatePrivilege Impersonate a client after authentication
333 SeCreateGlobalPrivilege Create global objects
334</pre><p>
335<a class="indexterm" name="id376020"></a>
336 The Samba Team is implementing only those privileges that are logical and useful in the UNIX/Linux
337 environment. Many of the Windows 200X/XP privileges have no direct equivalence in UNIX.
338 </p></div></div><div class="sect1" title="The Administrator Domain SID"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id376032"></a>The Administrator Domain SID</h2></div></div></div><p>
339<a class="indexterm" name="id376040"></a>
340<a class="indexterm" name="id376047"></a>
341<a class="indexterm" name="id376054"></a>
342<a class="indexterm" name="id376061"></a>
343<a class="indexterm" name="id376067"></a>
344Please note that every Windows NT4 and later server requires a domain Administrator account. Samba versions
345commencing with 3.0.11 permit Administrative duties to be performed via assigned rights and privileges
346(see <a class="link" href="rights.html" title="Chapter 15. User Rights and Privileges">User Rights and Privileges</a>). An account in the server's passdb backend can
347be set to the well-known RID of the default administrator account. To obtain the domain SID on a Samba domain
348controller, run the following command:
349</p><pre class="screen">
350<code class="prompt">root# </code> net getlocalsid
351SID for domain FOO is: S-1-5-21-4294955119-3368514841-2087710299
352</pre><p>
353<a class="indexterm" name="id376097"></a>
354You may assign the domain administrator RID to an account using the <code class="literal">pdbedit</code>
355command as shown here:
356<a class="indexterm" name="id376110"></a>
357</p><pre class="screen">
358<code class="prompt">root# </code> pdbedit -U S-1-5-21-4294955119-3368514841-2087710299-500 -u root -r
359</pre><p>
360</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
361<a class="indexterm" name="id376133"></a>
362<a class="indexterm" name="id376140"></a>
363<a class="indexterm" name="id376146"></a>
364<a class="indexterm" name="id376153"></a>
365The RID 500 is the well known standard value of the default Administrator account. It is the RID
366that confers the rights and privileges that the Administrator account has on a Windows machine
367or domain. Under UNIX/Linux the equivalent is UID=0 (the root account).
368</p></div><p>
369<a class="indexterm" name="id376166"></a>
370<a class="indexterm" name="id376173"></a>
371<a class="indexterm" name="id376180"></a>
372<a class="indexterm" name="id376186"></a>
373Releases of Samba version 3.0.11 and later make it possible to operate without an Administrator account
374provided equivalent rights and privileges have been established for a Windows user or a Windows
375group account.
376</p></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id376197"></a>Common Errors</h2></div></div></div><div class="sect2" title="What Rights and Privileges Will Permit Windows Client Administration?"><div class="titlepage"><div><div><h3 class="title"><a name="id376203"></a>What Rights and Privileges Will Permit Windows Client Administration?</h3></div></div></div><p>
377<a class="indexterm" name="id376211"></a>
378<a class="indexterm" name="id376218"></a>
379<a class="indexterm" name="id376225"></a>
380<a class="indexterm" name="id376231"></a>
381 When a Windows NT4 (or later) client joins a domain, the domain global <code class="literal">Domain Admins</code> group
382 is added to the membership of the local <code class="literal">Administrators</code> group on the client. Any user who is
383 a member of the domain global <code class="literal">Domain Admins</code> group will have administrative rights on the
384 Windows client.
385 </p><p>
386<a class="indexterm" name="id376261"></a>
387<a class="indexterm" name="id376268"></a>
388<a class="indexterm" name="id376275"></a>
389<a class="indexterm" name="id376282"></a>
390<a class="indexterm" name="id376289"></a>
391 This is often not the most desirable solution because it means that the user will have administrative
392 rights and privileges on domain servers also. The <code class="literal">Power Users</code> group on Windows client
393 workstations permits local administration of the workstation alone. Any domain global user or domain global
394 group can be added to the membership of the local workstation group <code class="literal">Power Users</code>.
395 </p><p>
396<a class="indexterm" name="id376313"></a>
397<a class="indexterm" name="id376320"></a>
398<a class="indexterm" name="id376327"></a>
399<a class="indexterm" name="id376334"></a>
400 See <a class="link" href="NetCommand.html#nestedgrpmgmgt" title="Nested Group Support">Nested Group Support</a> for an example of how to add domain users
401 and groups to a local group that is on a Windows workstation. The use of the <code class="literal">net</code>
402 command permits this to be done from the Samba server.
403 </p><p>
404<a class="indexterm" name="id376359"></a>
405<a class="indexterm" name="id376366"></a>
406<a class="indexterm" name="id376372"></a>
407 Another way this can be done is to log onto the Windows workstation as the user
408 <code class="literal">Administrator</code>, then open a <code class="literal">cmd</code> shell, then execute:
409</p><pre class="screen">
410<code class="prompt">C:\&gt; </code> net localgroup administrators /add <strong class="userinput"><code>domain_name\entity</code></strong>
411</pre><p>
412 where <code class="literal">entity</code> is either a domain user or a domain group account name.
413 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="idmapper.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="AccessControls.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 14. Identity Mapping (IDMAP) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 16. File, Directory, and Share Access Controls</td></tr></table></div></body></html>
Note: See TracBrowser for help on using the repository browser.