File: NT4Migration.html

package info (click to toggle)
samba 2:3.6.6-6+deb7u7
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 160,976 kB
  • sloc: ansic: 1,764,536; xml: 114,867; python: 78,119; perl: 27,633; sh: 13,802; makefile: 4,704; asm: 3,281; cpp: 2,281; yacc: 1,949; exp: 1,784; ada: 1,681; pascal: 1,089; cs: 879; awk: 756; lex: 566; csh: 58; sed: 45; php: 6
file content (279 lines) | stat: -rw-r--r-- 30,104 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</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="migration.html" title="Part�IV.�Migration and Updating"><link rel="prev" href="upgrading-to-3.0.html" title="Chapter�35.�Updating and Upgrading Samba"><link rel="next" href="SWAT.html" title="Chapter�37.�SWAT: The Samba Web Administration Tool"></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�36.�Migration from NT4 PDC to Samba-3 PDC</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrading-to-3.0.html">Prev</a>�</td><th width="60%" align="center">Part�IV.�Migration and Updating</th><td width="20%" align="right">�<a accesskey="n" href="SWAT.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter�36.�Migration from NT4 PDC to Samba-3 PDC"><div class="titlepage"><div><div><h2 class="title"><a name="NT4Migration"></a>Chapter�36.�Migration from NT4 PDC to Samba-3 PDC</h2></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><p class="pubdate">April 3, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NT4Migration.html#id441392">Planning and Getting Started</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id441422">Objectives</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id442286">Steps in Migration Process</a></span></dt></dl></dd><dt><span class="sect1"><a href="NT4Migration.html#id442509">Migration Options</a></span></dt><dd><dl><dt><span class="sect2"><a href="NT4Migration.html#id442592">Planning for Success</a></span></dt><dt><span class="sect2"><a href="NT4Migration.html#id442812">Samba-3 Implementation Choices</a></span></dt></dl></dd></dl></div><p>
<a class="indexterm" name="id441376"></a>
<a class="indexterm" name="id441383"></a>
This is a rough guide to assist those wishing to migrate from NT4 domain control to
Samba-3-based domain control.
</p><div class="sect1" title="Planning and Getting Started"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id441392"></a>Planning and Getting Started</h2></div></div></div><p>
<a class="indexterm" name="id441400"></a>
In the IT world there is often a saying that all problems are encountered because of
poor planning. The corollary to this saying is that not all problems can be anticipated
and planned for. Then again, good planning will anticipate most show-stopper-type situations.
</p><p>
<a class="indexterm" name="id441412"></a>
Those wishing to migrate from MS Windows NT4 domain control to a Samba-3 domain control
environment would do well to develop a detailed migration plan. So here are a few pointers to
help migration get underway.
</p><div class="sect2" title="Objectives"><div class="titlepage"><div><div><h3 class="title"><a name="id441422"></a>Objectives</h3></div></div></div><p>
<a class="indexterm" name="id441430"></a>
The key objective for most organizations is to make the migration from MS Windows NT4 
to Samba-3 domain control as painless as possible. One of the challenges you may experience
in your migration process may well be convincing management that the new environment
should remain in place. Many who have introduced open source technologies have experienced
pressure to return to a Microsoft-based platform solution at the first sign of trouble. 
</p><p>
<a class="indexterm" name="id441444"></a>
Before attempting a migration to a Samba-3-controlled network, make every possible effort to
gain all-round commitment to the change. Know precisely <span class="emphasis"><em>why</em></span> the change
is important for the organization. Possible motivations to make a change include:
</p><a class="indexterm" name="id441457"></a><a class="indexterm" name="id441464"></a><a class="indexterm" name="id441471"></a><a class="indexterm" name="id441478"></a><a class="indexterm" name="id441484"></a><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Improve network manageability.</p></li><li class="listitem"><p>Obtain better user-level functionality.</p></li><li class="listitem"><p>Reduce network operating costs.</p></li><li class="listitem"><p>Reduce exposure caused by Microsoft withdrawal of NT4 support.</p></li><li class="listitem"><p>Avoid MS License 6 implications.</p></li><li class="listitem"><p>Reduce organization's dependency on Microsoft.</p></li></ul></div><p>
<a class="indexterm" name="id441525"></a>
<a class="indexterm" name="id441532"></a>
<a class="indexterm" name="id441539"></a>
<a class="indexterm" name="id441545"></a>
<a class="indexterm" name="id441552"></a>
<a class="indexterm" name="id441559"></a>
Make sure everyone knows that Samba-3 is not MS Windows NT4. Samba-3 offers
an alternative solution that is both different from MS Windows NT4 and offers 
advantages compared with it. Gain recognition that Samba-3 lacks many of the
features that Microsoft has promoted as core values in migration from MS Windows NT4 to 
MS Windows 2000 and beyond (with or without Active Directory services).
</p><p>
What are the features that Samba-3 cannot provide?
</p><a class="indexterm" name="id441574"></a><a class="indexterm" name="id441581"></a><a class="indexterm" name="id441587"></a><a class="indexterm" name="id441594"></a><a class="indexterm" name="id441601"></a><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Active Directory Server.</p></li><li class="listitem"><p>Group Policy Objects (in Active Directory).</p></li><li class="listitem"><p>Machine Policy Objects.</p></li><li class="listitem"><p>Logon Scripts in Active Directory.</p></li><li class="listitem"><p>Software Application and Access Controls in Active Directory.</p></li></ul></div><p>
The features that Samba-3 does provide and that may be of compelling interest to your site
include:
</p><a class="indexterm" name="id441639"></a><a class="indexterm" name="id441646"></a><a class="indexterm" name="id441652"></a><a class="indexterm" name="id441659"></a><a class="indexterm" name="id441666"></a><a class="indexterm" name="id441673"></a><a class="indexterm" name="id441680"></a><a class="indexterm" name="id441686"></a><a class="indexterm" name="id441693"></a><a class="indexterm" name="id441700"></a><a class="indexterm" name="id441707"></a><a class="indexterm" name="id441714"></a><a class="indexterm" name="id441720"></a><a class="indexterm" name="id441727"></a><a class="indexterm" name="id441734"></a><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Lower cost of ownership.</p></li><li class="listitem"><p>Global availability of support with no strings attached.</p></li><li class="listitem"><p>Dynamic SMB servers (can run more than one SMB/CIFS server per UNIX/Linux system).</p></li><li class="listitem"><p>Creation of on-the-fly logon scripts.</p></li><li class="listitem"><p>Creation of on-the-fly policy files.</p></li><li class="listitem"><p>Greater stability, reliability, performance, and availability.</p></li><li class="listitem"><p>Manageability via an SSH connection.</p></li><li class="listitem"><p>Flexible choices of backend authentication technologies (tdbsam, ldapsam).</p></li><li class="listitem"><p>Ability to implement a full single-sign-on architecture.</p></li><li class="listitem"><p>Ability to distribute authentication systems for absolute minimum wide-area network bandwidth demand.</p></li></ul></div><p>
<a class="indexterm" name="id441795"></a>
Before migrating a network from MS Windows NT4 to Samba-3, consider all necessary factors. Users
should be educated about changes they may experience so the change will be a welcome one
and not become an obstacle to the work they need to do. The following sections explain factors that will 
help ensure a successful migration.
</p><div class="sect3" title="Domain Layout"><div class="titlepage"><div><div><h4 class="title"><a name="id441806"></a>Domain Layout</h4></div></div></div><p>
<a class="indexterm" name="id441814"></a>
<a class="indexterm" name="id441820"></a>
<a class="indexterm" name="id441827"></a>
<a class="indexterm" name="id441834"></a>
<a class="indexterm" name="id441841"></a>
<a class="indexterm" name="id441848"></a>
<a class="indexterm" name="id441855"></a>
<a class="indexterm" name="id441861"></a>
<a class="indexterm" name="id441868"></a>
<a class="indexterm" name="id441875"></a>
<a class="indexterm" name="id441882"></a>
<a class="indexterm" name="id441888"></a>
<a class="indexterm" name="id441895"></a>
<a class="indexterm" name="id441902"></a>
<a class="indexterm" name="id441909"></a>
<a class="indexterm" name="id441916"></a>
Samba-3 can be configured as a domain controller, a backup domain controller (probably best called
a secondary controller), a domain member, or a standalone server. The Windows network security
domain context should be sized and scoped before implementation. Particular attention needs to be
paid to the location of the Primary Domain Controller (PDC) as well as backup controllers (BDCs).
One way in which Samba-3 differs from Microsoft technology is that if one chooses to use an LDAP
authentication backend, then the same database can be used by several different domains. In a
complex organization, there can be a single LDAP database, which itself can be distributed (have
a master server and multiple slave servers) that can simultaneously serve multiple domains.
</p><p>
<a class="indexterm" name="id441932"></a>
From a design perspective, the number of users per server as well as the number of servers per
domain should be scaled taking into consideration server capacity and network bandwidth.
</p><p>
<a class="indexterm" name="id441944"></a>
<a class="indexterm" name="id441951"></a>
<a class="indexterm" name="id441958"></a>
<a class="indexterm" name="id441964"></a>
<a class="indexterm" name="id441971"></a>
<a class="indexterm" name="id441978"></a>
A physical network segment may house several domains. Each may span multiple network segments.
Where domains span routed network segments, consider and test the performance implications of
the design and layout of a network. A centrally located domain controller that is designed to
serve multiple routed network segments may result in severe performance problems. Check the
response time (ping timing) between the remote segment and the PDC. If it's long (more than 100 ms),
locate a BDC on the remote segment to serve as the local authentication and access control server.
</p></div><div class="sect3" title="Server Share and Directory Layout"><div class="titlepage"><div><div><h4 class="title"><a name="id441992"></a>Server Share and Directory Layout</h4></div></div></div><p>
<a class="indexterm" name="id441999"></a>
<a class="indexterm" name="id442006"></a>
There are cardinal rules to effective network design that cannot be broken with impunity.
The most important rule: Simplicity is king in every well-controlled network. Every part of
the infrastructure must be managed; the more complex it is, the greater will be the demand
of keeping systems secure and functional.
</p><p>
<a class="indexterm" name="id442019"></a>
<a class="indexterm" name="id442026"></a>
<a class="indexterm" name="id442033"></a>
<a class="indexterm" name="id442039"></a>
<a class="indexterm" name="id442046"></a>
<a class="indexterm" name="id442053"></a>
Keep in mind the nature of how data must be shared. Physical disk space layout should be considered
carefully. Some data must be backed up. The simpler the disk layout, the easier it will be to
keep track of backup needs. Identify what backup media will meet your needs; consider backup to tape,
CD-ROM or DVD-ROM, or other offline storage medium. Plan and implement for minimum
maintenance. Leave nothing to chance in your design; above all, do not leave backups to chance:
backup, test, and validate every backup; create a disaster recovery plan and prove that it works.
</p><p>
<a class="indexterm" name="id442068"></a>
<a class="indexterm" name="id442075"></a>
<a class="indexterm" name="id442082"></a>
Users should be grouped according to data access control needs. File and directory access 
is best controlled via group permissions, and the use of the <span class="quote">&#8220;<span class="quote">sticky bit</span>&#8221;</span> on group-controlled
directories may substantially avoid file access complaints from Samba share users.
</p><p>
<a class="indexterm" name="id442098"></a>
<a class="indexterm" name="id442104"></a>
<a class="indexterm" name="id442111"></a>
<a class="indexterm" name="id442118"></a>
<a class="indexterm" name="id442125"></a>
Inexperienced  network administrators often attempt elaborate techniques to set access
controls on files, directories, shares, as well as in share definitions.
Keep your design and implementation simple and document your design extensively. Have others
audit your documentation. Do not create a complex mess that your successor will not understand.
Remember, job security through complex design and implementation may cause loss of operations
and downtime to users as the new administrator learns to untangle your knots. Keep access
controls simple and effective, and make sure that users will never be interrupted by obtuse
complexity.
</p></div><div class="sect3" title="Logon Scripts"><div class="titlepage"><div><div><h4 class="title"><a name="id442139"></a>Logon Scripts</h4></div></div></div><p>
<a class="indexterm" name="id442147"></a>
Logon scripts can help to ensure that all users gain the share and printer connections they need.
</p><p>
Logon scripts can be created on the fly so all commands executed are specific to the
rights and privileges granted to the user. The preferred controls should be effected through
group membership so group information can be used to create a custom logon script using
the <a class="link" href="smb.conf.5.html#ROOTPREEXEC" target="_top">root preexec</a> parameters to the <em class="parameter"><code>NETLOGON</code></em> share.
</p><p>
<a class="indexterm" name="id442182"></a>
Some sites prefer to use a tool such as <code class="literal">kixstart</code> to establish a controlled
user environment. In any case, you may wish to do a Google search for logon script process controls.
In particular, you may wish to explore the use of the Microsoft Knowledge Base article KB189105 that
deals with how to add printers without user intervention via the logon script process.
</p></div><div class="sect3" title="Profile Migration/Creation"><div class="titlepage"><div><div><h4 class="title"><a name="id442200"></a>Profile Migration/Creation</h4></div></div></div><p>
User and group profiles may be migrated using the tools described in the section titled Desktop Profile
Management.
</p><p>
<a class="indexterm" name="id442212"></a>
<a class="indexterm" name="id442218"></a>
Profiles may also be managed using the Samba-3 tool <code class="literal">profiles</code>. This tool allows the MS
Windows NT-style security identifiers (SIDs) that are stored inside the profile
<code class="filename">NTuser.DAT</code> file to be changed to the SID of the Samba-3 domain.
</p></div><div class="sect3" title="User and Group Accounts"><div class="titlepage"><div><div><h4 class="title"><a name="id442241"></a>User and Group Accounts</h4></div></div></div><p>
<a class="indexterm" name="id442249"></a>
<a class="indexterm" name="id442256"></a>
<a class="indexterm" name="id442262"></a>
<a class="indexterm" name="id442269"></a>
It is possible to migrate all account settings from an MS Windows NT4 domain to Samba-3. Before
attempting to migrate user and group accounts, you are STRONGLY advised to create in Samba-3 the
groups that are present on the MS Windows NT4 domain <span class="emphasis"><em>AND</em></span> to map them to
suitable UNIX/Linux groups. By following this simple advice, all user and group attributes
should migrate painlessly.
</p></div></div><div class="sect2" title="Steps in Migration Process"><div class="titlepage"><div><div><h3 class="title"><a name="id442286"></a>Steps in Migration Process</h3></div></div></div><p>
The approximate migration process is described below.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
	You have an NT4 PDC that has the users, groups, policies, and profiles to be migrated.
	</p></li><li class="listitem"><p>
<a class="indexterm" name="id442306"></a>
<a class="indexterm" name="id442313"></a>
<a class="indexterm" name="id442319"></a>
	Samba-3 is set up as a domain controller with netlogon share, profile share, and so on. Configure the <code class="filename">smb.conf</code> file
	to function as a BDC: <em class="parameter"><code>domain master = No</code></em>.
	</p></li></ul></div><div class="procedure" title="Procedure�36.1.�The Account Migration Process"><a name="id442341"></a><p class="title"><b>Procedure�36.1.�The Account Migration Process</b></p><a class="indexterm" name="id442427"></a><ol class="procedure" type="1"><li class="step" title="Step 1"><p>
	<a class="indexterm" name="id442352"></a>
	Create a BDC account in the old NT4 domain for the Samba server using NT Server Manager.
	<span class="emphasis"><em>Samba must not be running.</em></span>
	</p></li><li class="step" title="Step 2"><p>
	<a class="indexterm" name="id442370"></a>
	<strong class="userinput"><code>net rpc join -S <em class="replaceable"><code>NT4PDC</code></em> -w <em class="replaceable"><code>DOMNAME</code></em> -U
	Administrator%<em class="replaceable"><code>passwd</code></em></code></strong>
	</p></li><li class="step" title="Step 3"><p>
<a class="indexterm" name="id442403"></a>
	<strong class="userinput"><code>net rpc vampire -S <em class="replaceable"><code>NT4PDC</code></em> -U 
	administrator%<em class="replaceable"><code>passwd</code></em></code></strong>
	</p></li><li class="step" title="Step 4"><p><strong class="userinput"><code>pdbedit -L</code></strong></p><p>Note: Did the users migrate?</p></li><li class="step" title="Step 5"><p>
	<a class="indexterm" name="id442454"></a>
	<a class="indexterm" name="id442463"></a>
	Now assign each of the UNIX groups to NT groups:
	(It may be useful to copy this text to a script called <code class="filename">initGroups.sh</code>)
	</p><pre class="programlisting">
#!/bin/bash
#### Keep this as a shell script for future re-use
			
# First assign well known domain global groups
net groupmap add ntgroup="Domain Admins" unixgroup=root rid=512 type=d
net groupmap add ntgroup="Domain Users"  unixgroup=users rid=513 type=d
net groupmap add ntgroup="Domain Guests" unixgroup=nobody rid=514 type=d

# Now for our added domain global groups
net groupmap add ntgroup="Designers" unixgroup=designers type=d
net groupmap add ntgroup="Engineers" unixgroup=engineers type=d
net groupmap add ntgroup="QA Team"   unixgroup=qateam    type=d
</pre><p>
	</p></li><li class="step" title="Step 6"><p><strong class="userinput"><code>net groupmap list</code></strong></p><p>Check that all groups are recognized.
	</p></li></ol></div><p>
Migrate all the profiles, then migrate all policy files.
</p></div></div><div class="sect1" title="Migration Options"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id442509"></a>Migration Options</h2></div></div></div><p>
Sites that wish to migrate from MS Windows NT4 domain control to a Samba-based solution
generally fit into three basic categories. <a class="link" href="NT4Migration.html#majtypes" title="Table�36.1.�The Three Major Site Types">Following table</a> shows the possibilities.
</p><div class="table"><a name="majtypes"></a><p class="title"><b>Table�36.1.�The Three Major Site Types</b></p><div class="table-contents"><table summary="The Three Major Site Types" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Number of Users</th><th align="justify">Description</th></tr></thead><tbody><tr><td align="left">&lt; 50</td><td align="justify"><p>Want simple conversion with no pain.</p></td></tr><tr><td align="left">50 - 250</td><td align="justify"><p>Want new features; can manage some inhouse complexity.</p></td></tr><tr><td align="left">&gt; 250</td><td align="justify"><p>Solution/implementation must scale well; complex needs.
		Cross-departmental decision process. Local expertise in most areas.</p></td></tr></tbody></table></div></div><br class="table-break"><div class="sect2" title="Planning for Success"><div class="titlepage"><div><div><h3 class="title"><a name="id442592"></a>Planning for Success</h3></div></div></div><p>
There are three basic choices for sites that intend to migrate from MS Windows NT4
to Samba-3:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
	Simple conversion (total replacement).
	</p></li><li class="listitem"><p>
	Upgraded conversion (could be one of integration).
	</p></li><li class="listitem"><p>
	Complete redesign (completely new solution).
	</p></li></ul></div><p>
Minimize downstream problems by:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
	Taking sufficient time.
	</p></li><li class="listitem"><p>
	Avoiding panic.
	</p></li><li class="listitem"><p>
	Testing all assumptions.
	</p></li><li class="listitem"><p>
	Testing the full roll-out program, including workstation deployment.
	</p></li></ul></div><p><a class="link" href="NT4Migration.html#natconchoices" title="Table�36.2.�Nature of the Conversion Choices">Following table</a> lists the conversion choices given the type of migration
being contemplated.
</p><div class="table"><a name="natconchoices"></a><p class="title"><b>Table�36.2.�Nature of the Conversion Choices</b></p><div class="table-contents"><table summary="Nature of the Conversion Choices" border="1"><colgroup><col align="justify"><col align="justify"><col align="justify"></colgroup><thead><tr><th align="justify">Simple Install</th><th align="justify">Upgrade Decisions</th><th align="justify">Redesign Decisions</th></tr></thead><tbody><tr><td align="justify"><p>Make use of minimal OS-specific features</p></td><td align="justify"><p>Translate NT4 features to new host OS features</p></td><td align="justify"><p>Improve on NT4 functionality, enhance management capabilities</p></td></tr><tr><td align="justify"><p>Move all accounts from NT4 into Samba-3</p></td><td align="justify"><p>Copy and improve</p></td><td align="justify"><p>Authentication regime (database location and access)</p></td></tr><tr><td align="justify"><p>Make least number of operational changes</p></td><td align="justify"><p>Make progressive improvements</p></td><td align="justify"><p>Desktop management methods</p></td></tr><tr><td align="justify"><p>Take least amount of time to migrate</p></td><td align="justify"><p>Minimize user impact</p></td><td align="justify"><p>Better control of Desktops/Users</p></td></tr><tr><td align="justify"><p>Live versus isolated conversion</p></td><td align="justify"><p>Maximize functionality</p></td><td align="justify"><p>Identify Needs for: <span class="emphasis"><em>Manageability, Scalability, Security, Availability</em></span></p></td></tr><tr><td align="justify"><p>Integrate Samba-3, then migrate while users are active, then change of control (swap out)</p></td><td align="justify"><p>Take advantage of lower maintenance opportunity</p></td><td align="justify"><p></p></td></tr></tbody></table></div></div><br class="table-break"></div><div class="sect2" title="Samba-3 Implementation Choices"><div class="titlepage"><div><div><h3 class="title"><a name="id442812"></a>Samba-3 Implementation Choices</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Authentication Database/Backend</span></dt><dd><p>
		Samba-3 can use an external authentication backend:
		</p><p>
		</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Winbind (external Samba or NT4/200x server).</p></li><li class="listitem"><p>External server could use Active Directory or NT4 domain.</p></li><li class="listitem"><p>Can use pam_mkhomedir.so to autocreate home directories.</p></li><li class="listitem"><p> Samba-3 can use a local authentication backend: <em class="parameter"><code>smbpasswd</code></em>,
				<em class="parameter"><code>tdbsam</code></em>, <em class="parameter"><code>ldapsam</code></em>
			</p></li></ul></div></dd><dt><span class="term">Access Control Points</span></dt><dd><p>
		Samba permits Access Control points to be set:
		</p><a class="indexterm" name="id442882"></a><a class="indexterm" name="id442889"></a><a class="indexterm" name="id442896"></a><a class="indexterm" name="id442903"></a><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>On the share itself  using share ACLs.</p></li><li class="listitem"><p>On the file system  using UNIX permissions on files and directories.</p><p>Note: Can enable Posix ACLs in file system also.</p></li><li class="listitem"><p>Through Samba share parameters  not recommended except as last resort.</p></li></ul></div></dd><dt><span class="term">Policies (migrate or create new ones)</span></dt><dd><p>
<a class="indexterm" name="id442948"></a>
<a class="indexterm" name="id442954"></a>
		Exercise great caution when making registry changes; use the right tool and be aware
		that changes made through NT4-style <code class="filename">NTConfig.POL</code> files can leave
		permanent changes.
<a class="indexterm" name="id442968"></a>
<a class="indexterm" name="id442975"></a>
<a class="indexterm" name="id442982"></a>
		</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Using Group Policy Editor (NT4).</p></li><li class="listitem"><p>Watch out for tattoo effect.</p></li></ul></div></dd><dt><span class="term">User and Group Profiles</span></dt><dd><p>
<a class="indexterm" name="id443012"></a>
<a class="indexterm" name="id443019"></a>
		Platform-specific, so use platform tool to change from a local to a roaming profile.
		Can use new profiles tool to change SIDs (<code class="filename">NTUser.DAT</code>).
		</p></dd><dt><span class="term">Logon Scripts</span></dt><dd><p>
		Know how they work.
		</p></dd><dt><span class="term">User and Group Mapping to UNIX/Linux</span></dt><dd><p>
		<a class="indexterm" name="id443055"></a>
		User and group mapping code is new. Many problems have been experienced as network administrators
		who are familiar with Samba-2.2.x migrate to Samba-3. Carefully study the chapters that document
		the new password backend behavior and the new group mapping functionality.
		</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The <em class="parameter"><code>username map</code></em> facility may be needed.</p></li><li class="listitem"><p>Use <code class="literal">net groupmap</code> to connect NT4 groups to UNIX groups.</p></li><li class="listitem"><p>
					Use <code class="literal">pdbedit</code> to set/change user configuration.
					</p><p>
					When migrating to LDAP backend, it may be easier to dump the initial
					LDAP database to LDIF, edit, then reload into LDAP.
					</p></li></ul></div></dd><dt><span class="term">OS-Specific Scripts/Programs May be Needed</span></dt><dd><p>
		Every operating system has its peculiarities. These are the result of engineering decisions
		that were based on the experience of the designer and may have side effects that were not
		anticipated. Limitations that may bite the Windows network administrator include:
		</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Add/Delete Users: Note OS limits on size of name
				(Linux 8 chars, NT4 up to 254 chars).</p></li><li class="listitem"><p>Add/Delete Machines: Applied only to domain members
				(Note: machine names may be limited to 16 characters).</p></li><li class="listitem"><p>Use <code class="literal">net groupmap</code> to connect NT4 groups to UNIX groups.</p></li><li class="listitem"><p>Add/Delete Groups: Note OS limits on size and nature.
				Linux limit is 16 char, no spaces, and no uppercase chars (<code class="literal">groupadd</code>).</p></li></ul></div></dd><dt><span class="term">Migration Tools</span></dt><dd><p>
				<a class="indexterm" name="id443163"></a>
				Domain Control (NT4-Style) Profiles, Policies, Access Controls, Security
				</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Samba: <code class="literal">net, rpcclient, smbpasswd, pdbedit, profiles</code></p></li><li class="listitem"><p>Windows: <code class="literal">NT4 Domain User Manager, Server Manager (NEXUS)</code></p></li></ul></div></dd></dl></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrading-to-3.0.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="migration.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="SWAT.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter�35.�Updating and Upgrading Samba�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�Chapter�37.�SWAT: The Samba Web Administration Tool</td></tr></table></div></body></html>