| blob | 73573361932c5095cdb7ed68194b588bcb959054 |
2 <HTML
3 ><HEAD
4 ><TITLE
6 ><META
21 ><BODY
28 ><DIV
30 ><TABLE
36 ><TR
37 ><TH
41 ></TR
42 ><TR
43 ><TD
47 ><A
51 ></TD
52 ><TD
56 ></TD
57 ><TD
61 ><A
65 ></TD
66 ></TR
67 ></TABLE
68 ><HR
71 ><DIV
73 ><H1
74 ><A
76 ></A
78 ><DIV
80 ><DL
81 ><DT
82 ><B
84 ></DT
85 ><DT
89 ></DT
90 ><DD
91 ><DL
92 ><DT
96 ></DT
97 ><DD
98 ><DL
99 ><DT
103 ></DT
104 ><DT
108 ></DT
109 ><DT
113 ></DT
114 ></DL
115 ></DD
116 ><DT
120 ></DT
121 ><DD
122 ><DL
123 ><DT
127 ></DT
128 ><DT
132 ></DT
133 ><DT
137 ></DT
138 ></DL
139 ></DD
140 ><DT
144 ></DT
145 ><DT
149 ></DT
150 ><DD
151 ><DL
152 ><DT
156 ></DT
157 ><DT
161 ></DT
162 ><DT
166 ></DT
167 ><DT
171 ></DT
172 ></DL
173 ></DD
174 ></DL
175 ></DD
176 ><DT
180 ></DT
181 ><DT
185 ></DT
186 ><DT
190 ></DT
191 ><DD
192 ><DL
193 ><DT
197 ></DT
198 ><DT
202 ></DT
203 ><DT
207 ></DT
208 ></DL
209 ></DD
210 ></DL
211 ></DIV
212 ><DIV
214 ><H1
216 ><A
219 ></H1
220 ><DIV
222 ><P
223 ></P
224 ><TABLE
228 ><TR
229 ><TD
233 ><IMG
237 ><TD
240 ><P
242 ></TD
243 ></TR
244 ></TABLE
245 ></DIV
246 ><P
247 >Before discussing how to configure roaming profiles, it is useful to see how
249 ><P
251 profiles location. However, the response does not have room for a separate
252 profiles location field, only the user's home share. This means that Win9X/Me
253 profiles are restricted to being stored in the user's home directory.</P
254 ><P
256 including a separate field for the location of the user's profiles.</P
257 ><DIV
259 ><H2
261 ><A
264 ></H2
265 ><P
267 ><DIV
269 ><H3
271 ><A
274 ></H3
275 ><P
277 following (for example):</P
278 ><P
279 ><PRE
282 >
284 This is typically implemented like:
286 <PRE
289 >
290 where %L translates to the name of the Samba server and %u translates to the user name</P
291 ><P
292 >The default for this option is \\%N\%U\profile, namely \\sambaserver\username\profile.
293 The \\N%\%U service is created automatically by the [homes] service. If you are using
294 a samba server for the profiles, you _must_ make the share specified in the logon path
295 browseable. Please refer to the man page for smb.conf in respect of the different
296 symantics of %L and %N, as well as %U and %u.</P
297 ><DIV
299 ><P
300 ></P
301 ><TABLE
305 ><TR
306 ><TD
310 ><IMG
314 ><TD
317 ><P
319 between logons. It is recommended to NOT use the <B
322 >
323 meta-service name as part of the profile share path.</P
324 ></TD
325 ></TR
326 ></TABLE
327 ></DIV
328 ></DIV
329 ><DIV
331 ><H3
333 ><A
336 ></H3
337 ><P
339 now been fixed so that <KBD
342 > now works as well, and it, too, relies
343 on the <B
347 ><P
348 >By using the logon home parameter, you are restricted to putting Win9x / Me
349 profiles in the user's home directory. But wait! There is a trick you
350 can use. If you set the following in the <B
357 ><P
358 ><PRE
361 ></P
362 ><P
364 of your home directory called <TT
368 ><P
372 > will also work, because of a feature in
373 Windows 9x / Me. It removes any directory stuff off the end of the home directory area
374 and only uses the server and share portion. That is, it looks like you
375 specified \\%L\%U for <B
379 ></DIV
380 ><DIV
382 ><H3
384 ><A
387 ></H3
388 ><P
389 >You can support profiles for both Win9X and WinNT clients by setting both the
390 <B
397 ><P
398 ><PRE
400 > logon home = \\%L\%u\.profiles
401 logon path = \\%L\profiles\%u</PRE
402 ></P
403 ></DIV
404 ></DIV
405 ><DIV
407 ><H2
409 ><A
412 ></H2
413 ><DIV
415 ><H3
417 ><A
420 ></H3
421 ><P
424 These directories and their contents will be merged with the local
425 versions stored in c:\windows\profiles\username on subsequent logins,
426 taking the most recent from each. You will need to use the [global]
428 "case sensitive = no" in order to maintain capital letters in shortcuts
429 in any of the profile folders.</P
430 ><P
431 >The user.DAT file contains all the user's preferences. If you wish to
432 enforce a set of preferences, rename their user.DAT file to user.MAN,
433 and deny them write access to this file.</P
434 ><P
435 ></P
436 ><OL
438 ><LI
439 ><P
441 select the User Profiles tab. Select the required level of
442 roaming preferences. Press OK, but do _not_ allow the computer
443 to reboot.
444 </P
445 ></LI
446 ><LI
447 ><P
449 Client for Microsoft Networks -> Preferences. Select 'Log on to
450 NT Domain'. Then, ensure that the Primary Logon is 'Client for
451 Microsoft Networks'. Press OK, and this time allow the computer
452 to reboot.
453 </P
454 ></LI
455 ></OL
456 ><P
458 If you have the Primary Logon as 'Client for Novell Networks', then
459 the profiles and logon script will be downloaded from your Novell
460 Server. If you have the Primary Logon as 'Windows Logon', then the
461 profiles will be loaded from the local machine - a bit against the
462 concept of roaming profiles, it would seem!</P
463 ><P
464 >You will now find that the Microsoft Networks Login box contains
465 [user, password, domain] instead of just [user, password]. Type in
466 the samba server's domain name (or any other domain known to exist,
467 but bear in mind that the user will be authenticated against this
468 domain and profiles downloaded from it, if that domain logon server
469 supports it), user name and user's password.</P
470 ><P
472 will inform you that 'The user has not logged on before' and asks you
473 if you wish to save the user's preferences? Select 'yes'.</P
474 ><P
476 to examine the contents of the directory specified in the "logon path"
479 ><P
480 >These folders will be cached locally on the client, and updated when
481 the user logs off (if you haven't made them read-only by then).
482 You will find that if the user creates further folders or short-cuts,
483 that the client will merge the profile contents downloaded with the
484 contents of the profile directory already on the local client, taking
485 the newest folders and short-cuts from each set.</P
486 ><P
487 >If you have made the folders / files read-only on the samba server,
488 then you will get errors from the Windows 9x / Me machine on logon and logout, as
489 it attempts to merge the local and the remote profile. Basically, if
490 you have any errors reported by the Windows 9x / Me machine, check the Unix file
491 permissions and ownership rights on the profile directory contents,
492 on the samba server.</P
493 ><P
494 >If you have problems creating user profiles, you can reset the user's
495 local desktop cache, as shown below. When this user then next logs in,
497 ><P
498 ></P
499 ><OL
501 ><LI
502 ><P
503 > instead of logging in under the [user, password, domain] dialog,
504 press escape.
505 </P
506 ></LI
507 ><LI
508 ><P
509 > run the regedit.exe program, and look in:
510 </P
511 ><P
512 > HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
513 </P
514 ><P
515 > you will find an entry, for each user, of ProfilePath. Note the
516 contents of this key (likely to be c:\windows\profiles\username),
517 then delete the key ProfilePath for the required user.
519 [Exit the registry editor].
521 </P
522 ></LI
523 ><LI
524 ><P
525 > <SPAN
527 ><I
530 ></SPAN
531 > - before deleting the contents of the
532 directory listed in the ProfilePath (this is likely to be
533 <TT
536 >, ask them if they
537 have any important files stored on their desktop or in their start menu.
538 Delete the contents of the directory ProfilePath (making a backup if any
539 of the files are needed).
540 </P
541 ><P
542 > This will have the effect of removing the local (read-only hidden
543 system file) user.DAT in their profile directory, as well as the
545 </P
546 ></LI
547 ><LI
548 ><P
549 > search for the user's .PWL password-caching file in the c:\windows
550 directory, and delete it.
551 </P
552 ></LI
553 ><LI
554 ><P
556 </P
557 ></LI
558 ><LI
559 ><P
561 above), and delete the user.DAT or user.MAN file for the user,
562 making a backup if required.
563 </P
564 ></LI
565 ></OL
566 ><P
568 and / or run a packet trace program such as ethereal or netmon.exe, and
569 look for error messages.</P
570 ><P
572 and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine
573 the example packet traces provided with Windows NT4/200x server, and see what the
574 differences are with the equivalent samba trace.</P
575 ></DIV
576 ><DIV
578 ><H3
580 ><A
583 ></H3
584 ><P
585 >When a user first logs in to a Windows NT Workstation, the profile
586 NTuser.DAT is created. The profile location can be now specified
588 ><P
589 >There is a parameter that is now available for use with NT Profiles:
593 > or any other drive, and
595 ><P
596 >The entry for the NT4 profile is a _directory_ not a file. The NT
597 help on profiles mentions that a directory is also created with a .PDS
598 extension. The user, while logging in, must have write permission to
599 create the full profile path (and the folder with the .PDS extension
600 for those situations where it might be created.)</P
601 ><P
605 NTuser.DAT. Nothing appears to be stored in the .PDS directory, and
606 its purpose is currently unknown.</P
607 ><P
608 >You can use the System Control Panel to copy a local profile onto
609 a samba server (see NT Help on profiles: it is also capable of firing
610 up the correct location in the System Control Panel for you). The
611 NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN
612 turns a profile into a mandatory one.</P
613 ><P
614 >The case of the profile is significant. The file must be called
615 NTuser.DAT or, for a mandatory profile, NTuser.MAN.</P
616 ></DIV
617 ><DIV
619 ><H3
621 ><A
624 ></H3
625 ><P
626 >You must first convert the profile from a local profile to a domain
627 profile on the MS Windows workstation as follows:</P
628 ><P
629 ></P
630 ><UL
631 ><LI
632 ><P
633 > Log on as the LOCAL workstation administrator.
634 </P
635 ></LI
636 ><LI
637 ><P
638 > Right click on the 'My Computer' Icon, select 'Properties'
639 </P
640 ></LI
641 ><LI
642 ><P
643 > Click on the 'User Profiles' tab
644 </P
645 ></LI
646 ><LI
647 ><P
648 > Select the profile you wish to convert (click on it once)
649 </P
650 ></LI
651 ><LI
652 ><P
653 > Click on the button 'Copy To'
654 </P
655 ></LI
656 ><LI
657 ><P
659 </P
660 ></LI
661 ><LI
662 ><P
664 here it will open up a selection box. Click on the domain to which the
665 profile must be accessible.
666 </P
667 ><DIV
669 ><P
670 ></P
671 ><TABLE
675 ><TR
676 ><TD
680 ><IMG
684 ><TD
687 ><P
688 >You will need to log on if a logon box opens up. Eg: In the connect
689 as: MIDEARTH\root, password: mypassword.</P
690 ></TD
691 ></TR
692 ></TABLE
693 ></DIV
694 ></LI
695 ><LI
696 ><P
697 > To make the profile capable of being used by anyone select 'Everyone'
698 </P
699 ></LI
700 ><LI
701 ><P
702 > Click OK. The Selection box will close.
703 </P
704 ></LI
705 ><LI
706 ><P
707 > Now click on the 'Ok' button to create the profile in the path you
708 nominated.
709 </P
710 ></LI
711 ></UL
712 ><P
713 >Done. You now have a profile that can be editted using the samba-3.0.0
714 <TT
716 >profiles</TT
717 > tool.</P
718 ><DIV
720 ><P
721 ></P
722 ><TABLE
726 ><TR
727 ><TD
731 ><IMG
735 ><TD
738 ><P
739 >Under NT/2K the use of mandotory profiles forces the use of MS Exchange
740 storage of mail data. That keeps desktop profiles usable.</P
741 ></TD
742 ></TR
743 ></TABLE
744 ></DIV
745 ><DIV
747 ><P
748 ></P
749 ><TABLE
753 ><TR
754 ><TD
758 ><IMG
762 ><TD
765 ><P
766 ></P
767 ><UL
768 ><LI
769 ><P
770 >This is a security check new to Windows XP (or maybe only
771 Windows XP service pack 1). It can be disabled via a group policy in
772 Active Directory. The policy is:</P
773 ><P
774 >"Computer Configuration\Administrative Templates\System\User
775 Profiles\Do not check for user ownership of Roaming Profile Folders"</P
776 ><P
778 Does the new version of samba have an Active Directory analogue? If so,
779 then you may be able to set the policy through this.</P
780 ><P
781 >If you cannot set group policies in samba, then you may be able to set
782 the policy locally on each machine. If you want to try this, then do
783 the following (N.B. I don't know for sure that this will work in the
784 same way as a domain group policy):</P
785 ></LI
786 ><LI
787 ><P
788 >On the XP workstation log in with an Administrator account.</P
789 ></LI
790 ><LI
791 ><P
793 ></LI
794 ><LI
795 ><P
797 ></LI
798 ><LI
799 ><P
801 ></LI
802 ><LI
803 ><P
804 >A Microsoft Management Console should appear.</P
805 ></LI
806 ><LI
807 ><P
809 ></LI
810 ><LI
811 ><P
813 ></LI
814 ><LI
815 ><P
817 ></LI
818 ><LI
819 ><P
821 ></LI
822 ><LI
823 ><P
825 ></LI
826 ><LI
827 ><P
829 ></LI
830 ><LI
831 ><P
833 ></LI
834 ><LI
835 ><P
837 ></LI
838 ><LI
839 ><P
841 ></LI
842 ><LI
843 ><P
845 ></LI
846 ><LI
847 ><P
849 ></LI
850 ><LI
851 ><P
852 >Close the whole console. You do not need to save the settings (this
853 refers to the console settings rather than the policies you have
854 changed).</P
855 ></LI
856 ><LI
857 ><P
859 ></LI
860 ></UL
861 ></TD
862 ></TR
863 ></TABLE
864 ></DIV
865 ></DIV
866 ></DIV
867 ><DIV
869 ><H2
871 ><A
874 ></H2
875 ><P
876 >Sharing of desktop profiles between Windows versions is NOT recommended.
877 Desktop profiles are an evolving phenomenon and profiles for later versions
878 of MS Windows clients add features that may interfere with earlier versions
879 of MS Windows clients. Probably the more salient reason to NOT mix profiles
880 is that when logging off an earlier version of MS Windows the older format
881 of profile contents may overwrite information that belongs to the newer
882 version resulting in loss of profile information content when that user logs
883 on again with the newer version of MS Windows.</P
884 ><P
885 >If you then want to share the same Start Menu / Desktop with W9x/Me, you will
886 need to specify a common location for the profiles. The smb.conf parameters
887 that need to be common are <SPAN
889 ><I
892 ></SPAN
893 > and
894 <SPAN
896 ><I
899 ></SPAN
901 ><P
902 >If you have this set up correctly, you will find separate user.DAT and
903 NTuser.DAT files in the same profile directory.</P
904 ></DIV
905 ><DIV
907 ><H2
909 ><A
912 ></H2
913 ><P
914 >There is nothing to stop you specifying any path that you like for the
915 location of users' profiles. Therefore, you could specify that the
916 profile be stored on a samba server, or any other SMB server, as long as
917 that SMB server supports encrypted passwords.</P
918 ><DIV
920 ><H3
922 ><A
925 ></H3
926 ><P
927 >Unfortunately, the Resource Kit information is specific to the version of MS Windows
929 ><P
931 ><P
932 ></P
933 ><UL
934 ><LI
935 ><P
936 >On your NT4 Domain Controller, right click on 'My Computer', then
937 select the tab labelled 'User Profiles'.</P
938 ></LI
939 ><LI
940 ><P
942 ><DIV
944 ><P
945 ></P
946 ><TABLE
950 ><TR
951 ><TD
955 ><IMG
959 ><TD
962 ><P
964 create a group profile. You can give the user 'Everyone' rights to the
965 profile you copy this to. That is what you need to do, since your samba
966 domain is not a member of a trust relationship with your NT4 PDC.</P
967 ></TD
968 ></TR
969 ></TABLE
970 ></DIV
971 ></LI
972 ><LI
973 ><P
975 ></LI
976 ><LI
977 ><P
978 >In the box labelled 'Copy Profile to' add your new path, eg:
979 <TT
982 ></P
983 ></LI
984 ><LI
985 ><P
987 ></LI
988 ><LI
989 ><P
990 >Click on the group 'Everyone' and then click OK. This closes the
991 'chose user' box.</P
992 ></LI
993 ><LI
994 ><P
996 ></LI
997 ></UL
998 ><P
1000 ></DIV
1001 ><DIV
1003 ><H3
1005 ><A
1008 ></H3
1009 ><P
1010 >You should obtain the SID of your NT4 domain. You can use smbpasswd to do
1011 this. Read the man page.</P
1012 ><P
1014 using the net samsync method. This way you can retain your profile
1015 settings as well as all your users.</P
1016 ></DIV
1017 ><DIV
1019 ><H3
1021 ><A
1024 ></H3
1025 ><P
1026 >The W2K professional resource kit has moveuser.exe. moveuser.exe changes
1027 the security of a profile from one user to another. This allows the account
1028 domain to change, and/or the user name to change.</P
1029 ></DIV
1030 ><DIV
1032 ><H3
1034 ><A
1037 ></H3
1038 ><P
1040 Resource Kit.</P
1041 ><P
1043 the following key:
1044 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</P
1045 ><P
1046 >Under the ProfileList key, there will be subkeys named with the SIDs of the
1047 users who have logged on to this computer. (To find the profile information
1048 for the user whose locally cached profile you want to move, find the SID for
1049 the user with the GetSID.exe utility.) Inside of the appropriate user's
1050 subkey, you will see a string value named ProfileImagePath.</P
1051 ></DIV
1052 ></DIV
1053 ></DIV
1054 ><DIV
1056 ><H1
1058 ><A
1061 ></H1
1062 ><P
1063 >A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
1064 During the user's session it may be possible to change the desktop environment, but
1065 as the user logs out all changes made will be lost. If it is desired to NOT allow the
1066 user any ability to change the desktop environment then this must be done through
1067 policy settings. See previous chapter.</P
1068 ><DIV
1070 ><P
1071 ></P
1072 ><TABLE
1076 ><TR
1077 ><TD
1081 ><IMG
1085 ><TD
1088 ><P
1089 >Under NO circumstances should the profile directory (or it's contents) be made read-only
1090 as this may render the profile un-usable.</P
1091 ></TD
1092 ></TR
1093 ></TABLE
1094 ></DIV
1095 ><P
1097 also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
1098 file in the copied profile and rename it to NTUser.MAN.</P
1099 ><P
1101 affect a mandatory profile.</P
1102 ></DIV
1103 ><DIV
1105 ><H1
1107 ><A
1110 ></H1
1111 ><P
1112 >Most organisations are arranged into departments. There is a nice benenfit in
1113 this fact since usually most users in a department will require the same desktop
1114 applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
1115 use of Group Profiles. A Group Profile is a profile that is created firstly using
1116 a template (example) user. Then using the profile migration tool (see above) the
1117 profile is assigned access rights for the user group that needs to be given access
1118 to the group profile.</P
1119 ><P
1120 >The next step is rather important. PLEASE NOTE: Instead of assigning a group profile
1121 to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
1122 the now modified profile.</P
1123 ><DIV
1125 ><P
1126 ></P
1127 ><TABLE
1131 ><TR
1132 ><TD
1136 ><IMG
1140 ><TD
1143 ><P
1144 > Be careful with group profiles, if the user who is a member of a group also
1145 has a personal profile, then the result will be a fusion (merge) of the two.
1146 </P
1147 ></TD
1148 ></TR
1149 ></TABLE
1150 ></DIV
1151 ></DIV
1152 ><DIV
1154 ><H1
1156 ><A
1159 ></H1
1160 ><P
1162 a profile does not already exist. Armed with a knowledge of where the default profile
1163 is located on the Windows workstation, and knowing which registry keys affect the path
1164 from which the default profile is created, it is possible to modify the default profile
1165 to one that has been optimised for the site. This has significant administrative
1166 advantages.</P
1167 ><DIV
1169 ><H2
1171 ><A
1174 ></H2
1175 ><P
1176 >To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System
1177 Policy Editor or change the registry directly.</P
1178 ><P
1180 select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System,
1181 select User Profiles, click on the enable box. Do not forget to save the registry changes.</P
1182 ><P
1183 >To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive
1184 <TT
1187 >. Now add a DWORD type key with the name
1188 "User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.</P
1189 ><DIV
1191 ><H3
1193 ><A
1196 ></H3
1197 ><P
1199 <TT
1202 >, is checked
1203 for an existing entry for that user:</P
1204 ><P
1205 >If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
1206 version of the user profile. Windows 9x / Me also checks the user's home directory (or other
1207 specified directory if the location has been modified) on the server for the User Profile.
1208 If a profile exists in both locations, the newer of the two is used. If the User Profile exists
1209 on the server, but does not exist on the local machine, the profile on the server is downloaded
1210 and used. If the User Profile only exists on the local machine, that copy is used.</P
1211 ><P
1212 >If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
1213 machine is used and is copied to a newly created folder for the logged on user. At log off, any
1214 changes that the user made are written to the user's local profile. If the user has a roaming
1215 profile, the changes are written to the user's profile on the server.</P
1216 ></DIV
1217 ></DIV
1218 ><DIV
1220 ><H2
1222 ><A
1225 ></H2
1226 ><P
1227 >On MS Windows NT4 the default user profile is obtained from the location
1228 <TT
1231 > which in a default installation will translate to
1232 <TT
1235 >. Under this directory on a clean install there will be
1240 ><P
1244 > directory contains menu settings that are common across all
1245 system users. The <TT
1248 > directory contains menu entries that are
1249 customisable per user depending on the profile settings chosen/created.</P
1250 ><P
1252 ><P
1253 ></P
1254 ><TABLE
1256 ><TBODY
1257 ><TR
1258 ><TD
1260 ></TR
1261 ><TR
1262 ><TD
1264 ></TR
1265 ></TBODY
1266 ></TABLE
1267 ><P
1268 ></P
1269 ><P
1270 >When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
1271 the following steps are followed in respect of profile handling:</P
1272 ><P
1273 ></P
1274 ><OL
1276 ><LI
1277 ><P
1278 > The users' account information which is obtained during the logon process contains
1279 the location of the users' desktop profile. The profile path may be local to the
1280 machine or it may be located on a network share. If there exists a profile at the location
1281 of the path from the user account, then this profile is copied to the location
1282 <TT
1285 >. This profile then inherits the
1286 settings in the <TT
1292 >
1293 location.
1294 </P
1295 ></LI
1296 ><LI
1297 ><P
1298 > If the user account has a profile path, but at it's location a profile does not exist,
1299 then a new profile is created in the <TT
1302 >
1303 directory from reading the <TT
1306 > profile.
1307 </P
1308 ></LI
1309 ><LI
1310 ><P
1311 > If the NETLOGON share on the authenticating server (logon server) contains a policy file
1312 (<TT
1318 >
1319 which is applied to the <TT
1322 > part of the registry.
1323 </P
1324 ></LI
1325 ><LI
1326 ><P
1327 > When the user logs out, if the profile is set to be a roaming profile it will be written
1328 out to the location of the profile. The <TT
1331 > file is then
1332 re-created from the contents of the <TT
1335 > contents.
1336 Thus, should there not exist in the NETLOGON share an <TT
1339 > at the
1340 next logon, the effect of the provious <TT
1343 > will still be held
1344 in the profile. The effect of this is known as <SPAN
1346 ><I
1349 ></SPAN
1350 >.
1351 </P
1352 ></LI
1353 ></OL
1354 ><P
1357 ><I
1360 ></SPAN
1363 ><I
1366 ></SPAN
1367 >. A Local profile
1368 will stored in the <TT
1371 > location. A roaming profile will
1372 also remain stored in the same way, unless the following registry key is created:</P
1373 ><P
1374 ><PRE
1376 > HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
1378 >
1380 In which case, the local copy (in <TT
1383 >) will be
1384 deleted on logout.</P
1385 ><P
1389 >
1390 may be redirected to a network share by modifying the following registry keys. These changes may be affected
1391 via use of the System Policy Editor (to do so may require that you create your owns template extension
1392 for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
1393 creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.</P
1394 ><P
1395 >The Registry Hive key that affects the behaviour of folders that are part of the default user profile
1396 are controlled by entries on Windows NT4 is:</P
1397 ><P
1398 ><PRE
1400 > HKEY_CURRENT_USER
1401 \Software
1402 \Microsoft
1403 \Windows
1404 \CurrentVersion
1405 \Explorer
1406 \User Shell Folders\</PRE
1407 ></P
1408 ><P
1409 >The above hive key contains a list of automatically managed folders. The default entries are:</P
1410 ><P
1411 > <PRE
1413 > Name Default Value
1414 -------------- -----------------------------------------
1415 AppData %USERPROFILE%\Application Data
1416 Desktop %USERPROFILE%\Desktop
1417 Favorites %USERPROFILE%\Favorites
1418 NetHood %USERPROFILE%\NetHood
1419 PrintHood %USERPROFILE%\PrintHood
1420 Programs %USERPROFILE%\Start Menu\Programs
1421 Recent %USERPROFILE%\Recent
1422 SendTo %USERPROFILE%\SendTo
1423 Start Menu %USERPROFILE%\Start Menu
1424 Startup %USERPROFILE%\Start Menu\Programs\Startup
1425 </PRE
1426 >
1427 </P
1428 ><P
1429 >The registry key that contains the location of the default profile settings is:
1431 <PRE
1433 > HKEY_LOCAL_MACHINE
1434 \SOFTWARE
1435 \Microsoft
1436 \Windows
1437 \CurrentVersion
1438 \Explorer
1439 \User Shell Folders</PRE
1440 >
1442 The default entries are:
1444 <PRE
1446 > Common Desktop %SystemRoot%\Profiles\All Users\Desktop
1447 Common Programs %SystemRoot%\Profiles\All Users\Programs
1448 Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu
1449 Common Startu p %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup</PRE
1450 ></P
1451 ></DIV
1452 ><DIV
1454 ><H2
1456 ><A
1459 ></H2
1460 ><DIV
1462 ><P
1463 ></P
1464 ><TABLE
1468 ><TR
1469 ><TD
1473 ><IMG
1477 ><TD
1480 ><P
1481 > MS Windows XP Home Edition does use default per user profiles, but can not participate
1482 in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
1483 only from itself. While there are benefits in doing this the beauty of those MS Windows
1484 clients that CAN participate in domain logon processes allows the administrator to create
1485 a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
1486 </P
1487 ></TD
1488 ></TR
1489 ></TABLE
1490 ></DIV
1491 ><P
1492 >When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
1493 <TT
1496 >. The administrator can modify (or change
1497 the contents of this location and MS Windows 200x/XP will gladly user it. This is far from the optimum
1498 arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
1499 workstation. </P
1500 ><P
1502 profile is not found, then the client will search for a default profile in the NETLOGON share
1503 of the authenticating server. ie: In MS Windows parlance:
1504 <TT
1507 > and if one exits there it will copy this
1508 to the workstation to the <TT
1511 > under the Windows
1512 login name of the user.</P
1513 ><DIV
1515 ><P
1516 ></P
1517 ><TABLE
1521 ><TR
1522 ><TD
1526 ><IMG
1530 ><TD
1533 ><P
1534 > This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory
1535 should be created at the root of this share and msut be called <TT
1538 >.
1539 </P
1540 ></TD
1541 ></TR
1542 ></TABLE
1543 ></DIV
1544 ><P
1545 >If a default profile does not exist in this location then MS Windows 200x/XP will use the local
1546 default profile.</P
1547 ><P
1548 >On loging out, the users' desktop profile will be stored to the location specified in the registry
1549 settings that pertain to the user. If no specific policies have been created, or passed to the client
1550 during the login process (as Samba does automatically), then the user's profile will be written to
1551 the local machine only under the path <TT
1555 ><P
1557 ><P
1558 ></P
1559 ><UL
1560 ><LI
1561 ><P
1562 > Modify the registry keys on the local machine manually and place the new default profile in the
1563 NETLOGON share root - NOT recommended as it is maintenance intensive.
1564 </P
1565 ></LI
1566 ><LI
1567 ><P
1568 > Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
1569 in the root of the NETLOGON share along with the new default profile.
1570 </P
1571 ></LI
1572 ><LI
1573 ><P
1574 > Create a GPO that enforces this through Active Directory, and place the new default profile
1575 in the NETLOGON share.
1576 </P
1577 ></LI
1578 ></UL
1579 ><P
1580 >The Registry Hive key that affects the behaviour of folders that are part of the default user profile
1582 ><P
1583 ><PRE
1585 > HKEY_CURRENT_USER
1586 \Software
1587 \Microsoft
1588 \Windows
1589 \CurrentVersion
1590 \Explorer
1591 \User Shell Folders\</PRE
1592 ></P
1593 ><P
1594 >The above hive key contains a list of automatically managed folders. The default entries are:</P
1595 ><P
1596 > <PRE
1598 > Name Default Value
1599 -------------- -----------------------------------------
1600 AppData %USERPROFILE%\Application Data
1601 Cache %USERPROFILE%\Local Settings\Temporary Internet Files
1602 Cookies %USERPROFILE%\Cookies
1603 Desktop %USERPROFILE%\Desktop
1604 Favorites %USERPROFILE%\Favorites
1605 History %USERPROFILE%\Local Settings\History
1606 Local AppData %USERPROFILE%\Local Settings\Application Data
1607 Local Settings %USERPROFILE%\Local Settings
1608 My Pictures %USERPROFILE%\My Documents\My Pictures
1609 NetHood %USERPROFILE%\NetHood
1610 Personal %USERPROFILE%\My Documents
1611 PrintHood %USERPROFILE%\PrintHood
1612 Programs %USERPROFILE%\Start Menu\Programs
1613 Recent %USERPROFILE%\Recent
1614 SendTo %USERPROFILE%\SendTo
1615 Start Menu %USERPROFILE%\Start Menu
1616 Startup %USERPROFILE%\Start Menu\Programs\Startup
1617 Templates %USERPROFILE%\Templates
1618 </PRE
1619 >
1620 </P
1621 ><P
1622 >There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all
1623 the others are of type REG_EXPAND_SZ.</P
1624 ><P
1625 >It makes a huge difference to the speed of handling roaming user profiles if all the folders are
1626 stored on a dedicated location on a network server. This means that it will NOT be necessary to
1627 write Outlook PST file over the network for every login and logout.</P
1628 ><P
1629 >To set this to a network location you could use the following examples:
1631 <PRE
1634 >
1636 This would store the folders in the user's home directory under a directory called "Default Folders"
1638 You could also use:
1640 <PRE
1643 >
1645 in which case the default folders will be stored in the server named <SPAN
1647 ><I
1650 ></SPAN
1651 >
1652 in the share called <SPAN
1654 ><I
1657 ></SPAN
1658 > under a directory that has the name of the MS Windows
1659 user as seen by the Linux/Unix file system.</P
1660 ><P
1661 >Please note that once you have created a default profile share, you MUST migrate a user's profile
1662 (default or custom) to it.</P
1663 ><P
1666 ><I
1669 ></SPAN
1672 ><I
1675 ></SPAN
1676 >.
1677 A roaming profile will be cached locally unless the following registry key is created:</P
1678 ><P
1679 ><PRE
1681 > HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
1683 >
1685 In which case, the local cache copy will be deleted on logout.</P
1686 ></DIV
1687 ></DIV
1688 ></DIV
1689 ><DIV
1691 ><HR
1699 ><TR
1700 ><TD
1704 ><A
1708 ></TD
1709 ><TD
1713 ><A
1717 ></TD
1718 ><TD
1722 ><A
1726 ></TD
1727 ></TR
1728 ><TR
1729 ><TD
1734 ><TD
1738 ><A
1742 ></TD
1743 ><TD
1748 ></TR
1749 ></TABLE
1750 ></DIV
1751 ></BODY
1752 ></HTML
1753 >