summaryrefslogtreecommitdiff
path: root/docs/htmldocs/nt4migration.html
blob: 6278a643714575f3877c5514778911c7b6fa20e3 (plain)
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
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Migration from NT4 PDC to Samba-3 PDC</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="PREVIOUS"
TITLE="How to compile SAMBA"
HREF="compiling.html"><LINK
REL="NEXT"
TITLE="Portability"
HREF="portability.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>SAMBA Project Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="compiling.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="portability.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="NT4MIGRATION"
></A
>Chapter 28. Migration from NT4 PDC to Samba-3 PDC</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>28.1. <A
HREF="nt4migration.html#AEN4375"
>Planning and Getting Started</A
></DT
><DD
><DL
><DT
>28.1.1. <A
HREF="nt4migration.html#AEN4379"
>Objectives</A
></DT
><DT
>28.1.2. <A
HREF="nt4migration.html#AEN4405"
>Steps In Migration Process</A
></DT
></DL
></DD
><DT
>28.2. <A
HREF="nt4migration.html#AEN4408"
>Managing Samba-3 Domain Control</A
></DT
></DL
></DIV
><P
>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"
><H1
CLASS="SECT1"
><A
NAME="AEN4375"
>28.1. Planning and Getting Started</A
></H1
><P
>In the IT world there is often a saying that all problems are encountered because of
poor planning. The corrollary to this saying is that not all problems can be anticpated
and planned for. Then again, good planning will anticpate most show stopper type situations.</P
><P
>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 under way.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN4379"
>28.1.1. Objectives</A
></H2
><P
>The key objective for most organisations will be 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 one of 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
>It is strongly advised that before attempting a migration to a Samba-3 controlled network
that every possible effort be made to gain all-round commitment to the change. Firstly, you
should know precisely <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>why</I
></SPAN
> the change is important for the organisation.
Possible motivations to make a change include:</P
><P
></P
><UL
><LI
><P
>Improve network manageability</P
></LI
><LI
><P
>Obtain better user level functionality</P
></LI
><LI
><P
>Reduce network operating costs</P
></LI
><LI
><P
>Reduce exposure caused by Microsoft withdrawal of NT4 support</P
></LI
><LI
><P
>Avoid MS License 6 implications</P
></LI
><LI
><P
>Reduce organisation's dependency on Microsoft</P
></LI
></UL
><P
>It is vital that oit be well recognised that Samba-3 is NOT MS Windows NT4. Samba-3 offers
an alternative solution that is both different from MS Windows NT4 and that offers some
advantages compared with it. It should also be recognised 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 the Samba-3 can NOT provide?</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>Active Directory Server</TD
></TR
><TR
><TD
>Group Policy Objects (in Active Direcrtory)</TD
></TR
><TR
><TD
>Machine Policy objects</TD
></TR
><TR
><TD
>Logon Scripts in Active Directorty</TD
></TR
><TR
><TD
>Software Application and Access Controls in Active Directory</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN4405"
>28.1.2. Steps In Migration Process</A
></H2
><P
>This is not a definitive ste-by-step process yet - just a place holder so the info 
is not lost.

1. You will have an NT4 PDC that has the users, groups, policies and profiles to be migrated

2. Samba-3 set up as a DC with netlogon share, profile share, etc.

3. Process:
	a. Create a BDC account for the samba server using NT Server Manager
		- Samba must NOT be running

	b. rpcclient NT4PDC -U Administrator%passwd
		lsaquery

		Note the SID returned by step b.

	c. net getsid -S NT4PDC -w DOMNAME -U Administrator%passwd

		Note the SID in step c.

	d. net getlocalsid

		Note the SID, now check that all three SIDS reported are the same!

	e. net rpc join -S NT4PDC -w DOMNAME -U Administrator%passwd

	f. net rpc vampire -S NT4PDC -U administrator%passwd

	g. pdbedit -l

		Note - did the users migrate?

	h. initGrps.sh DOMNAME

	i. smbgroupedit -v

		Now check that all groups are recognised

	j. net rpc campire -S NT4PDC -U administrator%passwd

	k. pdbedit -lv

		Note - check that all group membership has been migrated.


Now it is time to migrate all the profiles, then migrate all policy files.

Moe later.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN4408"
>28.2. Managing Samba-3 Domain Control</A
></H1
><P
>Lots of blah blah here.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="compiling.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="samba-howto-collection.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="portability.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to compile SAMBA</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="appendixes.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Portability</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>