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#id2988251">Features and Benefits</a></dt><dt><a href="ProfileMgmt.html#id2988285">Roaming Profiles</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2988326">Samba Configuration for Profile Handling</a></dt><dt><a href="ProfileMgmt.html#id2988731">Windows Client Profile Configuration Information</a></dt><dt><a href="ProfileMgmt.html#id2989902">Sharing Profiles between W9x/Me and NT4/200x/XP workstations</a></dt><dt><a href="ProfileMgmt.html#id2989967">Profile Migration from Windows NT4/200x Server to Samba</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2990232">Mandatory profiles</a></dt><dt><a href="ProfileMgmt.html#id2990290">Creating/Managing Group Profiles</a></dt><dt><a href="ProfileMgmt.html#id2990336">Default Profile for Windows Users</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2990356">MS Windows 9x/Me</a></dt><dt><a href="ProfileMgmt.html#id2990504">MS Windows NT4 Workstation</a></dt><dt><a href="ProfileMgmt.html#id2991058">MS Windows 200x/XP</a></dt></dl></dd><dt><a href="ProfileMgmt.html#id2991562">Common Errors</a></dt><dd><dl><dt><a href="ProfileMgmt.html#id2991575">How does one set up roaming profiles for just one (or a few) user/s or group/s?</a></dt><dt><a href="ProfileMgmt.html#id2991638">Can NOT use Roaming Profiles</a></dt><dt><a href="ProfileMgmt.html#id2991859">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="id2988251"></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
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.
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 to deal with those
14 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2988285"></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>
15 Roaming profiles support is different for Win9x / Me and Windows NT4/200x.
17 Before discussing how to configure roaming profiles, it is useful to see how
18 Windows 9x / Me and Windows NT4/200x clients implement these features.
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 Win9X/Me
23 profiles are restricted to being stored in the user's home directory.
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="id2988326"></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="id2988340"></a>NT4/200x User Profiles</h4></div></div><div></div></div><p>
30 To support Windows NT4/200x clients, in the [global] section of smb.conf set the
31 following (for example):
33 </p><pre class="programlisting">
34 logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
37 This is typically implemented like:
39 </p><pre class="programlisting">
40 logon path = \\%L\Profiles\%u
42 where %L translates to the name of the Samba server and %u translates to the user name
44 The default for this option is <tt class="filename">\\%N\%U\profile</tt>,
45 namely <tt class="filename">\\sambaserver\username\profile</tt>.
46 The <tt class="filename">\\N%\%U</tt> service is created automatically by the [homes] service. If you are using
47 a samba server for the profiles, you _must_ make the share specified in the logon path
48 browseable. Please refer to the man page for <tt class="filename">smb.conf</tt> in respect of the different
49 semantics of %L and %N, as well as %U and %u.
50 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
51 MS Windows NT/2K clients at times do not disconnect a connection to a server
52 between logons. It is recommended to NOT use the <i class="parameter"><tt>homes</tt></i>
53 meta-service name as part of the profile share path.
54 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2988432"></a>Windows 9x / Me User Profiles</h4></div></div><div></div></div><p>
55 To support Windows 9x / Me clients, you must use the <i class="parameter"><tt>logon home</tt></i> parameter. Samba has
56 now been fixed so that <b class="userinput"><tt>net use /home</tt></b> now works as well, and it, too, relies
57 on the <b class="command">logon home</b> parameter.
59 By using the logon home parameter, you are restricted to putting Win9x / Me
60 profiles in the user's home directory. But wait! There is a trick you
61 can use. If you set the following in the <i class="parameter"><tt>[global]</tt></i> section of your <tt class="filename">smb.conf</tt> file:
62 </p><pre class="programlisting">
63 logon home = \\%L\%U\.profiles
65 then your Windows 9x / Me clients will dutifully put their clients in a subdirectory
66 of your home directory called <tt class="filename">.profiles</tt> (thus making them hidden).
68 Not only that, but <b class="userinput"><tt>net use /home</tt></b> will also work, because of a feature in
69 Windows 9x / Me. It removes any directory stuff off the end of the home directory area
70 and only uses the server and share portion. That is, it looks like you
71 specified <tt class="filename">\\%L\%U</tt> for <i class="parameter"><tt>logon home</tt></i>.
72 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2988541"></a>Mixed Windows 9x / Me and Windows NT4/200x User Profiles</h4></div></div><div></div></div><p>
73 You can support profiles for both Win9X and WinNT clients by setting both the
74 <i class="parameter"><tt>logon home</tt></i> and <i class="parameter"><tt>logon path</tt></i> parameters. For example:
75 </p><pre class="programlisting">
76 logon home = \\%L\%u\.profiles
77 logon path = \\%L\profiles\%u
78 </pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2988580"></a>Disabling Roaming Profile Support</h4></div></div><div></div></div><p>
79 A question often asked is “<span class="quote">How may I enforce use of local profiles?</span>” or
80 “<span class="quote">How do I disable Roaming Profiles?</span>”
82 There are three ways of doing this:
83 </p><div class="variablelist"><dl><dt><span class="term">In <tt class="filename">smb.conf</tt></span></dt><dd><p>
84 Affect the following settings and ALL clients
85 will be forced to use a local profile:
86 </p><pre class="programlisting">
90 </p></dd><dt><span class="term">MS Windows Registry:</span></dt><dd><p>
91 By using the Microsoft Management Console gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This of course modifies registry settings. The full path to the option is:
93 </p><pre class="programlisting">
94 Local Computer Policy\
95 Computer Configuration\
96 Administrative Templates\
100 Disable: Only Allow Local User Profiles
101 Disable: Prevent Roaming Profile Change from Propagating to the Server
103 </p></dd><dt><span class="term">Change of Profile Type:</span></dt><dd><p>
104 From the start menu right click on the
105 My Computer icon, select <span class="guimenuitem">Properties</span>, click on the <span class="guilabel">User Profiles</span>
106 tab, select the profile you wish to change from Roaming type to Local, click <span class="guibutton">Change Type</span>.
107 </p></dd></dl></div><p>
108 Consult the MS Windows registry guide for your particular MS Windows version for more
109 information about which registry keys to change to enforce use of only local user
111 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
112 The specifics of how to convert a local profile to a roaming profile, or a roaming profile
113 to a local one vary according to the version of MS Windows you are running. Consult the
114 Microsoft MS Windows Resource Kit for your version of Windows for specific information.
115 </p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2988731"></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="id2988739"></a>Windows 9x / Me Profile Setup</h4></div></div><div></div></div><p>
116 When a user first logs in on Windows 9X, the file user.DAT is created,
117 as are folders <tt class="filename">Start Menu</tt>, <tt class="filename">Desktop</tt>,
118 <tt class="filename">Programs</tt> and <tt class="filename">Nethood</tt>.
119 These directories and their contents will be merged with the local
120 versions stored in <tt class="filename">c:\windows\profiles\username</tt> on subsequent logins,
121 taking the most recent from each. You will need to use the <i class="parameter"><tt>[global]</tt></i>
122 options <i class="parameter"><tt>preserve case = yes</tt></i>, <i class="parameter"><tt>short preserve case = yes</tt></i> and
123 <i class="parameter"><tt>case sensitive = no</tt></i> in order to maintain capital letters in shortcuts
124 in any of the profile folders.
126 The user.DAT file contains all the user's preferences. If you wish to
127 enforce a set of preferences, rename their user.DAT file to user.MAN,
128 and deny them write access to this file.
129 </p><div class="orderedlist"><ol type="1"><li><p>
130 On the Windows 9x / Me machine, go to <span class="guimenu">Control Panel</span> -> <span class="guimenuitem">Passwords</span> and
131 select the <span class="guilabel">User Profiles</span> tab. Select the required level of
132 roaming preferences. Press <span class="guibutton">OK</span>, but do _not_ allow the computer
135 On the Windows 9x / Me machine, go to <span class="guimenu">Control Panel</span> -> <span class="guimenuitem">Network</span> ->
136 <span class="guimenuitem">Client for Microsoft Networks</span> -> <span class="guilabel">Preferences</span>. Select <span class="guilabel">Log on to
137 NT Domain</span>. Then, ensure that the Primary Logon is <span class="guilabel">Client for
138 Microsoft Networks</span>. Press <span class="guibutton">OK</span>, and this time allow the computer
140 </p></li></ol></div><p>
141 Under Windows 9x / Me Profiles are downloaded from the Primary Logon.
142 If you have the Primary Logon as 'Client for Novell Networks', then
143 the profiles and logon script will be downloaded from your Novell
144 Server. If you have the Primary Logon as 'Windows Logon', then the
145 profiles will be loaded from the local machine - a bit against the
146 concept of roaming profiles, it would seem!
148 You will now find that the Microsoft Networks Login box contains
149 [user, password, domain] instead of just [user, password]. Type in
150 the samba server's domain name (or any other domain known to exist,
151 but bear in mind that the user will be authenticated against this
152 domain and profiles downloaded from it, if that domain logon server
153 supports it), user name and user's password.
155 Once the user has been successfully validated, the Windows 9x / Me machine
156 will inform you that <tt class="computeroutput">The user has not logged on before' and asks you
157 if you wish to save the user's preferences?</tt> Select <span class="guibutton">yes</span>.
159 Once the Windows 9x / Me client comes up with the desktop, you should be able
160 to examine the contents of the directory specified in the <i class="parameter"><tt>logon path</tt></i>
161 on the samba server and verify that the <tt class="filename">Desktop</tt>, <tt class="filename">Start Menu</tt>,
162 <tt class="filename">Programs</tt> and <tt class="filename">Nethood</tt> folders have been created.
164 These folders will be cached locally on the client, and updated when
165 the user logs off (if you haven't made them read-only by then).
166 You will find that if the user creates further folders or short-cuts,
167 that the client will merge the profile contents downloaded with the
168 contents of the profile directory already on the local client, taking
169 the newest folders and short-cuts from each set.
171 If you have made the folders / files read-only on the samba server,
172 then you will get errors from the Windows 9x / Me machine on logon and logout, as
173 it attempts to merge the local and the remote profile. Basically, if
174 you have any errors reported by the Windows 9x / Me machine, check the Unix file
175 permissions and ownership rights on the profile directory contents,
178 If you have problems creating user profiles, you can reset the user's
179 local desktop cache, as shown below. When this user then next logs in,
180 they will be told that they are logging in "for the first time".
181 </p><div class="orderedlist"><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
182 Before deleting the contents of the
183 directory listed in the ProfilePath (this is likely to be
184 <tt class="filename">c:\windows\profiles\username)</tt>, ask them if they
185 have any important files stored on their desktop or in their start menu.
186 Delete the contents of the directory ProfilePath (making a backup if any
187 of the files are needed).
189 This will have the effect of removing the local (read-only hidden
190 system file) user.DAT in their profile directory, as well as the
191 local "desktop", "nethood", "start menu" and "programs" folders.
192 </p></div><ol type="1"><li><p>
193 instead of logging in under the [user, password, domain] dialog,
194 press <span class="guibutton">escape</span>.
196 run the <b class="command">regedit.exe</b> program, and look in:
198 <tt class="filename">HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList</tt>
200 you will find an entry, for each user, of ProfilePath. Note the
201 contents of this key (likely to be <tt class="filename">c:\windows\profiles\username</tt>),
202 then delete the key ProfilePath for the required user.
203 </p><p>[Exit the registry editor].</p></li><li><p>
204 search for the user's .PWL password-caching file in the <tt class="filename">c:\windows</tt>
205 directory, and delete it.
207 log off the windows 9x / Me client.
209 check the contents of the profile path (see <i class="parameter"><tt>logon path</tt></i> described
210 above), and delete the <tt class="filename">user.DAT</tt> or <tt class="filename">user.MAN</tt> file for the user,
211 making a backup if required.
212 </p></li></ol></div><p>
213 If all else fails, increase samba's debug log levels to between 3 and 10,
214 and / or run a packet trace program such as ethereal or <b class="command">netmon.exe</b>, and
215 look for error messages.
217 If you have access to an Windows NT4/200x server, then first set up roaming profiles
218 and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine
219 the example packet traces provided with Windows NT4/200x server, and see what the
220 differences are with the equivalent samba trace.
221 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2989233"></a>Windows NT4 Workstation</h4></div></div><div></div></div><p>
222 When a user first logs in to a Windows NT Workstation, the profile
223 NTuser.DAT is created. The profile location can be now specified
224 through the <i class="parameter"><tt>logon path</tt></i> parameter.
226 There is a parameter that is now available for use with NT Profiles:
227 <i class="parameter"><tt>logon drive</tt></i>. This should be set to <tt class="filename">H:</tt> or any other drive, and
228 should be used in conjunction with the new "logon home" parameter.
230 The entry for the NT4 profile is a _directory_ not a file. The NT
231 help on profiles mentions that a directory is also created with a .PDS
232 extension. The user, while logging in, must have write permission to
233 create the full profile path (and the folder with the .PDS extension
234 for those situations where it might be created.)
236 In the profile directory, Windows NT4 creates more folders than Windows 9x / Me.
237 It creates <tt class="filename">Application Data</tt> and others, as well as <tt class="filename">Desktop</tt>, <tt class="filename">Nethood</tt>,
238 <tt class="filename">Start Menu</tt> and <tt class="filename">Programs</tt>. The profile itself is stored in a file
239 <tt class="filename">NTuser.DAT</tt>. Nothing appears to be stored in the .PDS directory, and
240 its purpose is currently unknown.
242 You can use the <span class="application">System Control Panel</span> to copy a local profile onto
243 a samba server (see NT Help on profiles: it is also capable of firing
244 up the correct location in the <span class="application">System Control Panel</span> for you). The
245 NT Help file also mentions that renaming <tt class="filename">NTuser.DAT</tt> to <tt class="filename">NTuser.MAN</tt>
246 turns a profile into a mandatory one.
248 The case of the profile is significant. The file must be called
249 <tt class="filename">NTuser.DAT</tt> or, for a mandatory profile, <tt class="filename">NTuser.MAN</tt>.
250 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2989391"></a>Windows 2000/XP Professional</h4></div></div><div></div></div><p>
251 You must first convert the profile from a local profile to a domain
252 profile on the MS Windows workstation as follows:
253 </p><div class="procedure"><ol type="1"><li><p>
254 Log on as the <span class="emphasis"><em>LOCAL</em></span> workstation administrator.
256 Right click on the <span class="guiicon">My Computer</span> Icon, select <span class="guimenuitem">Properties</span>
258 Click on the <span class="guilabel">User Profiles</span> tab
260 Select the profile you wish to convert (click on it once)
262 Click on the button <span class="guibutton">Copy To</span>
264 In the <span class="guilabel">Permitted to use</span> box, click on the <span class="guibutton">Change</span> button.
266 Click on the 'Look in" area that lists the machine name, when you click
267 here it will open up a selection box. Click on the domain to which the
268 profile must be accessible.
269 </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. Eg: In the connect
270 as: <i class="replaceable"><tt>MIDEARTH</tt></i>\root, password: <i class="replaceable"><tt>mypassword</tt></i>.</p></div></li><li><p>
271 To make the profile capable of being used by anyone select 'Everyone'
273 Click <span class="guibutton">OK</span>. The Selection box will close.
275 Now click on the <span class="guibutton">Ok</span> button to create the profile in the path you
277 </p></li></ol></div><p>
278 Done. You now have a profile that can be edited using the samba-3.0.0
279 <b class="command">profiles</b> tool.
280 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
281 Under NT/2K the use of mandatory profiles forces the use of MS Exchange
282 storage of mail data. That keeps desktop profiles usable.
283 </p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><div class="procedure"><ol type="1"><li><p>
284 This is a security check new to Windows XP (or maybe only
285 Windows XP service pack 1). It can be disabled via a group policy in
286 Active Directory. The policy is:</p><p><tt class="filename">Computer Configuration\Administrative Templates\System\User
287 Profiles\Do not check for user ownership of Roaming Profile Folders</tt></p><p>...and it should be set to <tt class="constant">Enabled</tt>.
288 Does the new version of samba have an Active Directory analogue? If so,
289 then you may be able to set the policy through this.
291 If you cannot set group policies in samba, then you may be able to set
292 the policy locally on each machine. If you want to try this, then do
293 the following (N.B. I don't know for sure that this will work in the
294 same way as a domain group policy):
296 On the XP workstation log in with an Administrator account.
297 </p></li><li><p>Click: <span class="guimenu">Start</span>, <span class="guimenuitem">Run</span></p></li><li><p>Type: <b class="userinput"><tt>mmc</tt></b></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>A Microsoft Management Console should appear.</p></li><li><p>Click: <span class="guimenu">File</span>, <span class="guimenuitem">Add/Remove Snap-in...</span>, <span class="guimenuitem">Add</span></p></li><li><p>Double-Click: <span class="guiicon">Group Policy</span></p></li><li><p>Click: <span class="guibutton">Finish</span>, <span class="guibutton">Close</span></p></li><li><p>Click: <span class="guibutton">OK</span></p></li><li><p>In the "Console Root" window:</p></li><li><p>Expand: <span class="guiicon">Local Computer Policy</span>, <span class="guiicon">Computer Configuration</span>,
298 <span class="guiicon">Administrative Templates</span>, <span class="guiicon">System</span>, <span class="guiicon">User Profiles</span></p></li><li><p>Double-Click: <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: <span class="guibutton">OK</span></p></li><li><p>Close the whole console. You do not need to save the settings (this
299 refers to the console settings rather than the policies you have
300 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="id2989902"></a>Sharing Profiles between W9x/Me and NT4/200x/XP workstations</h3></div></div><div></div></div><p>
301 Sharing of desktop profiles between Windows versions is NOT recommended.
302 Desktop profiles are an evolving phenomenon and profiles for later versions
303 of MS Windows clients add features that may interfere with earlier versions
304 of MS Windows clients. Probably the more salient reason to NOT mix profiles
305 is that when logging off an earlier version of MS Windows the older format
306 of profile contents may overwrite information that belongs to the newer
307 version resulting in loss of profile information content when that user logs
308 on again with the newer version of MS Windows.
310 If you then want to share the same Start Menu / Desktop with W9x/Me, you will
311 need to specify a common location for the profiles. The smb.conf parameters
312 that need to be common are <i class="parameter"><tt>logon path</tt></i> and
313 <i class="parameter"><tt>logon home</tt></i>.
315 If you have this set up correctly, you will find separate <tt class="filename">user.DAT</tt> and
316 <tt class="filename">NTuser.DAT</tt> files in the same profile directory.
317 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2989967"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div><div></div></div><p>
318 There is nothing to stop you specifying any path that you like for the
319 location of users' profiles. Therefore, you could specify that the
320 profile be stored on a samba server, or any other SMB server, as long as
321 that SMB server supports encrypted passwords.
322 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2989984"></a>Windows NT4 Profile Management Tools</h4></div></div><div></div></div><p>
323 Unfortunately, the Resource Kit information is specific to the version of MS Windows
324 NT4/200x. The correct resource kit is required for each platform.
326 Here is a quick guide:
327 </p><div class="procedure"><ol type="1"><li><p>
328 On your NT4 Domain Controller, right click on <span class="guiicon">My Computer</span>, then
329 select the tab labelled <span class="guilabel">User Profiles</span>.
331 Select a user profile you want to migrate and click on it.
332 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term "migrate" loosely. You can copy a profile to
333 create a group profile. You can give the user 'Everyone' rights to the
334 profile you copy this to. That is what you need to do, since your samba
335 domain is not a member of a trust relationship with your NT4 PDC.</p></div></li><li><p>Click the <span class="guibutton">Copy To</span> button.</p></li><li><p>In the box labelled <span class="guilabel">Copy Profile to</span> add your new path, eg:
336 <tt class="filename">c:\temp\foobar</tt></p></li><li><p>Click on the button <span class="guibutton">Change</span> in the <span class="guilabel">Permitted to use</span> box.</p></li><li><p>Click on the group 'Everyone' and then click <span class="guibutton">OK</span>. This closes the
337 'choose user' box.</p></li><li><p>Now click <span class="guibutton">OK</span>.</p></li></ol></div><p>
338 Follow the above for every profile you need to migrate.
339 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2990153"></a>Side bar Notes</h4></div></div><div></div></div><p>
340 You should obtain the SID of your NT4 domain. You can use smbpasswd to do
341 this. Read the man page.</p><p>
342 With Samba-3.0.0 alpha code you can import all you NT4 domain accounts
343 using the net samsync method. This way you can retain your profile
344 settings as well as all your users.
345 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2990175"></a>moveuser.exe</h4></div></div><div></div></div><p>
346 The W2K professional resource kit has moveuser.exe. moveuser.exe changes
347 the security of a profile from one user to another. This allows the account
348 domain to change, and/or the user name to change.
349 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2990191"></a>Get SID</h4></div></div><div></div></div><p>
350 You can identify the SID by using GetSID.exe from the Windows NT Server 4.0
353 Windows NT 4.0 stores the local profile information in the registry under
355 <tt class="filename">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</tt>
357 Under the ProfileList key, there will be subkeys named with the SIDs of the
358 users who have logged on to this computer. (To find the profile information
359 for the user whose locally cached profile you want to move, find the SID for
360 the user with the GetSID.exe utility.) Inside of the appropriate user's
361 subkey, you will see a string value named ProfileImagePath.
362 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990232"></a>Mandatory profiles</h2></div></div><div></div></div><p>
363 A Mandatory Profile is a profile that the user does NOT have the ability to overwrite.
364 During the user's session it may be possible to change the desktop environment, but
365 as the user logs out all changes made will be lost. If it is desired to NOT allow the
366 user any ability to change the desktop environment then this must be done through
367 policy settings. See previous chapter.
368 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
369 Under NO circumstances should the profile directory (or it's contents) be made read-only
370 as this may render the profile un-usable.
372 For MS Windows NT4/200x/XP the above method can be used to create mandatory profiles
373 also. To convert a group profile into a mandatory profile simply locate the NTUser.DAT
374 file in the copied profile and rename it to NTUser.MAN.
376 For MS Windows 9x / Me it is the <tt class="filename">User.DAT</tt> file that must be renamed to <tt class="filename">User.MAN</tt> to
377 affect a mandatory profile.
378 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990290"></a>Creating/Managing Group Profiles</h2></div></div><div></div></div><p>
379 Most organisations are arranged into departments. There is a nice benefit in
380 this fact since usually most users in a department will require the same desktop
381 applications and the same desktop layout. MS Windows NT4/200x/XP will allow the
382 use of Group Profiles. A Group Profile is a profile that is created firstly using
383 a template (example) user. Then using the profile migration tool (see above) the
384 profile is assigned access rights for the user group that needs to be given access
385 to the group profile.
387 The next step is rather important. <span class="emphasis"><em>Please note:</em></span> Instead of assigning a group profile
388 to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned
389 the now modified profile.
390 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
391 Be careful with group profiles, if the user who is a member of a group also
392 has a personal profile, then the result will be a fusion (merge) of the two.
393 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2990336"></a>Default Profile for Windows Users</h2></div></div><div></div></div><p>
394 MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom
395 a profile does not already exist. Armed with a knowledge of where the default profile
396 is located on the Windows workstation, and knowing which registry keys affect the path
397 from which the default profile is created, it is possible to modify the default profile
398 to one that has been optimised for the site. This has significant administrative
400 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2990356"></a>MS Windows 9x/Me</h3></div></div><div></div></div><p>
401 To enable default per use profiles in Windows 9x / Me you can either use the <span class="application">Windows 98 System
402 Policy Editor</span> or change the registry directly.
404 To enable default per user profiles in Windows 9x / Me, launch the <span class="application">System Policy Editor</span>, then
405 select <span class="guimenu">File</span> -> <span class="guimenuitem">Open Registry</span>, then click on the
406 <span class="guiicon">Local Computer</span> icon, click on <span class="guilabel">Windows 98 System</span>,
407 select <span class="guilabel">User Profiles</span>, click on the enable box. Do not forget to save the registry changes.
409 To modify the registry directly, launch the <span class="application">Registry Editor</span> (<b class="command">regedit.exe</b>), select the hive
410 <tt class="filename">HKEY_LOCAL_MACHINE\Network\Logon</tt>. Now add a DWORD type key with the name
411 "User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0.
412 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2990454"></a>How User Profiles Are Handled in Windows 9x / Me?</h4></div></div><div></div></div><p>
413 When a user logs on to a Windows 9x / Me machine, the local profile path,
414 <tt class="filename">HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</tt>, is checked
415 for an existing entry for that user:
417 If the user has an entry in this registry location, Windows 9x / Me checks for a locally cached
418 version of the user profile. Windows 9x / Me also checks the user's home directory (or other
419 specified directory if the location has been modified) on the server for the User Profile.
420 If a profile exists in both locations, the newer of the two is used. If the User Profile exists
421 on the server, but does not exist on the local machine, the profile on the server is downloaded
422 and used. If the User Profile only exists on the local machine, that copy is used.
424 If a User Profile is not found in either location, the Default User Profile from the Windows 9x / Me
425 machine is used and is copied to a newly created folder for the logged on user. At log off, any
426 changes that the user made are written to the user's local profile. If the user has a roaming
427 profile, the changes are written to the user's profile on the server.
428 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2990504"></a>MS Windows NT4 Workstation</h3></div></div><div></div></div><p>
429 On MS Windows NT4 the default user profile is obtained from the location
430 <tt class="filename">%SystemRoot%\Profiles</tt> which in a default installation will translate to
431 <tt class="filename">C:\WinNT\Profiles</tt>. Under this directory on a clean install there will be
432 three (3) directories: <tt class="filename">Administrator</tt>, <tt class="filename">All Users</tt>, <tt class="filename">Default User</tt>.
434 The <tt class="filename">All Users</tt> directory contains menu settings that are common across all
435 system users. The <tt class="filename">Default User</tt> directory contains menu entries that are
436 customisable per user depending on the profile settings chosen/created.
438 When a new user first logs onto an MS Windows NT4 machine a new profile is created from:
439 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>All Users settings</td></tr><tr><td>Default User settings (contains the default NTUser.DAT file)</td></tr></table><p>
440 When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain
441 the following steps are followed in respect of profile handling:
442 </p><div class="procedure"><ol type="1"><li><p>
443 The users' account information which is obtained during the logon process contains
444 the location of the users' desktop profile. The profile path may be local to the
445 machine or it may be located on a network share. If there exists a profile at the location
446 of the path from the user account, then this profile is copied to the location
447 <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>. This profile then inherits the
448 settings in the <tt class="filename">All Users</tt> profile in the <tt class="filename">%SystemRoot%\Profiles</tt>
451 If the user account has a profile path, but at it's location a profile does not exist,
452 then a new profile is created in the <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>
453 directory from reading the <tt class="filename">Default User</tt> profile.
455 If the NETLOGON share on the authenticating server (logon server) contains a policy file
456 (<tt class="filename">NTConfig.POL</tt>) then it's contents are applied to the <tt class="filename">NTUser.DAT</tt>
457 which is applied to the <tt class="filename">HKEY_CURRENT_USER</tt> part of the registry.
459 When the user logs out, if the profile is set to be a roaming profile it will be written
460 out to the location of the profile. The <tt class="filename">NTuser.DAT</tt> file is then
461 re-created from the contents of the <tt class="filename">HKEY_CURRENT_USER</tt> contents.
462 Thus, should there not exist in the NETLOGON share an <tt class="filename">NTConfig.POL</tt> at the
463 next logon, the effect of the previous <tt class="filename">NTConfig.POL</tt> will still be held
464 in the profile. The effect of this is known as <span class="emphasis"><em>tatooing</em></span>.
465 </p></li></ol></div><p>
466 MS Windows NT4 profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>. A Local profile
467 will stored in the <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt> location. A roaming profile will
468 also remain stored in the same way, unless the following registry key is created:
470 </p><pre class="programlisting">
471 HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\
472 "DeleteRoamingCache"=dword:00000001
475 In which case, the local copy (in <tt class="filename">%SystemRoot%\Profiles\%USERNAME%</tt>) will be
478 Under MS Windows NT4 default locations for common resources (like <tt class="filename">My Documents</tt>
479 may be redirected to a network share by modifying the following registry keys. These changes may be affected
480 via use of the System Policy Editor (to do so may require that you create your owns template extension
481 for the policy editor to allow this to be done through the GUI. Another way to do this is by way of first
482 creating a default user profile, then while logged in as that user, run regedt32 to edit the key settings.
484 The Registry Hive key that affects the behaviour of folders that are part of the default user profile
485 are controlled by entries on Windows NT4 is:
487 <tt class="filename">HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\</tt>
489 The above hive key contains a list of automatically managed folders. The default entries are:
491 </p><div class="table"><a name="id2990854"></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><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu </td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr></tbody></table></div><p>
493 The registry key that contains the location of the default profile settings is:
495 <tt class="filename">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders</tt>
497 The default entries are:
499 </p><div class="table"><a name="id2990998"></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><col></colgroup><tbody><tr><td>Common Desktop</td><td>%SystemRoot%\Profiles\All Users\Desktop</td></tr><tr><td>Common Programs</td><td>%SystemRoot%\Profiles\All Users\Programs</td></tr><tr><td>Common Start Menu</td><td>%SystemRoot%\Profiles\All Users\Start Menu</td></tr><tr><td>Common Startup</td><td>%SystemRoot%\Profiles\All Users\Start Menu\Programs\Startup</td></tr></tbody></table></div><p>
500 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2991058"></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>
501 MS Windows XP Home Edition does use default per user profiles, but can not participate
502 in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile
503 only from itself. While there are benefits in doing this the beauty of those MS Windows
504 clients that CAN participate in domain logon processes allows the administrator to create
505 a global default profile and to enforce it through the use of Group Policy Objects (GPOs).
507 When a new user first logs onto MS Windows 200x/XP machine the default profile is obtained from
508 <tt class="filename">C:\Documents and Settings\Default User</tt>. The administrator can modify (or change
509 the contents of this location and MS Windows 200x/XP will gladly use it. This is far from the optimum
510 arrangement since it will involve copying a new default profile to every MS Windows 200x/XP client
513 When MS Windows 200x/XP participate in a domain security context, and if the default user
514 profile is not found, then the client will search for a default profile in the NETLOGON share
515 of the authenticating server. ie: In MS Windows parlance:
516 <tt class="filename">%LOGONSERVER%\NETLOGON\Default User</tt> and if one exits there it will copy this
517 to the workstation to the <tt class="filename">C:\Documents and Settings\</tt> under the Windows
518 login name of the user.
519 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
520 This path translates, in Samba parlance, to the <tt class="filename">smb.conf</tt> <i class="parameter"><tt>[NETLOGON]</tt></i> share. The directory
521 should be created at the root of this share and must be called <tt class="filename">Default Profile</tt>.
523 If a default profile does not exist in this location then MS Windows 200x/XP will use the local
526 On logging out, the users' desktop profile will be stored to the location specified in the registry
527 settings that pertain to the user. If no specific policies have been created, or passed to the client
528 during the login process (as Samba does automatically), then the user's profile will be written to
529 the local machine only under the path <tt class="filename">C:\Documents and Settings\%USERNAME%</tt>.
531 Those wishing to modify the default behaviour can do so through three methods:
532 </p><div class="itemizedlist"><ul type="disc"><li><p>
533 Modify the registry keys on the local machine manually and place the new default profile in the
534 NETLOGON share root - NOT recommended as it is maintenance intensive.
536 Create an NT4 style NTConfig.POL file that specified this behaviour and locate this file
537 in the root of the NETLOGON share along with the new default profile.
539 Create a GPO that enforces this through Active Directory, and place the new default profile
540 in the NETLOGON share.
541 </p></li></ul></div><p>
542 The Registry Hive key that affects the behaviour of folders that are part of the default user profile
543 are controlled by entries on Windows 200x/XP is:
545 <tt class="filename">HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\</tt>
547 The above hive key contains a list of automatically managed folders. The default entries are:
549 </p><div class="table"><a name="id2991253"></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><col></colgroup><thead><tr><th>Name</th><th>Default Value</th></tr></thead><tbody><tr><td>AppData</td><td>%USERPROFILE%\Application Data</td></tr><tr><td>Cache</td><td>%USERPROFILE%\Local Settings\Temporary Internet Files</td></tr><tr><td>Cookies</td><td>%USERPROFILE%\Cookies</td></tr><tr><td>Desktop</td><td>%USERPROFILE%\Desktop</td></tr><tr><td>Favorites</td><td>%USERPROFILE%\Favorites</td></tr><tr><td>History</td><td>%USERPROFILE%\Local Settings\History</td></tr><tr><td>Local AppData</td><td>%USERPROFILE%\Local Settings\Application Data</td></tr><tr><td>Local Settings</td><td>%USERPROFILE%\Local Settings</td></tr><tr><td>My Pictures</td><td>%USERPROFILE%\My Documents\My Pictures</td></tr><tr><td>NetHood</td><td>%USERPROFILE%\NetHood</td></tr><tr><td>Personal</td><td>%USERPROFILE%\My Documents</td></tr><tr><td>PrintHood</td><td>%USERPROFILE%\PrintHood</td></tr><tr><td>Programs</td><td>%USERPROFILE%\Start Menu\Programs</td></tr><tr><td>Recent</td><td>%USERPROFILE%\Recent</td></tr><tr><td>SendTo</td><td>%USERPROFILE%\SendTo</td></tr><tr><td>Start Menu</td><td>%USERPROFILE%\Start Menu</td></tr><tr><td>Startup</td><td>%USERPROFILE%\Start Menu\Programs\Startup</td></tr><tr><td>Templates</td><td>%USERPROFILE%\Templates</td></tr></tbody></table></div><p>
551 There is also an entry called "Default" that has no value set. The default entry is of type <tt class="constant">REG_SZ</tt>, all
552 the others are of type <tt class="constant">REG_EXPAND_SZ</tt>.
554 It makes a huge difference to the speed of handling roaming user profiles if all the folders are
555 stored on a dedicated location on a network server. This means that it will NOT be necessary to
556 write the Outlook PST file over the network for every login and logout.
558 To set this to a network location you could use the following examples:
559 </p><p><tt class="filename">%LOGONSERVER%\%USERNAME%\Default Folders</tt></p><p>
560 This would store the folders in the user's home directory under a directory called <tt class="filename">Default Folders</tt>
562 </p><p><tt class="filename">\\<i class="replaceable"><tt>SambaServer</tt></i>\<i class="replaceable"><tt>FolderShare</tt></i>\%USERNAME%</tt></p><p>
563 in which case the default folders will be stored in the server named <i class="replaceable"><tt>SambaServer</tt></i>
564 in the share called <i class="replaceable"><tt>FolderShare</tt></i> under a directory that has the name of the MS Windows
565 user as seen by the Linux/Unix file system.
567 Please note that once you have created a default profile share, you MUST migrate a user's profile
568 (default or custom) to it.
570 MS Windows 200x/XP profiles may be <span class="emphasis"><em>Local</em></span> or <span class="emphasis"><em>Roaming</em></span>.
571 A roaming profile will be cached locally unless the following registry key is created:
572 </p><p><tt class="filename">HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\"DeleteRoamingCache"=dword:00000001</tt></p><p>
573 In which case, the local cache copy will be deleted on logout.
574 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2991562"></a>Common Errors</h2></div></div><div></div></div><p>
575 The following are some typical errors/problems/questions that have been asked.
576 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2991575"></a>How does one set up roaming profiles for just one (or a few) user/s or group/s?</h3></div></div><div></div></div><p>
577 With samba-2.2.x the choice you have is to enable or disable roaming
578 profiles support. It is a global only setting. The default is to have
579 roaming profiles and the default path will locate them in the user's home
582 If disabled globally then no-one will have roaming profile ability.
583 If enabled and you want it to apply only to certain machines, then on
584 those machines on which roaming profile support is NOT wanted it is then
585 necessary to disable roaming profile handling in the registry of each such
588 With samba-3.0.0 (soon to be released) you can have a global profile
589 setting in smb.conf _AND_ you can over-ride this by per-user settings
590 using the Domain User Manager (as with MS Windows NT4/ Win 2Kx).
592 In any case, you can configure only one profile per user. That profile can
594 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>A profile unique to that user</td></tr><tr><td>A mandatory profile (one the user can not change)</td></tr><tr><td>A group profile (really should be mandatory ie:unchangable)</td></tr></table></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2991638"></a>Can NOT use Roaming Profiles</h3></div></div><div></div></div><p>
595 “<span class="quote">
596 I dont want Roaming profile to be implemented, I just want to give users
599 Please help me I am totally lost with this error from past two days I tried
600 everything and googled around quite a bit but of no help. Please help me.
601 </span>”</p><p>
605 </p><div class="variablelist"><dl><dt><span class="term">Local profiles</span></dt><dd><p>
606 I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out
607 </p></dd><dt><span class="term">Roaming profiles</span></dt><dd><p>
608 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>can use auto-delete on logout option</td></tr><tr><td>requires a registry key change on workstation</td></tr></table><p>
612 </p><div class="variablelist"><dl><dt><span class="term">Personal Roaming profiles</span></dt><dd><p>
613 - should be preserved on a central server
614 - workstations 'cache' (store) a local copy
615 - used in case the profile can not be downloaded
617 </p></dd><dt><span class="term">Group profiles</span></dt><dd><p>- loaded from a central place</p></dd><dt><span class="term">Mandatory profiles</span></dt><dd><p>
618 - can be personal or group
619 - can NOT be changed (except by an administrator
620 </p></dd></dl></div><p>
621 </p></dd></dl></div><p>
624 A WinNT4/2K/XP profile can vary in size from 130KB to off the scale.
625 Outlook PST files are most often part of the profile and can be many GB in
626 size. On average (in a well controlled environment) roaming profile size of
627 2MB is a good rule of thumb to use for planning purposes. In an
628 undisciplined environment I have seen up to 2GB profiles. Users tend to
629 complain when it take an hour to log onto a workstation but they harvest
630 the fruits of folly (and ignorance).
632 The point of all the above is to show that roaming profiles and good
633 controls of how they can be changed as well as good discipline make up for
636 Microsoft's answer to the PST problem is to store all email in an MS
637 Exchange Server back-end. But this is another story ...!
639 So, having LOCAL profiles means:
641 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>If lots of users user each machine - lot's of local disk storage needed for local profiles</td></tr><tr><td>Every workstation the user logs into has it's own profile - can be very different from machine to machine</td></tr></table><p>
643 On the other hand, having roaming profiles means:
644 </p><table class="simplelist" border="0" summary="Simple list"><tr><td>The network administrator can control EVERY aspect of user profiles</td></tr><tr><td>With the use of mandatory profiles - a drastic reduction in network management overheads</td></tr><tr><td>User unhappiness about not being able to change their profiles soon fades as they get used to being able to work reliably</td></tr></table><p>
647 I have managed and installed MANY NT/2K networks and have NEVER found one
648 where users who move from machine to machine are happy with local
649 profiles. In the long run local profiles bite them.
650 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2991859"></a>Changing the default profile</h3></div></div><div></div></div><p>“<span class="quote">
651 When the client tries to logon to the PDC it looks for a profile to download
652 where do I put this default profile.
653 </span>”</p><p>
654 Firstly, your samba server need to be configured as a domain controller.
655 </p><pre class="programlisting">
657 os level = 32 (or more)
660 Plus you need to have a <i class="parameter"><tt>[netlogon]</tt></i> share that is world readable.
661 It is a good idea to add a logon script to pre-set printer and
662 drive connections. There is also a facility for automatically
663 synchronizing the workstation time clock with that of the logon
664 server (another good thing to do).
665 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
666 To invoke auto-deletion of roaming profile from the local
667 workstation cache (disk storage) you need to use the <span class="application">Group Policy Editor</span>
668 to create a file called <tt class="filename">NTConfig.POL</tt> with the appropriate entries. This
669 file needs to be located in the <i class="parameter"><tt>netlogon</tt></i> share root directory.</p></div><p>
670 Oh, of course the windows clients need to be members of the domain.
671 Workgroup machines do NOT do network logons - so they never see domain
674 Secondly, for roaming profiles you need:
676 logon path = \\%N\profiles\%U (with some such path)
677 logon drive = H: (Z: is the default)
679 Plus you need a PROFILES share that is world writable.
680 </p></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>
git.samba.org / nivanova / samba-autobuild / .git / blob