| blob | 99475261947ce6ab59bad84ea245dd9e8bee67b6 |
1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 24. Desktop Profile Management</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.60.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="PolicyMgmt.html" title="Chapter 23. System and Account Policies"><link rel="next" href="pam.html" title="Chapter 25. PAM-Based Distributed Authentication"></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 24. Desktop Profile Management</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="PolicyMgmt.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="pam.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter 24. Desktop Profile Management</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><tt class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="ProfileMgmt.html#id2954425">Features and Benefits</a></dt><dt><a href="ProfileMgmt.html#id2954459">Roaming Profiles</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2954500">Samba Configuration for Profile Handling</a></dt><dt><a href="ProfileMgmt.html#id2955058">Windows Client Profile Configuration Information</a></dt><dt><a href="ProfileMgmt.html#id2956404">Sharing Profiles between W9x/Me and NT4/200x/XP Workstations</a></dt><dt><a href="ProfileMgmt.html#id2956492">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2956822">Mandatory Profiles</a></dt><dt><a href="ProfileMgmt.html#id2956917">Creating and Managing Group Profiles</a></dt><dt><a href="ProfileMgmt.html#id2956970">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2956999">MS Windows 9x/Me</a></dt><dt><a href="ProfileMgmt.html#id2957150">MS Windows NT4 Workstation</a></dt><dt><a href="ProfileMgmt.html#id2957772">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2958338">Common Errors</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2958351">Configuring Roaming Profiles for a Few Users or Groups</a></dt><dt><a href="ProfileMgmt.html#id2958416">Cannot Use Roaming Profiles</a></dt><dt><a href="ProfileMgmt.html#id2958626">Changing the Default Profile</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954425"></a>Features and Benefits</h2></div></div><div></div></div><p>
2 Roaming profiles are feared by some, hated by a few, loved by many, and a Godsend for
3 some administrators.
4 </p><p>
5 Roaming profiles allow an administrator to make available a consistent user desktop
6 as the user moves from one machine to another. This chapter provides much information
7 regarding how to configure and manage roaming profiles.
8 </p><p>
9 While roaming profiles might sound like nirvana to some, they are a real and tangible
10 problem to others. In particular, users of mobile computing tools, where often there may not
11 be a sustained network connection, are often better served by purely local profiles.
12 This chapter provides information to help the Samba administrator deal with those
13 situations.
14 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2954459"></a>Roaming Profiles</h2></div></div><div></div></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
16 </p></div><p>
17 Before discussing how to configure roaming profiles, it is useful to see how
19 </p><p>
20 Windows 9x/Me clients send a NetUserGetInfo request to the server to get the user's
21 profiles location. However, the response does not have room for a separate
22 profiles location field, only the user's home share. This means that Windows 9x/Me
23 profiles are restricted to being stored in the user's home directory.
24 </p><p>
25 Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields
26 including a separate field for the location of the user's profiles.
27 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2954500"></a>Samba Configuration for Profile Handling</h3></div></div><div></div></div><p>
28 This section documents how to configure Samba for MS Windows client profile support.
29 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2954513"></a>NT4/200x User Profiles</h4></div></div><div></div></div><p>
30 For example, to support Windows NT4/200x clients, set the followoing in the [global] section of the <tt class="filename">smb.conf</tt> file:
31 </p><p>
32 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</tt></i></td></tr></table><p>
34 This is typically implemented like:
36 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon path = \\%L\Profiles\%u</tt></i></td></tr></table><p>
37 where “<span class="quote">%L</span>” translates to the name of the Samba server and “<span class="quote">%u</span>” translates to the user name.
38 </p><p>
39 The default for this option is <tt class="filename">\\%N\%U\profile</tt>, namely <tt class="filename">\\sambaserver\username\profile</tt>.
40 The <tt class="filename">\\N%\%U</tt> service is created automatically by the [homes] service. If you are using
41 a Samba server for the profiles, you must make the share that is specified in the logon path
42 browseable. Please refer to the man page for <tt class="filename">smb.conf</tt> in respect of the different
43 semantics of “<span class="quote">%L</span>” and “<span class="quote">%N</span>”, as well as “<span class="quote">%U</span>” and “<span class="quote">%u</span>”.
44 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
45 MS Windows NT/200x clients at times do not disconnect a connection to a server between logons. It is recommended
46 to not use the <i class="parameter"><tt>homes</tt></i> meta-service name as part of the profile share path.
47 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2954652"></a>Windows 9x/Me User Profiles</h4></div></div><div></div></div><p>
48 To support Windows 9x/Me clients, you must use the <a class="indexterm" name="id2954664"></a><i class="parameter"><tt>logon home</tt></i>
49 parameter. Samba has been fixed so <b class="userinput"><tt>net use /home</tt></b> now works as well and it, too, relies
51 </p><p>
52 By using the logon home parameter, you are restricted to putting Windows 9x/Me profiles in the user's home
53 directory. But wait! There is a trick you can use. If you set the following in the
54 <i class="parameter"><tt>[global]</tt></i> section of your <tt class="filename">smb.conf</tt> file:
55 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon home = \\%L\%U\.profiles</tt></i></td></tr></table><p>
56 then your Windows 9x/Me clients will dutifully put their clients in a subdirectory
58 </p><p>
59 Not only that, but <b class="userinput"><tt>net use /home</tt></b> will also work because of a feature in
60 Windows 9x/Me. It removes any directory stuff off the end of the home directory area
61 and only uses the server and share portion. That is, it looks like you
62 specified <tt class="filename">\\%L\%U</tt> for <a class="indexterm" name="id2954767"></a><i class="parameter"><tt>logon home</tt></i>.
63 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2954783"></a>Mixed Windows 9x/Me and Windows NT4/200x User Profiles</h4></div></div><div></div></div><p>
64 You can support profiles for Windows 9x and Windows NT clients by setting both the
65 <a class="indexterm" name="id2954795"></a><i class="parameter"><tt>logon home</tt></i> and <a class="indexterm" name="id2954809"></a><i class="parameter"><tt>logon path</tt></i> parameters. For example:
66 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon home = \\%L\%u\.profiles</tt></i></td></tr><tr><td><i class="parameter"><tt>logon path = \\%L\profiles\%u</tt></i></td></tr></table></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2954850"></a>Disabling Roaming Profile Support</h4></div></div><div></div></div><p>
67 A question often asked is: “<span class="quote">How may I enforce use of local profiles?</span>” or
69 </p><p>
71 There are three ways of doing this:
73 </p><div class="variablelist"><dl><dt><span class="term">In <tt class="filename">smb.conf</tt></span></dt><dd><p>
74 Affect the following settings and ALL clients will be forced to use a local profile:
75 <a class="indexterm" name="id2954920"></a><i class="parameter"><tt>logon home</tt></i> and <a class="indexterm" name="id2954933"></a><i class="parameter"><tt>logon path</tt></i>
77 By using the Microsoft Management Console gpedit.msc to instruct your MS Windows XP
78 machine to use only a local profile. This, of course, modifies registry settings. The full
79 path to the option is:
81 Local Computer Policy\
82 Computer Configuration\
83 Administrative Templates\
84 System\
85 User Profiles\
87 Disable: Only Allow Local User Profiles
88 Disable: Prevent Roaming Profile Change from Propagating to the Server
89 </pre><p>
90 </p></dd><dt><span class="term">Change of Profile Type:</span></dt><dd><p>From the start menu right-click on <span class="guiicon">My Computer icon</span>,
91 select <span class="guimenuitem">Properties</span>, click on the <span class="guilabel">User Profiles</span>
92 tab, select the profile you wish to change from
95 </p></dd></dl></div><p>
96 Consult the MS Windows registry guide for your particular MS Windows version for more information
97 about which registry keys to change to enforce use of only local user profiles.
98 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
99 The specifics of how to convert a local profile to a roaming profile, or a roaming profile
100 to a local one vary according to the version of MS Windows you are running. Consult the Microsoft MS
101 Windows Resource Kit for your version of Windows for specific information.
102 </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2955058"></a>Windows Client Profile Configuration Information</h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2955066"></a>Windows 9x/Me Profile Setup</h4></div></div><div></div></div><p>
103 When a user first logs in on Windows 9X, the file user.DAT is created, as are folders
104 <tt class="filename">Start Menu</tt>, <tt class="filename">Desktop</tt>, <tt class="filename">Programs</tt>, and
105 <tt class="filename">Nethood</tt>. These directories and their contents will be merged with the local
106 versions stored in <tt class="filename">c:\windows\profiles\username</tt> on subsequent logins, taking the
107 most recent from each. You will need to use the <i class="parameter"><tt>[global]</tt></i> options
108 <a class="indexterm" name="id2955121"></a><i class="parameter"><tt>preserve case</tt></i> = yes,
109 <a class="indexterm" name="id2955136"></a><i class="parameter"><tt>short preserve case</tt></i> = yes and
111 in order to maintain capital letters in shortcuts in any of the profile folders.
112 </p><p>
113 The <tt class="filename">user.DAT</tt> file contains all the user's preferences. If you wish to enforce a set of preferences,
114 rename their <tt class="filename">user.DAT</tt> file to <tt class="filename">user.MAN</tt>, and deny them write access to this file.
117 <span class="guimenuitem">Passwords</span> and select the <span class="guilabel">User Profiles</span> tab.
118 Select the required level of roaming preferences. Press <span class="guibutton">OK</span>, but do not
119 allow the computer to reboot.
120 </p></li><li><p>
122 <span class="guimenuitem">Network</span> -> <span class="guimenuitem">Client for Microsoft Networks</span>
123 -> <span class="guilabel">Preferences</span>. Select <span class="guilabel">Log on to NT Domain</span>. Then,
124 ensure that the Primary Logon is <span class="guilabel">Client for Microsoft Networks</span>. Press
126 </p></li></ol></div><p> Under Windows 9x/ME, profiles are downloaded from the Primary Logon. If you have the Primary Logon
127 as “<span class="quote">Client for Novell Networks</span>”, then the profiles and logon script will be downloaded from
128 your Novell Server. If you have the Primary Logon as “<span class="quote">Windows Logon</span>”, then the profiles will
129 be loaded from the local machine a bit against the concept of roaming profiles, it would seem! </p><p>
130 You will now find that the Microsoft Networks Login box contains <tt class="constant">[user, password, domain]</tt> instead
131 of just <tt class="constant">[user, password]</tt>. Type in the Samba server's domain name (or any other domain known to exist,
132 but bear in mind that the user will be authenticated against this domain and profiles downloaded from it,
133 if that domain logon server supports it), user name and user's password.
134 </p><p> Once the user has been successfully validated, the Windows 9x/Me machine will inform you that
135 <tt class="computeroutput">The user has not logged on before</tt> and asks you <tt class="computeroutput">Do you
136 wish to save the user's preferences?</tt> Select <span class="guibutton">Yes</span>. </p><p> Once the Windows 9x/Me client comes up with the desktop, you should be able to examine the
137 contents of the directory specified in the <a class="indexterm" name="id2955374"></a><i class="parameter"><tt>logon path</tt></i> on
138 the Samba server and verify that the <tt class="filename">Desktop</tt>, <tt class="filename">Start Menu</tt>,
139 <tt class="filename">Programs</tt> and <tt class="filename">Nethood</tt> folders have been created. </p><p> These folders will be cached locally on the client, and updated when the user logs off (if
140 you haven't made them read-only by then). You will find that if the user creates further folders or
141 shortcut, that the client will merge the profile contents downloaded with the contents of the profile
142 directory already on the local client, taking the newest folders and shortcut from each set. </p><p> If you have made the folders/files read-only on the Samba server, then you will get errors from
143 the Windows 9x/Me machine on logon and logout as it attempts to merge the local and remote profile.
144 Basically, if you have any errors reported by the Windows 9x/Me machine, check the UNIX file permissions
145 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
146 shown below. When this user next logs in, the user will be told that he/she is logging in “<span class="quote">for
151 Instead of logging in under the [user, password, domain] dialog, press <span class="guibutton">escape</span>.
152 </p></li><li><p>
154 </p><p>
156 </p><p>
157 You will find an entry for each user of ProfilePath. Note the contents of this key
160 </p></li><li><p>
161 Exit the registry editor.
162 </p></li><li><p>
163 Search for the user's .PWL password-caching file in the <tt class="filename">c:\windows</tt> directory, and delete it.
164 </p></li><li><p>
165 Log off the Windows 9x/Me client.
166 </p></li><li><p>
167 Check the contents of the profile path (see <a class="indexterm" name="id2955562"></a><i class="parameter"><tt>logon path</tt></i>
168 described above) and delete the <tt class="filename">user.DAT</tt> or <tt class="filename">user.MAN</tt>
169 file for the user, making a backup if required.
170 </p></li></ol></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
171 Before deleting the contents of the directory listed in the <i class="parameter"><tt>ProfilePath</tt></i>
172 (this is likely to be <tt class="filename">c:\windows\profiles\username)</tt>, ask the owner if they have
173 any important files stored on their desktop or in their start menu. Delete the contents of the
174 directory <i class="parameter"><tt>ProfilePath</tt></i> (making a backup if any of the files are needed).
175 </p><p>
176 This will have the effect of removing the local (read-only hidden system file) <tt class="filename">user.DAT</tt>
177 in their profile directory, as well as the local “<span class="quote">desktop,</span>” “<span class="quote">nethood,</span>”
178 “<span class="quote">start menu,</span>” and “<span class="quote">programs</span>” folders.
179 </p></div><p>
181 sniffer program such as ethereal or <b class="command">netmon.exe</b>, and look for error messages.
182 </p><p> If you have access to an Windows NT4/200x server, then first set up roaming profiles and/or
183 netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces
184 provided with Windows NT4/200x server, and see what the differences are with the equivalent Samba trace.
185 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2955678"></a>Windows NT4 Workstation</h4></div></div><div></div></div><p> When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile
186 location can be now specified through the <a class="indexterm" name="id2955691"></a><i class="parameter"><tt>logon path</tt></i> parameter.
187 </p><p> There is a parameter that is now available for use with NT Profiles: <a class="indexterm" name="id2955710"></a><i class="parameter"><tt>logon drive</tt></i>.
188 This should be set to <tt class="filename">H:</tt> or any other drive, and should be used in conjunction with
189 the new <a class="indexterm" name="id2955733"></a><i class="parameter"><tt>logon home</tt></i> parameter. </p><p> The entry for the NT4 profile is a directory not a file. The NT help on Profiles mentions that a
190 directory is also created with a .PDS extension. The user, while logging in, must have write permission
191 to create the full profile path (and the folder with the .PDS extension for those situations where it
192 might be created.) </p><p> In the profile directory, Windows NT4 creates more folders than Windows 9x/Me. It creates
193 <tt class="filename">Application Data</tt> and others, as well as <tt class="filename">Desktop</tt>,
194 <tt class="filename">Nethood</tt>, <tt class="filename">Start Menu,</tt> and <tt class="filename">Programs</tt>.
195 The profile itself is stored in a file <tt class="filename">NTuser.DAT</tt>. Nothing appears to be stored
196 in the .PDS directory, and its purpose is currently unknown. </p><p> You can use the <span class="application">System Control Panel</span> to copy a local profile onto
197 a Samba server (see NT Help on Profiles; it is also capable of firing up the correct location in the
198 <span class="application">System Control Panel</span> for you). The NT Help file also mentions that renaming
199 <tt class="filename">NTuser.DAT</tt> to <tt class="filename">NTuser.MAN</tt> turns a profile into a mandatory one.
200 </p><p> The case of the profile is significant. The file must be called <tt class="filename">NTuser.DAT</tt>
201 or, for a mandatory profile, <tt class="filename">NTuser.MAN</tt>. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2955863"></a>Windows 2000/XP Professional</h4></div></div><div></div></div><p> You must first convert the profile from a local profile to a domain profile on the MS Windows
202 workstation as follows: </p><div class="procedure"><ol type="1"><li><p> Log on as the <span class="emphasis"><em>local</em></span> workstation administrator. </p></li><li><p> Right-click on the <span class="guiicon">My Computer</span> Icon, select
203 <span class="guimenuitem">Properties</span>.</p></li><li><p> Click on the <span class="guilabel">User Profiles</span> tab.</p></li><li><p> Select the profile you wish to convert (click it once).</p></li><li><p> Click on the <span class="guibutton">Copy To</span> button.</p></li><li><p> In the <span class="guilabel">Permitted to use</span> box, click on the
204 <span class="guibutton">Change</span> button. </p></li><li><p> Click on the <span class="guilabel">Look in</span> area that lists the machine name. When you click here, it will
205 open up a selection box. Click on the domain to which the profile must be accessible. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>You will need to log on if a logon box opens up.
207 <i class="replaceable"><tt>mypassword</tt></i>.</p></div></li><li><p> To make the profile capable of being used by anyone, select “<span class="quote">Everyone</span>”. </p></li><li><p> Click on <span class="guibutton">OK</span> and the Selection box will close. </p></li><li><p> Now click on <span class="guibutton">OK</span> to create the profile in the path
208 you nominated. </p></li></ol></div><p> Done. You now have a profile that can be edited using the Samba <b class="command">profiles</b> tool.
209 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
210 Under Windows NT/200x, the use of mandatory profiles forces the use of MS Exchange storage of mail
211 data and keeps it out of the desktop profile. That keeps desktop profiles from becoming unusable.
212 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2956079"></a>Windows XP Service Pack 1</h5></div></div><div></div></div><p>
213 There is a security check new to Windows XP (or maybe only Windows XP service pack 1).
214 It can be disabled via a group policy in the Active Directory. The policy is called:
215 </p><p>
216 <tt class="filename">Computer Configuration\Administrative Templates\System\User Profiles\Do not check for
217 user ownership of Roaming Profile Folders</tt>i
218 </p><p>
220 </p><p>
221 Does the new version of Samba have an Active Directory analogue? If so, then you may be able to set the policy through this.
222 </p><p>If you cannot set group policies in Samba, then you may be able to set the policy locally on
223 each machine. If you want to try this, then do the following (N.B. I do not know for sure that this
224 will work in the same way as a domain group policy):
225 </p><div class="procedure"><ol type="1"><li><p>On the XP workstation, log in with an Administrative account.</p></li><li><p>Click on <span class="guimenu">Start</span> -> <span class="guimenuitem">Run</span>.</p></li><li><p>Type <b class="command">mmc</b>.</p></li><li><p>Click on <span class="guibutton">OK</span>.</p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click on <span class="guimenu">File</span> -> <span class="guimenuitem">Add/Remove Snap-in</span> -> <span class="guimenuitem">Add</span>.</p></li><li><p>Double-click on <span class="guiicon">Group Policy</span>.</p></li><li><p>Click on <span class="guibutton">Finish</span> -> <span class="guibutton">Close</span>.</p></li><li><p>Click on <span class="guibutton">OK</span>.</p></li><li><p>In the “<span class="quote">Console Root</span>” window expand <span class="guiicon">Local Computer Policy</span> ->
226 <span class="guiicon">Computer Configuration</span> -> <span class="guiicon">Administrative Templates</span> -> <span class="guiicon">System</span> -> <span class="guiicon">User Profiles</span>.</p></li><li><p>Double-click on <span class="guilabel">Do not check for user ownership of Roaming Profile Folders</span>.</p></li><li><p>Select <span class="guilabel">Enabled</span>.</p></li><li><p>Click on <span class="guibutton">OK</span>.</p></li><li><p>Close the whole console. You do not need to save the settings (this refers to the
227 console settings rather than the policies you have changed).</p></li><li><p>Reboot.</p></li></ol></div></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956404"></a>Sharing Profiles between W9x/Me and NT4/200x/XP Workstations</h3></div></div><div></div></div><p> Sharing of desktop profiles between Windows versions is not recommended. Desktop profiles are an
228 evolving phenomenon and profiles for later versions of MS Windows clients add features that may interfere
229 with earlier versions of MS Windows clients. Probably the more salient reason to not mix profiles is
230 that when logging off an earlier version of MS Windows, the older format of profile contents may overwrite
231 information that belongs to the newer version resulting in loss of profile information content when that
232 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
233 location for the profiles. The <tt class="filename">smb.conf</tt> parameters that need to be common are <a class="indexterm" name="id2956443"></a><i class="parameter"><tt>logon path</tt></i> and <a class="indexterm" name="id2956457"></a><i class="parameter"><tt>logon home</tt></i>. </p><p> If you have this set up correctly, you will find separate <tt class="filename">user.DAT</tt> and
234 <tt class="filename">NTuser.DAT</tt> files in the same profile directory. </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956492"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><div></div></div><p> There is nothing to stop you from specifying any path that you like for the location of users' profiles.
235 Therefore, you could specify that the profile be stored on a Samba server, or any other SMB server,
236 as long as that SMB server supports encrypted passwords. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2956509"></a>Windows NT4 Profile Management Tools</h4></div></div><div></div></div><p> Unfortunately, the Resource Kit information is specific to the version of MS Windows NT4/200x. The
237 correct resource kit is required for each platform. </p><p>Here is a quick guide:</p><div class="procedure"><ol type="1"><li><p> On your NT4 Domain Controller, right click on <span class="guiicon">My Computer</span>, then select the
238 tab labeled <span class="guilabel">User Profiles</span>. </p></li><li><p> Select a user profile you want to migrate and click on it. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term “<span class="quote">migrate</span>” loosely. You can copy a profile to create a group
239 profile. You can give the user <i class="parameter"><tt>Everyone</tt></i> rights to the profile you copy this to. That
240 is what you need to do, since your Samba domain is not a member of a trust relationship with your NT4
241 PDC.</p></div></li><li><p>Click on the <span class="guibutton">Copy To</span> button.</p></li><li><p>In the box labeled <span class="guilabel">Copy Profile to</span> add your new path, e.g.,
242 <tt class="filename">c:\temp\foobar</tt></p></li><li><p>Click on <span class="guibutton">Change</span> in the <span class="guilabel">Permitted to use</span> box.</p></li><li><p>Click on the group “<span class="quote">Everyone</span>”, click on <span class="guibutton">OK</span>. This
243 closes the “<span class="quote">choose user</span>” box.</p></li><li><p>Now click on <span class="guibutton">OK</span>.</p></li></ol></div><p> Follow the above for every profile you need to migrate. </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2956689"></a>Side Bar Notes</h4></div></div><div></div></div><p>
245 You should obtain the SID of your NT4 domain. You can use smbpasswd to do this. Read the man
246 page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2956712"></a>moveuser.exe</h4></div></div><div></div></div><p> The Windows 200x professional resource kit has <b class="command">moveuser.exe</b>. <b class="command">moveuser.exe</b> changes the security of a profile
247 from one user to another. This allows the account domain to change, and/or the user name to change.</p><p>
249 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2956753"></a>Get SID</h4></div></div><div></div></div><p>
251 You can identify the SID by using <b class="command">GetSID.exe</b> 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:
252 <tt class="filename">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</tt> </p><p> Under the ProfileList key, there will be subkeys named with the SIDs of the users who have logged
253 on to this computer. (To find the profile information for the user whose locally cached profile you want
254 to move, find the SID for the user with the <b class="command">GetSID.exe</b> utility.) Inside the appropriate user's subkey,
255 you will see a string value named <i class="parameter"><tt>ProfileImagePath</tt></i>. </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2956822"></a>Mandatory Profiles</h2></div></div><div></div></div><p>
257 A Mandatory Profile is a profile that the user does not have the ability to overwrite. During the
258 user's session, it may be possible to change the desktop environment, however, as the user logs out all changes
259 made will be lost. If it is desired to not allow the user any ability to change the desktop environment,
260 then this must be done through policy settings. See the previous chapter. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
261 Under NO circumstances should the profile directory (or its contents) be made read-only
262 as this may render the profile un-usable. Where it is essential to make a profile read-only
263 within the UNIX file system, this can be done but then you absolutely must use the <b class="command">fake-permissions</b>
264 VFS module to instruct MS Windows NT/200x/XP clients that the Profile has write permission for the user. See <link linkend="fakeperms">.
265 </p></div><p> For MS Windows NT4/200x/XP, the above method can also be used to create mandatory profiles. To
266 convert a group profile into a mandatory profile, simply locate the <tt class="filename">NTUser.DAT</tt> file in the copied profile
267 and rename it to <tt class="filename">NTUser.MAN</tt>. </p><p> For MS Windows 9x/ME, it is the <tt class="filename">User.DAT</tt> file that must be renamed to
268 <tt class="filename">User.MAN</tt> to effect a mandatory profile. </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2956917"></a>Creating and Managing Group Profiles</h2></div></div><div></div></div><p>
270 Most organizations are arranged into departments. There is a nice benefit in this fact since usually
271 most users in a department require the same desktop applications and the same desktop layout. MS
272 Windows NT4/200x/XP will allow the use of Group Profiles. A Group Profile is a profile that is created
273 first using a template (example) user. Then using the profile migration tool (see above), the profile is
274 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. Instead of assigning a group profile to users (Using User Manager)
275 on a “<span class="quote">per user</span>” basis, the group itself is assigned the now modified profile. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Be careful with Group Profiles. If the user who is a member of a group also has a personal
276 profile, then the result will be a fusion (merge) of the two. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2956970"></a>Default Profile for Windows Users</h2></div></div><div></div></div><p>
279 does not already exist. Armed with a knowledge of where the default profile is located on the Windows
280 workstation, and knowing which registry keys effect the path from which the default profile is created,
281 it is possible to modify the default profile to one that has been optimized for the site. This has
282 significant administrative advantages. </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2956999"></a>MS Windows 9x/Me</h3></div></div><div></div></div><p> To enable default per use profiles in Windows 9x/ME, you can either use the <span class="application">Windows
283 98 System Policy Editor</span> or change the registry directly. </p><p> To enable default per user profiles in Windows 9x/ME, launch the <span class="application">System Policy
284 Editor</span>, then select <span class="guimenu">File</span> -> <span class="guimenuitem">Open Registry</span>,
285 next click on the <span class="guiicon">Local Computer</span> icon, click on <span class="guilabel">Windows 98 System</span>,
286 select <span class="guilabel">User Profiles</span>, and click on the enable box. Remember to save the registry
287 changes. </p><p> To modify the registry directly, launch the <span class="application">Registry Editor</span>
288 (<b class="command">regedit.exe</b>) and select the hive <tt class="filename">HKEY_LOCAL_MACHINE\Network\Logon</tt>. Now
290 enable user profiles to set the value
291 to 1; to disable user profiles set it to 0. </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2957101"></a>User Profile Handling with Windows 9x/Me</h4></div></div><div></div></div><p> When a user logs on to a Windows 9x/Me machine, the local profile path,
292 <tt class="filename">HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</tt>, is checked
293 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
294 version of the user profile. Windows 9x/Me also checks the user's home directory (or other specified
295 directory if the location has been modified) on the server for the User Profile. If a profile exists
296 in both locations, the newer of the two is used. If the User Profile exists on the server, but does not
297 exist on the local machine, the profile on the server is downloaded and used. If the User Profile only
298 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
299 9x/Me machine is used and copied to a newly created folder for the logged on user. At log off, any
300 changes that the user made are written to the user's local profile. If the user has a roaming profile,
301 the changes are written to the user's profile on the server. </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957150"></a>MS Windows NT4 Workstation</h3></div></div><div></div></div><p> On MS Windows NT4, the default user profile is obtained from the location
302 <tt class="filename">%SystemRoot%\Profiles</tt> which in a default installation will translate to
303 <tt class="filename">C:\Windows NT\Profiles</tt>. Under this directory on a clean install there will be three
306 User</tt>. </p><p> The <tt class="filename">All Users</tt> directory contains menu settings that are common across all
307 system users. The <tt class="filename">Default User</tt> directory contains menu entries that are customizable
308 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><div class="itemizedlist"><ul type="disc"><li><p>All Users settings.</p></li><li><p>Default User settings (contains the default <tt class="filename">NTUser.DAT</tt> file).</p></li></ul></div><p> When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain,
309 the following steps are followed in respect of profile handling:
312 </p><div class="procedure"><ol type="1"><li><p> The users' account information that is obtained during the logon process
313 contains the location of the users' desktop profile. The profile path may be local to
314 the machine or it may be located on a network share. If there exists a profile at the
315 location of the path from the user account, then this profile is copied to the location
316 <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>. This profile then inherits the settings
317 in the <tt class="filename">All Users</tt> profile in the <tt class="filename">%SystemRoot%\Profiles</tt>
318 location. </p></li><li><p> If the user account has a profile path, but at its location a profile does not
319 exist, then a new profile is created in the <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>
320 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
322 <tt class="filename">NTUser.DAT</tt> which is applied to the <tt class="filename">HKEY_CURRENT_USER</tt>
323 part of the registry.
324 </p></li><li><p> When the user logs out, if the profile is set to be a roaming profile it will be
325 written out to the location of the profile. The <tt class="filename">NTuser.DAT</tt> file is then
327 should there not exist in the NETLOGON share an <tt class="filename">NTConfig.POL</tt> at the next
328 logon, the effect of the previous <tt class="filename">NTConfig.POL</tt> will still be held in the
329 profile. The effect of this is known as tattooing.
330 </p></li></ol></div><p> MS Windows NT4 profiles may be <span class="emphasis"><em>local</em></span> or <span class="emphasis"><em>roaming</em></span>. A local
331 profile will stored in the <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt> location. A roaming
332 profile will also remain stored in the same way, unless the following registry key is created as shown: </p><pre class="screen"> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
334 </pre><p>
335 In this case, the local copy (in <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>) will be deleted
336 on logout.</p><p> Under MS Windows NT4, default locations for common resources like <tt class="filename">My Documents</tt>
337 may be redirected to a network share by modifying the following registry keys. These changes may be
338 affected via use of the System Policy Editor. To do so may require that you create your own template
339 extension for the policy editor to allow this to be done through the GUI. Another way to do this is by
340 way of first creating a default user profile, then while logged in as that user, run <b class="command">regedt32</b> to edit
341 the key settings. </p><p>
342 The Registry Hive key that affects the behavior of folders that are part of the default user
343 profile are controlled by entries on Windows NT4 is:
345 HKEY_CURRENT_USER
346 \Software
347 \Microsoft
348 \Windows
349 \CurrentVersion
350 \Explorer
351 \User Shell Folders
352 </pre><p>
354 </p><p> The above hive key contains a list of automatically managed folders. The default entries are shown in <link linkend="ProfileLocs">. </p><div class="table"><a name="ProfileLocs"></a><p class="title"><b>Table 24.1. User Shell Folder Registry Keys Default Values</b></p><table summary="User Shell Folder Registry Keys Default Values" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="left">Default Value</th></tr></thead><tbody><tr><td align="left">AppData</td><td align="left">%USERPROFILE%\Application Data</td></tr><tr><td align="left">Desktop</td><td align="left">%USERPROFILE%\Desktop</td></tr><tr><td align="left">Favorites</td><td align="left">%USERPROFILE%\Favorites</td></tr><tr><td align="left">NetHood</td><td align="left">%USERPROFILE%\NetHood</td></tr><tr><td align="left">PrintHood</td><td align="left">%USERPROFILE%\PrintHood</td></tr><tr><td align="left">Programs</td><td align="left">%USERPROFILE%\Start Menu\Programs</td></tr><tr><td align="left">Recent</td><td align="left">%USERPROFILE%\Recent</td></tr><tr><td align="left">SendTo</td><td align="left">%USERPROFILE%\SendTo</td></tr><tr><td align="left">Start Menu </td><td align="left">%USERPROFILE%\Start Menu</td></tr><tr><td align="left">Startup</td><td align="left">%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div><p> The registry key that contains the location of the default profile settings is: </p><p> <tt class="filename">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\
355 User Shell Folders</tt> </p><p> The default entries are shown in <link linkend="regkeys">.</p><div class="table"><a name="regkeys"></a><p class="title"><b>Table 24.2. Defaults of Profile Settings Registry Keys</b></p><table summary="Defaults of Profile Settings Registry Keys" border="1"><colgroup><col align="left"><col align="left"></colgroup><tbody><tr><td align="left">Common Desktop</td><td align="left">%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td align="left">Common Programs</td><td align="left">%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td align="left">Common Start Menu</td><td align="left">%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td align="left">Common Startup</td><td align="left">%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2957772"></a>MS Windows 200x/XP</h3></div></div><div></div></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
357 MS Windows XP Home Edition does use default per user profiles, but cannot participate
358 in domain security, cannot log onto an NT/ADS-style domain, and thus can obtain the profile only
359 from itself. While there are benefits in doing this, the beauty of those MS Windows clients that
360 can participate in domain logon processes allows the administrator to create a global default
361 profile and enforce it through the use of Group Policy Objects (GPOs).
362 </p></div><p> When a new user first logs onto an MS Windows 200x/XP machine, the default profile is obtained from
363 <tt class="filename">C:\Documents and Settings\Default User</tt>. The administrator can modify or change the
364 contents of this location and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement
365 since it will involve copying a new default profile to every MS Windows 200x/XP client workstation. </p><p> When MS Windows 200x/XP participates in a domain security context, and if the default user profile is
366 not found, then the client will search for a default profile in the NETLOGON share of the authenticating
367 server. In MS Windows parlance,<tt class="filename">%LOGONSERVER%\NETLOGON\Default User,</tt> and if one
368 exists there it will copy this to the workstation to the <tt class="filename">C:\Documents and Settings\</tt>
369 under the Windows login name of the user. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> This path translates, in Samba parlance, to the <tt class="filename">smb.conf</tt>
371 of this share and must be called <tt class="filename">Default Profile</tt>. </p></div><p> If a default profile does not exist in this location, then MS Windows 200x/XP will use the local
372 default profile. </p><p> On logging out, the users' desktop profile will be stored to the location specified in the registry
373 settings that pertain to the user. If no specific policies have been created or passed to the client
374 during the login process (as Samba does automatically), then the user's profile will be written to the
375 local machine only under the path <tt class="filename">C:\Documents and Settings\%USERNAME%</tt>. </p><p> Those wishing to modify the default behavior can do so through these three methods: </p><div class="itemizedlist"><ul type="disc"><li><p> Modify the registry keys on the local machine manually and place the new
376 default profile in the NETLOGON share root. This is not recommended as it is maintenance intensive.
377 </p></li><li><p> Create an NT4-style NTConfig.POL file that specified this behavior and locate
378 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
379 default profile in the NETLOGON share. </p></li></ul></div><p>The registry hive key that effects the behavior of folders that are part of the default user
380 profile are controlled by entries on Windows 200x/XP is: </p><p> <tt class="filename">HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell
381 Folders\</tt> </p><p>
382 The above hive key contains a list of automatically managed folders. The default entries are shown
385 </p><div class="table"><a name="defregpthkeys"></a><p class="title"><b>Table 24.3. Defaults of Default User Profile Paths Registry Keys</b></p><table summary="Defaults of Default User Profile Paths Registry Keys" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th align="left">Name</th><th align="left">Default Value</th></tr></thead><tbody><tr><td align="left">AppData</td><td align="left">%USERPROFILE%\Application Data</td></tr><tr><td align="left">Cache</td><td align="left">%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td align="left">Cookies</td><td align="left">%USERPROFILE%\Cookies</td></tr><tr><td align="left">Desktop</td><td align="left">%USERPROFILE%\Desktop</td></tr><tr><td align="left">Favorites</td><td align="left">%USERPROFILE%\Favorites</td></tr><tr><td align="left">History</td><td align="left">%USERPROFILE%\Local Settings\History</td></tr><tr><td align="left">Local AppData</td><td align="left">%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td align="left">Local Settings</td><td align="left">%USERPROFILE%\Local Settings</td></tr><tr><td align="left">My Pictures</td><td align="left">%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td align="left">NetHood</td><td align="left">%USERPROFILE%\NetHood</td></tr><tr><td align="left">Personal</td><td align="left">%USERPROFILE%\My Documents</td></tr><tr><td align="left">PrintHood</td><td align="left">%USERPROFILE%\PrintHood</td></tr><tr><td align="left">Programs</td><td align="left">%USERPROFILE%\Start Menu\Programs</td></tr><tr><td align="left">Recent</td><td align="left">%USERPROFILE%\Recent</td></tr><tr><td align="left">SendTo</td><td align="left">%USERPROFILE%\SendTo</td></tr><tr><td align="left">Start Menu</td><td align="left">%USERPROFILE%\Start Menu</td></tr><tr><td align="left">Startup</td><td align="left">%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td align="left">Templates</td><td align="left">%USERPROFILE%\Templates</td></tr></tbody></table></div><p> There is also an entry called “<span class="quote">Default</span>” that has no value set. The default entry is
386 of type <tt class="constant">REG_SZ</tt>, all the others are of type <tt class="constant">REG_EXPAND_SZ</tt>. </p><p> It makes a huge difference to the speed of handling roaming user profiles if all the folders are
387 stored on a dedicated location on a network server. This means that it will not be necessary to write
388 the 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: </p><p><tt class="filename">%LOGONSERVER%\%USERNAME%\Default Folders</tt></p><p> This would store the folders in the user's home directory under a directory called <tt class="filename">Default
389 Folders</tt>. You could also use: </p><p><tt class="filename">\\<i class="replaceable"><tt>SambaServer</tt></i>\<i class="replaceable"><tt>FolderShare</tt></i>\%USERNAME%</tt></p><p>
390 in which case the default folders will be stored in the server named <i class="replaceable"><tt>SambaServer</tt></i>
391 in the share called <i class="replaceable"><tt>FolderShare</tt></i> under a directory that has the name of the
392 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
393 (default or custom) to it. </p><p> MS Windows 200x/XP profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>.
394 A roaming profile will be cached locally unless the following registry key is created:
397 </p><p> </p><pre class="programlisting"> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
399 In this case, the local cache copy will be deleted on logout.
400 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2958338"></a>Common Errors</h2></div></div><div></div></div><p>
401 The following are some typical errors, problems and questions that have been asked on the Samba mailing lists.
402 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958351"></a>Configuring Roaming Profiles for a Few Users or Groups</h3></div></div><div></div></div><p>
403 With Samba-2.2.x, the choice you have is to enable or disable roaming profiles support. It is a
404 global only setting. The default is to have roaming profiles and the default path will locate them in
405 the user's home directory.
406 </p><p>
407 If disabled globally, then no one will have roaming profile ability. If enabled and you want it
408 to apply only to certain machines, then on those machines on which roaming profile support is not wanted
409 it is then necessary to disable roaming profile handling in the registry of each such machine.
410 </p><p>
411 With Samba-3, you can have a global profile setting in <tt class="filename">smb.conf</tt> and you can override this by
412 per-user settings using the Domain User Manager (as with MS Windows NT4/ Win 200xx). </p><p> In any case, you can configure only one profile per user. That profile can be either: </p><div class="itemizedlist"><ul type="disc"><li>A profile unique to that user.</li><li>A mandatory profile (one the user cannot change).</li><li>A group profile (really should be mandatory, that is unchangable).</li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958416"></a>Cannot Use Roaming Profiles</h3></div></div><div></div></div><p> A user requested the following: “<span class="quote"> I do not want Roaming profiles to be implemented. I want
413 to give users a local profile alone. Please help me, I am totally lost with this error. For the past
414 two days I tried everything, I googled around but found no useful pointers. Please help me. </span>”</p><p> The choices are: </p><div class="variablelist"><dl><dt><span class="term">Local profiles</span></dt><dd><p> I know of no registry keys that will allow
415 auto-deletion of LOCAL profiles on log out.</p></dd><dt><span class="term">Roaming profiles</span></dt><dd><p> As a user logs onto the network, a centrally
416 stored profile is copied to the workstation to form a local profile. This local profile
417 will persist (remain on the workstation disk) unless a registry key is changed that will
418 cause this profile to be automatically deleted on logout. </p></dd></dl></div><p>The roaming profile choices are: </p><div class="variablelist"><dl><dt><span class="term">Personal roaming profiles</span></dt><dd><p> These are typically stored in
419 a profile share on a central (or conveniently located local) server. </p><p> Workstations cache (store) a local copy of the profile. This cached
420 copy is used when the profile cannot be downloaded at next logon. </p></dd><dt><span class="term">Group profiles</span></dt><dd><p>These are loaded from a central profile
421 server.</p></dd><dt><span class="term">Mandatory profiles</span></dt><dd><p> Mandatory profiles can be created for
422 a user as well as for any group that a user is a member of. Mandatory profiles cannot be
423 changed by ordinary users. Only the administrator can change or reconfigure a mandatory
424 profile. </p></dd></dl></div><p> A Windows NT4/200x/XP profile can vary in size from 130KB to very large. Outlook PST files are
425 most often part of the profile and can be many GB in size. On average (in a well controlled environment),
426 roaming profile size of 2MB is a good rule of thumb to use for planning purposes. In an undisciplined
427 environment, I have seen up to 2GB profiles. Users tend to complain when it takes an hour to log onto a
428 workstation but they harvest the fruits of folly (and ignorance). </p><p> The point of all the above is to show that roaming profiles and good controls of how they can be
429 changed as well as good discipline make up for a problem-free site. </p><p> Microsoft's answer to the PST problem is to store all email in an MS Exchange Server backend. This
430 removes the need for a PST file. </p><p>Local profiles mean: </p><div class="itemizedlist"><ul type="disc"><li><p>If each machine is used by many users, then much local disk storage is needed
431 for local profiles.</p></li><li><p>Every workstation the user logs into has
432 its own profile; these can be very different from machine to machine.</p></li></ul></div><p> On the other hand, use of roaming profiles means: </p><div class="itemizedlist"><ul type="disc"><li><p>The network administrator can control the desktop environment of all users.</p></li><li><p>Use of mandatory profiles drastically reduces network management overheads.</p></li><li><p>In the long run, users will experience fewer problems.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2958626"></a>Changing the Default Profile</h3></div></div><div></div></div><p>“<span class="quote">When the client logs onto the Domain Controller, it searches
435 First, the Samba server needs to be configured as a Domain Controller. This can be done by
436 setting in <tt class="filename">smb.conf</tt>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>security = user</tt></i></td></tr><tr><td><i class="parameter"><tt>os level = 32 (or more)</tt></i></td></tr><tr><td><i class="parameter"><tt>domain logons = Yes</tt></i></td></tr></table><p> There must be a <i class="parameter"><tt>[netlogon]</tt></i> share that is world readable. It is
437 a good idea to add a logon script to pre-set printer and drive connections. There is also a facility
438 for automatically synchronizing the workstation time clock with that of the logon server (another good
439 thing to do). </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> To invoke auto-deletion of roaming profile from the local workstation cache (disk storage), use
440 the <span class="application">Group Policy Editor</span> to create a file called <tt class="filename">NTConfig.POL</tt>
441 with the appropriate entries. This file needs to be located in the <i class="parameter"><tt>netlogon</tt></i>
442 share root directory.</p></div><p> Windows clients need to be members of the domain. Workgroup machines do not use network logons
443 so they do not interoperate with domain profiles. </p><p> For roaming profiles, add to <tt class="filename">smb.conf</tt>: </p><table class="simplelist" border="0" summary="Simple list"><tr><td><i class="parameter"><tt>logon path = \\%N\profiles\%U</tt></i></td></tr><tr><td># Default logon drive is Z:</td></tr><tr><td><i class="parameter"><tt>logon drive = H:</tt></i></td></tr><tr><td># This requires a PROFILES share that is world writable.</td></tr></table></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="PolicyMgmt.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="pam.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 23. System and Account Policies </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 25. PAM-Based Distributed Authentication</td></tr></table></div></body></html>