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
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Desktop Profile Management</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="Advanced Configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="System and Account Policies"
HREF="policymgmt.html"><LINK
REL="NEXT"
TITLE="Interdomain Trust Relationships"
HREF="interdomaintrusts.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="policymgmt.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="interdomaintrusts.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="PROFILEMGMT"
></A
>Chapter 18. Desktop Profile Management</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>18.1. <A
HREF="profilemgmt.html#AEN3095"
>Roaming Profiles</A
></DT
><DD
><DL
><DT
>18.1.1. <A
HREF="profilemgmt.html#AEN3102"
>Samba Configuration for Profile Handling</A
></DT
><DD
><DL
><DT
>18.1.1.1. <A
HREF="profilemgmt.html#AEN3105"
>NT4/200x User Profiles</A
></DT
><DT
>18.1.1.2. <A
HREF="profilemgmt.html#AEN3115"
>Windows 9x / Me User Profiles</A
></DT
><DT
>18.1.1.3. <A
HREF="profilemgmt.html#AEN3130"
>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A
></DT
></DL
></DD
><DT
>18.1.2. <A
HREF="profilemgmt.html#AEN3137"
>Windows Client Profile Configuration Information</A
></DT
><DD
><DL
><DT
>18.1.2.1. <A
HREF="profilemgmt.html#AEN3139"
>Windows 9x / Me Profile Setup</A
></DT
><DT
>18.1.2.2. <A
HREF="profilemgmt.html#AEN3175"
>Windows NT4 Workstation</A
></DT
><DT
>18.1.2.3. <A
HREF="profilemgmt.html#AEN3184"
>Windows 2000/XP Professional</A
></DT
></DL
></DD
><DT
>18.1.3. <A
HREF="profilemgmt.html#AEN3257"
>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
></DT
><DT
>18.1.4. <A
HREF="profilemgmt.html#AEN3264"
>Profile Migration from Windows NT4/200x Server to Samba</A
></DT
><DD
><DL
><DT
>18.1.4.1. <A
HREF="profilemgmt.html#AEN3267"
>Windows NT4 Profile Management Tools</A
></DT
><DT
>18.1.4.2. <A
HREF="profilemgmt.html#AEN3290"
>Side bar Notes</A
></DT
><DT
>18.1.4.3. <A
HREF="profilemgmt.html#AEN3294"
>moveuser.exe</A
></DT
><DT
>18.1.4.4. <A
HREF="profilemgmt.html#AEN3297"
>Get SID</A
></DT
></DL
></DD
></DL
></DD
><DT
>18.2. <A
HREF="profilemgmt.html#AEN3302"
>Mandatory profiles</A
></DT
><DT
>18.3. <A
HREF="profilemgmt.html#AEN3309"
>Creating/Managing Group Profiles</A
></DT
><DT
>18.4. <A
HREF="profilemgmt.html#AEN3315"
>Default Profile for Windows Users</A
></DT
><DD
><DL
><DT
>18.4.1. <A
HREF="profilemgmt.html#AEN3318"
>MS Windows 9x/Me</A
></DT
><DT
>18.4.2. <A
HREF="profilemgmt.html#AEN3330"
>MS Windows NT4 Workstation</A
></DT
><DT
>18.4.3. <A
HREF="profilemgmt.html#AEN3384"
>MS Windows 200x/XP</A
></DT
></DL
></DD
></DL
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3095"
>18.1. Roaming Profiles</A
></H1
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Roaming profiles support is different for Win9x / Me and Windows NT4/200x.</P
></TD
></TR
></TABLE
></DIV
><P
>Before discussing how to configure roaming profiles, it is useful to see how
Windows 9x / Me and Windows NT4/200x clients implement these features.</P
><P
>Windows 9x / Me clients send a NetUserGetInfo request to the server to get the user's
profiles location. However, the response does not have room for a separate
profiles location field, only the user's home share. This means that Win9X/Me
profiles are restricted to being stored in the user's home directory.</P
><P
>Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields,
including a separate field for the location of the user's profiles.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3102"
>18.1.1. Samba Configuration for Profile Handling</A
></H2
><P
>This section documents how to configure Samba for MS Windows client profile support.</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3105"
>18.1.1.1. NT4/200x User Profiles</A
></H3
><P
>To support Windowns NT4/200x clients, in the [global] section of smb.conf set the
following (for example):</P
><P
><PRE
CLASS="PROGRAMLISTING"
> logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</PRE
>
This is typically implemented like:
<PRE
CLASS="PROGRAMLISTING"
> logon path = \\%L\Profiles\%u</PRE
>
where %L translates to the name of the Samba server and %u translates to the user name</P
><P
>The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile.
The \\N%\%U service is created automatically by the [homes] service. If you are using
a samba server for the profiles, you _must_ make the share specified in the logon path
browseable. Please refer to the man page for smb.conf in respect of the different
symantics of %L and %N, as well as %U and %u.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>MS Windows NT/2K clients at times do not disconnect a connection to a server
between logons. It is recommended to NOT use the <B
CLASS="COMMAND"
>homes</B
>
meta-service name as part of the profile share path.</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3115"
>18.1.1.2. Windows 9x / Me User Profiles</A
></H3
><P
>To support Windows 9x / Me clients, you must use the "logon home" parameter. Samba has
now been fixed so that <KBD
CLASS="USERINPUT"
>net use /home</KBD
> now works as well, and it, too, relies
on the <B
CLASS="COMMAND"
>logon home</B
> parameter.</P
><P
>By using the logon home parameter, you are restricted to putting Win9x / Me
profiles in the user's home directory. But wait! There is a trick you
can use. If you set the following in the <B
CLASS="COMMAND"
>[global]</B
> section of your <TT
CLASS="FILENAME"
>smb.conf</TT
> file:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> logon home = \\%L\%U\.profiles</PRE
></P
><P
>then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
of your home directory called <TT
CLASS="FILENAME"
>.profiles</TT
> (thus making them hidden).</P
><P
>Not only that, but <KBD
CLASS="USERINPUT"
>net use/home</KBD
> will also work, because of a feature in
Windows 9x / Me. It removes any directory stuff off the end of the home directory area
and only uses the server and share portion. That is, it looks like you
specified \\%L\%U for <B
CLASS="COMMAND"
>logon home</B
>.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3130"
>18.1.1.3. Mixed Windows 9x / Me and Windows NT4/200x User Profiles</A
></H3
><P
>You can support profiles for both Win9X and WinNT clients by setting both the
<B
CLASS="COMMAND"
>logon home</B
> and <B
CLASS="COMMAND"
>logon path</B
> parameters. For example:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> logon home = \\%L\%u\.profiles
logon path = \\%L\profiles\%u</PRE
></P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3137"
>18.1.2. Windows Client Profile Configuration Information</A
></H2
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3139"
>18.1.2.1. Windows 9x / Me Profile Setup</A
></H3
><P
>When a user first logs in on Windows 9X, the file user.DAT is created,
as are folders "Start Menu", "Desktop", "Programs" and "Nethood".
These directories and their contents will be merged with the local
versions stored in c:\windows\profiles\username on subsequent logins,
taking the most recent from each. You will need to use the [global]
options "preserve case = yes", "short preserve case = yes" and
"case sensitive = no" in order to maintain capital letters in shortcuts
in any of the profile folders.</P
><P
>The user.DAT file contains all the user's preferences. If you wish to
enforce a set of preferences, rename their user.DAT file to user.MAN,
and deny them write access to this file.</P
><P
></P
><OL
TYPE="1"
><LI
><P
> On the Windows 9x / Me machine, go to Control Panel -> Passwords and
select the User Profiles tab. Select the required level of
roaming preferences. Press OK, but do _not_ allow the computer
to reboot.
</P
></LI
><LI
><P
> On the Windows 9x / Me machine, go to Control Panel -> Network ->
Client for Microsoft Networks -> Preferences. Select 'Log on to
NT Domain'. Then, ensure that the Primary Logon is 'Client for
Microsoft Networks'. Press OK, and this time allow the computer
to reboot.
</P
></LI
></OL
><P
>Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
If you have the Primary Logon as 'Client for Novell Networks', then
the profiles and logon script will be downloaded from your Novell
Server. If you have the Primary Logon as 'Windows Logon', then the
profiles will be loaded from the local machine - a bit against the
concept of roaming profiles, it would seem!</P
><P
>You will now find that the Microsoft Networks Login box contains
[user, password, domain] instead of just [user, password]. Type in
the samba server's domain name (or any other domain known to exist,
but bear in mind that the user will be authenticated against this
domain and profiles downloaded from it, if that domain logon server
supports it), user name and user's password.</P
><P
>Once the user has been successfully validated, the Windows 9x / Me machine
will inform you that 'The user has not logged on before' and asks you
if you wish to save the user's preferences? Select 'yes'.</P
><P
>Once the Windows 9x / Me client comes up with the desktop, you should be able
to examine the contents of the directory specified in the "logon path"
on the samba server and verify that the "Desktop", "Start Menu",
"Programs" and "Nethood" folders have been created.</P
><P
>These folders will be cached locally on the client, and updated when
the user logs off (if you haven't made them read-only by then).
You will find that if the user creates further folders or short-cuts,
that the client will merge the profile contents downloaded with the
contents of the profile directory already on the local client, taking
the newest folders and short-cuts from each set.</P
><P
>If you have made the folders / files read-only on the samba server,
then you will get errors from the Windows 9x / Me machine on logon and logout, as
it attempts to merge the local and the remote profile. Basically, if
you have any errors reported by the Windows 9x / Me machine, check the Unix file
permissions and ownership rights on the profile directory contents,
on the samba server.</P
><P
>If you have problems creating user profiles, you can reset the user's
local desktop cache, as shown below. When this user then next logs in,
they will be told that they are logging in "for the first time".</P
><P
></P
><OL
TYPE="1"
><LI
><P
> instead of logging in under the [user, password, domain] dialog,
press escape.
</P
></LI
><LI
><P
> run the regedit.exe program, and look in:
</P
><P
> HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
</P
><P
> you will find an entry, for each user, of ProfilePath. Note the
contents of this key (likely to be c:\windows\profiles\username),
then delete the key ProfilePath for the required user.
[Exit the registry editor].
</P
></LI
><LI
><P
> <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>WARNING</I
></SPAN
> - before deleting the contents of the
directory listed in the ProfilePath (this is likely to be
<TT
CLASS="FILENAME"
>c:\windows\profiles\username)</TT
>, ask them if they
have any important files stored on their desktop or in their start menu.
Delete the contents of the directory ProfilePath (making a backup if any
of the files are needed).
</P
><P
> This will have the effect of removing the local (read-only hidden
system file) user.DAT in their profile directory, as well as the
local "desktop", "nethood", "start menu" and "programs" folders.
</P
></LI
><LI
><P
> search for the user's .PWL password-caching file in the c:\windows
directory, and delete it.
</P
></LI
><LI
><P
> log off the windows 9x / Me client.
</P
></LI
><LI
><P
> check the contents of the profile path (see "logon path" described
above), and delete the user.DAT or user.MAN file for the user,
making a backup if required.
</P
></LI
></OL
><P
>If all else fails, increase samba's debug log levels to between 3 and 10,
and / or run a packet trace program such as ethereal or netmon.exe, and
look for error messages.</P
><P
>If you have access to an Windows NT4/200x server, then first set up roaming profiles
and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine
the example packet traces provided with Windows NT4/200x server, and see what the
differences are with the equivalent samba trace.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3175"
>18.1.2.2. Windows NT4 Workstation</A
></H3
><P
>When a user first logs in to a Windows NT Workstation, the profile
NTuser.DAT is created. The profile location can be now specified
through the "logon path" parameter.</P
><P
>There is a parameter that is now available for use with NT Profiles:
"logon drive". This should be set to <TT
CLASS="FILENAME"
>H:</TT
> or any other drive, and
should be used in conjunction with the new "logon home" parameter.</P
><P
>The entry for the NT4 profile is a _directory_ not a file. The NT
help on profiles mentions that a directory is also created with a .PDS
extension. The user, while logging in, must have write permission to
create the full profile path (and the folder with the .PDS extension
for those situations where it might be created.)</P
><P
>In the profile directory, Windows NT4 creates more folders than Windows 9x / Me.
It creates "Application Data" and others, as well as "Desktop", "Nethood",
"Start Menu" and "Programs". The profile itself is stored in a file
NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
its purpose is currently unknown.</P
><P
>You can use the System Control Panel to copy a local profile onto
a samba server (see NT Help on profiles: it is also capable of firing
up the correct location in the System Control Panel for you). The
NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
turns a profile into a mandatory one.</P
><P
>The case of the profile is significant. The file must be called
NTuser.DAT or, for a mandatory profile, NTuser.MAN.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3184"
>18.1.2.3. Windows 2000/XP Professional</A
></H3
><P
>You must first convert the profile from a local profile to a domain
profile on the MS Windows workstation as follows:</P
><P
></P
><UL
><LI
><P
> Log on as the LOCAL workstation administrator.
</P
></LI
><LI
><P
> Right click on the 'My Computer' Icon, select 'Properties'
</P
></LI
><LI
><P
> Click on the 'User Profiles' tab
</P
></LI
><LI
><P
> Select the profile you wish to convert (click on it once)
</P
></LI
><LI
><P
> Click on the button 'Copy To'
</P
></LI
><LI
><P
> In the "Permitted to use" box, click on the 'Change' button.
</P
></LI
><LI
><P
> Click on the 'Look in" area that lists the machine name, when you click
here it will open up a selection box. Click on the domain to which the
profile must be accessible.
</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>You will need to log on if a logon box opens up. Eg: In the connect
as: MIDEARTH\root, password: mypassword.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
> To make the profile capable of being used by anyone select 'Everyone'
</P
></LI
><LI
><P
> Click OK. The Selection box will close.
</P
></LI
><LI
><P
> Now click on the 'Ok' button to create the profile in the path you
nominated.
</P
></LI
></UL
><P
>Done. You now have a profile that can be editted using the samba-3.0.0
<TT
CLASS="FILENAME"
>profiles</TT
> tool.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Under NT/2K the use of mandotory profiles forces the use of MS Exchange
storage of mail data. That keeps desktop profiles usable.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
></P
><UL
><LI
><P
>This is a security check new to Windows XP (or maybe only
Windows XP service pack 1). It can be disabled via a group policy in
Active Directory. The policy is:</P
><P
>"Computer Configuration\Administrative Templates\System\User
Profiles\Do not check for user ownership of Roaming Profile Folders"</P
><P
>...and it should be set to "Enabled".
Does the new version of samba have an Active Directory analogue? If so,
then you may be able to set the policy through this.</P
><P
>If you cannot set group policies in samba, then you may be able to set
the policy locally on each machine. If you want to try this, then do
the following (N.B. I don't know for sure that this will work in the
same way as a domain group policy):</P
></LI
><LI
><P
>On the XP workstation log in with an Administrator account.</P
></LI
><LI
><P
>Click: "Start", "Run"</P
></LI
><LI
><P
>Type: "mmc"</P
></LI
><LI
><P
>Click: "OK"</P
></LI
><LI
><P
>A Microsoft Management Console should appear.</P
></LI
><LI
><P
>Click: File, "Add/Remove Snap-in...", "Add"</P
></LI
><LI
><P
>Double-Click: "Group Policy"</P
></LI
><LI
><P
>Click: "Finish", "Close"</P
></LI
><LI
><P
>Click: "OK"</P
></LI
><LI
><P
>In the "Console Root" window:</P
></LI
><LI
><P
>Expand: "Local Computer Policy", "Computer Configuration",</P
></LI
><LI
><P
>"Administrative Templates", "System", "User Profiles"</P
></LI
><LI
><P
>Double-Click: "Do not check for user ownership of Roaming Profile</P
></LI
><LI
><P
>Folders"</P
></LI
><LI
><P
>Select: "Enabled"</P
></LI
><LI
><P
>Click: OK"</P
></LI
><LI
><P
>Close the whole console. You do not need to save the settings (this
refers to the console settings rather than the policies you have
changed).</P
></LI
><LI
><P
>Reboot</P
></LI
></UL
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3257"
>18.1.3. Sharing Profiles between W9x/Me and NT4/200x/XP workstations</A
></H2
><P
>Sharing of desktop profiles between Windows versions is NOT recommended.
Desktop profiles are an evolving phenomenon and profiles for later versions
of MS Windows clients add features that may interfere with earlier versions
of MS Windows clients. Probably the more salient reason to NOT mix profiles
is that when logging off an earlier version of MS Windows the older format
of profile contents may overwrite information that belongs to the newer
version resulting in loss of profile information content when that user logs
on again with the newer version of MS Windows.</P
><P
>If you then want to share the same Start Menu / Desktop with W9x/Me, you will
need to specify a common location for the profiles. The smb.conf parameters
that need to be common are <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>logon path</I
></SPAN
> and
<SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>logon home</I
></SPAN
>.</P
><P
>If you have this set up correctly, you will find separate user.DAT and
NTuser.DAT files in the same profile directory.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3264"
>18.1.4. Profile Migration from Windows NT4/200x Server to Samba</A
></H2
><P
>There is nothing to stop you specifying any path that you like for the
location of users' profiles. Therefore, you could specify that the
profile be stored on a samba server, or any other SMB server, as long as
that SMB server supports encrypted passwords.</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3267"
>18.1.4.1. Windows NT4 Profile Management Tools</A
></H3
><P
>Unfortunately, the Resource Kit information is specific to the version of MS Windows
NT4/200x. The correct resource kit is required for each platform.</P
><P
>Here is a quick guide:</P
><P
></P
><UL
><LI
><P
>On your NT4 Domain Controller, right click on 'My Computer', then
select the tab labelled 'User Profiles'.</P
></LI
><LI
><P
>Select a user profile you want to migrate and click on it.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>I am using the term "migrate" lossely. You can copy a profile to
create a group profile. You can give the user 'Everyone' rights to the
profile you copy this to. That is what you need to do, since your samba
domain is not a member of a trust relationship with your NT4 PDC.</P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>Click the 'Copy To' button.</P
></LI
><LI
><P
>In the box labelled 'Copy Profile to' add your new path, eg:
<TT
CLASS="FILENAME"
>c:\temp\foobar</TT
></P
></LI
><LI
><P
>Click on the button labelled 'Change' in the "Permitted to use" box.</P
></LI
><LI
><P
>Click on the group 'Everyone' and then click OK. This closes the
'chose user' box.</P
></LI
><LI
><P
>Now click OK.</P
></LI
></UL
><P
>Follow the above for every profile you need to migrate.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3290"
>18.1.4.2. Side bar Notes</A
></H3
><P
>You should obtain the SID of your NT4 domain. You can use smbpasswd to do
this. Read the man page.</P
><P
>With Samba-3.0.0 alpha code you can import all you NT4 domain accounts
using the net samsync method. This way you can retain your profile
settings as well as all your users.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3294"
>18.1.4.3. moveuser.exe</A
></H3
><P
>The W2K professional resource kit has moveuser.exe. moveuser.exe changes
the security of a profile from one user to another. This allows the account
domain to change, and/or the user name to change.</P
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3297"
>18.1.4.4. Get SID</A
></H3
><P
>You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
Resource Kit.</P
><P
>Windows NT 4.0 stores the local profile information in the registry under
the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</P
><P
>Under the ProfileList key, there will be subkeys named with the SIDs of the
users who have logged on to this computer. (To find the profile information
for the user whose locally cached profile you want to move, find the SID for
the user with the GetSID.exe utility.) Inside of the appropriate user's
subkey, you will see a string value named ProfileImagePath.</P
></DIV
></DIV
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3302"
>18.2. Mandatory profiles</A
></H1
><P
>A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
During the user's session it may be possible to change the desktop environment, but
as the user logs out all changes made will be lost. If it is desired to NOT allow the
user any ability to change the desktop environment then this must be done through
policy settings. See previous chapter.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Under NO circumstances should the profile directory (or it's contents) be made read-only
as this may render the profile un-usable.</P
></TD
></TR
></TABLE
></DIV
><P
>For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles
also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
file in the copied profile and rename it to NTUser.MAN.</P
><P
>For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to
affect a mandatory profile.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3309"
>18.3. Creating/Managing Group Profiles</A
></H1
><P
>Most organisations are arranged into departments. There is a nice benenfit in
this fact since usually most users in a department will require the same desktop
applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
use of Group Profiles. A Group Profile is a profile that is created firstly using
a template (example) user. Then using the profile migration tool (see above) the
profile is assigned access rights for the user group that needs to be given access
to the group profile.</P
><P
>The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
the now modified profile.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> Be careful with group profiles, if the user who is a member of a group also
has a personal profile, then the result will be a fusion (merge) of the two.
</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3315"
>18.4. Default Profile for Windows Users</A
></H1
><P
>MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
a profile does not already exist. Armed with a knowledge of where the default profile
is located on the Windows workstation, and knowing which registry keys affect the path
from which the default profile is created, it is possible to modify the default profile
to one that has been optimised for the site. This has significant administrative
advantages.</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3318"
>18.4.1. MS Windows 9x/Me</A
></H2
><P
>To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
Policy Editor or change the registry directly.</P
><P
>To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then
select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System,
select User Profiles, click on the enable box. Do not forget to save the registry changes.</P
><P
>To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
<TT
CLASS="FILENAME"
>HKEY_LOCAL_MACHINE\Network\Logon</TT
>. Now add a DWORD type key with the name
"User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.</P
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN3324"
>18.4.1.1. How User Profiles Are Handled in Windows 9x / Me?</A
></H3
><P
>When a user logs on to a Windows 9x / Me machine, the local profile path,
<TT
CLASS="FILENAME"
>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</TT
>, is checked
for an existing entry for that user:</P
><P
>If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
version of the user profile. Windows 9x / Me also checks the user's home directory (or other
specified directory if the location has been modified) on the server for the User Profile.
If a profile exists in both locations, the newer of the two is used. If the User Profile exists
on the server, but does not exist on the local machine, the profile on the server is downloaded
and used. If the User Profile only exists on the local machine, that copy is used.</P
><P
>If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
machine is used and is copied to a newly created folder for the logged on user. At log off, any
changes that the user made are written to the user's local profile. If the user has a roaming
profile, the changes are written to the user's profile on the server.</P
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3330"
>18.4.2. MS Windows NT4 Workstation</A
></H2
><P
>On MS Windows NT4 the default user profile is obtained from the location
<TT
CLASS="FILENAME"
>%SystemRoot%\Profiles</TT
> which in a default installation will translate to
<TT
CLASS="FILENAME"
>C:\WinNT\Profiles</TT
>. Under this directory on a clean install there will be
three (3) directories: <TT
CLASS="FILENAME"
>Administrator, All Users, Default User</TT
>.</P
><P
>The <TT
CLASS="FILENAME"
>All Users</TT
> directory contains menu settings that are common across all
system users. The <TT
CLASS="FILENAME"
>Default User</TT
> directory contains menu entries that are
customisable per user depending on the profile settings chosen/created.</P
><P
>When a new user first logs onto an MS Windows NT4 machine a new profile is created from:</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
>All Users settings</TD
></TR
><TR
><TD
>Default User settings (contains the default NTUser.DAT file)</TD
></TR
></TBODY
></TABLE
><P
></P
><P
>When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
the following steps are followed in respect of profile handling:</P
><P
></P
><OL
TYPE="1"
><LI
><P
> The users' account information which is obtained during the logon process contains
the location of the users' desktop profile. The profile path may be local to the
machine or it may be located on a network share. If there exists a profile at the location
of the path from the user account, then this profile is copied to the location
<TT
CLASS="FILENAME"
>%SystemRoot%\Profiles\%USERNAME%</TT
>. This profile then inherits the
settings in the <TT
CLASS="FILENAME"
>All Users</TT
> profile in the <TT
CLASS="FILENAME"
>%SystemRoot%\Profiles</TT
>
location.
</P
></LI
><LI
><P
> If the user account has a profile path, but at it's location a profile does not exist,
then a new profile is created in the <TT
CLASS="FILENAME"
>%SystemRoot%\Profiles\%USERNAME%</TT
>
directory from reading the <TT
CLASS="FILENAME"
>Default User</TT
> profile.
</P
></LI
><LI
><P
> If the NETLOGON share on the authenticating server (logon server) contains a policy file
(<TT
CLASS="FILENAME"
>NTConfig.POL</TT
>) then it's contents are applied to the <TT
CLASS="FILENAME"
>NTUser.DAT</TT
>
which is applied to the <TT
CLASS="FILENAME"
>HKEY_CURRENT_USER</TT
> part of the registry.
</P
></LI
><LI
><P
> When the user logs out, if the profile is set to be a roaming profile it will be written
out to the location of the profile. The <TT
CLASS="FILENAME"
>NTuser.DAT</TT
> file is then
re-created from the contents of the <TT
CLASS="FILENAME"
>HKEY_CURRENT_USER</TT
> contents.
Thus, should there not exist in the NETLOGON share an <TT
CLASS="FILENAME"
>NTConfig.POL</TT
> at the
next logon, the effect of the provious <TT
CLASS="FILENAME"
>NTConfig.POL</TT
> will still be held
in the profile. The effect of this is known as <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>tatooing</I
></SPAN
>.
</P
></LI
></OL
><P
>MS Windows NT4 profiles may be <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Local</I
></SPAN
> or <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Roaming</I
></SPAN
>. A Local profile
will stored in the <TT
CLASS="FILENAME"
>%SystemRoot%\Profiles\%USERNAME%</TT
> location. A roaming profile will
also remain stored in the same way, unless the following registry key is created:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
"DeleteRoamingCache"=dword:00000001</PRE
>
In which case, the local copy (in <TT
CLASS="FILENAME"
>%SystemRoot%\Profiles\%USERNAME%</TT
>) will be
deleted on logout.</P
><P
>Under MS Windows NT4 default locations for common resources (like <TT
CLASS="FILENAME"
>My Documents</TT
>
may be redirected to a network share by modifying the following registry keys. These changes may be affected
via use of the System Policy Editor (to do so may require that you create your owns template extension
for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.</P
><P
>The Registry Hive key that affects the behaviour of folders that are part of the default user profile
are controlled by entries on Windows NT4 is:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> HKEY_CURRENT_USER
\Software
\Microsoft
\Windows
\CurrentVersion
\Explorer
\User Shell Folders\</PRE
></P
><P
>The above hive key contains a list of automatically managed folders. The default entries are:</P
><P
> <PRE
CLASS="PROGRAMLISTING"
> Name Default Value
-------------- -----------------------------------------
AppData %USERPROFILE%\Application Data
Desktop %USERPROFILE%\Desktop
Favorites %USERPROFILE%\Favorites
NetHood %USERPROFILE%\NetHood
PrintHood %USERPROFILE%\PrintHood
Programs %USERPROFILE%\Start Menu\Programs
Recent %USERPROFILE%\Recent
SendTo %USERPROFILE%\SendTo
Start Menu %USERPROFILE%\Start Menu
Startup %USERPROFILE%\Start Menu\Programs\Startup
</PRE
>
</P
><P
>The registry key that contains the location of the default profile settings is:
<PRE
CLASS="PROGRAMLISTING"
> HKEY_LOCAL_MACHINE
\SOFTWARE
\Microsoft
\Windows
\CurrentVersion
\Explorer
\User Shell Folders</PRE
>
The default entries are:
<PRE
CLASS="PROGRAMLISTING"
> Common Desktop %SystemRoot%\Profiles\All Users\Desktop
Common Programs %SystemRoot%\Profiles\All Users\Programs
Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu
Common Startu p %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</PRE
></P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3384"
>18.4.3. MS Windows 200x/XP</A
></H2
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> MS Windows XP Home Edition does use default per user profiles, but can not participate
in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
only from itself. While there are benefits in doing this the beauty of those MS Windows
clients that CAN participate in domain logon processes allows the administrator to create
a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
</P
></TD
></TR
></TABLE
></DIV
><P
>When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
<TT
CLASS="FILENAME"
>C:\Documents and Settings\Default User</TT
>. The administrator can modify (or change
the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum
arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
workstation. </P
><P
>When MS Windows 200x/XP participate in a domain security context, and if the default user
profile is not found, then the client will search for a default profile in the NETLOGON share
of the authenticating server. ie: In MS Windows parlance:
<TT
CLASS="FILENAME"
>%LOGONSERVER%\NETLOGON\Default User</TT
> and if one exits there it will copy this
to the workstation to the <TT
CLASS="FILENAME"
>C:\Documents and Settings\</TT
> under the Windows
login name of the user.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
should be created at the root of this share and msut be called <TT
CLASS="FILENAME"
>Default Profile</TT
>.
</P
></TD
></TR
></TABLE
></DIV
><P
>If a default profile does not exist in this location then MS Windows 200x/XP will use the local
default profile.</P
><P
>On loging out, the users' desktop profile will be stored to the location specified in the registry
settings that pertain to the user. If no specific policies have been created, or passed to the client
during the login process (as Samba does automatically), then the user's profile will be written to
the local machine only under the path <TT
CLASS="FILENAME"
>C:\Documents and Settings\%USERNAME%</TT
>.</P
><P
>Those wishing to modify the default behaviour can do so through up to three methods:</P
><P
></P
><UL
><LI
><P
> Modify the registry keys on the local machine manually and place the new default profile in the
NETLOGON share root - NOT recommended as it is maintenance intensive.
</P
></LI
><LI
><P
> Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
in the root of the NETLOGON share along with the new default profile.
</P
></LI
><LI
><P
> Create a GPO that enforces this through Active Directory, and place the new default profile
in the NETLOGON share.
</P
></LI
></UL
><P
>The Registry Hive key that affects the behaviour of folders that are part of the default user profile
are controlled by entries on Windows 200x/XP is:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> HKEY_CURRENT_USER
\Software
\Microsoft
\Windows
\CurrentVersion
\Explorer
\User Shell Folders\</PRE
></P
><P
>The above hive key contains a list of automatically managed folders. The default entries are:</P
><P
> <PRE
CLASS="PROGRAMLISTING"
> Name Default Value
-------------- -----------------------------------------
AppData %USERPROFILE%\Application Data
Cache %USERPROFILE%\Local Settings\Temporary Internet Files
Cookies %USERPROFILE%\Cookies
Desktop %USERPROFILE%\Desktop
Favorites %USERPROFILE%\Favorites
History %USERPROFILE%\Local Settings\History
Local AppData %USERPROFILE%\Local Settings\Application Data
Local Settings %USERPROFILE%\Local Settings
My Pictures %USERPROFILE%\My Documents\My Pictures
NetHood %USERPROFILE%\NetHood
Personal %USERPROFILE%\My Documents
PrintHood %USERPROFILE%\PrintHood
Programs %USERPROFILE%\Start Menu\Programs
Recent %USERPROFILE%\Recent
SendTo %USERPROFILE%\SendTo
Start Menu %USERPROFILE%\Start Menu
Startup %USERPROFILE%\Start Menu\Programs\Startup
Templates %USERPROFILE%\Templates
</PRE
>
</P
><P
>There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all
the others are of type REG_EXPAND_SZ.</P
><P
>It makes a huge difference to the speed of handling roaming user profiles if all the folders are
stored on a dedicated location on a network server. This means that it will NOT be necessary to
write Outlook PST file over the network for every login and logout.</P
><P
>To set this to a network location you could use the following examples:
<PRE
CLASS="PROGRAMLISTING"
> %LOGONSERVER%\%USERNAME%\Default Folders</PRE
>
This would store the folders in the user's home directory under a directory called "Default Folders"
You could also use:
<PRE
CLASS="PROGRAMLISTING"
> \\SambaServer\FolderShare\%USERNAME%</PRE
>
in which case the default folders will be stored in the server named <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>SambaServer</I
></SPAN
>
in the share called <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>FolderShare</I
></SPAN
> under a directory that has the name of the MS Windows
user as seen by the Linux/Unix file system.</P
><P
>Please note that once you have created a default profile share, you MUST migrate a user's profile
(default or custom) to it.</P
><P
>MS Windows 200x/XP profiles may be <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Local</I
></SPAN
> or <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Roaming</I
></SPAN
>.
A roaming profile will be cached locally unless the following registry key is created:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
"DeleteRoamingCache"=dword:00000001</PRE
>
In which case, the local cache copy will be deleted on logout.</P
></DIV
></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="policymgmt.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="interdomaintrusts.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>System and Account Policies</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Interdomain Trust Relationships</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|
