1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�27.�Desktop Profile Management</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies"><link rel="next" href="pam.html" title="Chapter�28.�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�27.�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" title="Chapter�27.�Desktop Profile Management"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter�27.�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><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id424054">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id424096">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id424145">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id424715">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id425983">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id426012">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id426108">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id426439">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id426567">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id426630">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id426656">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id426792">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id427317">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id427779">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id427789">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id427843">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id427992">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id428146">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id424054"></a>Features and Benefits</h2></div></div></div><p>
2
<a class="indexterm" name="id424061"></a>
1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter�27.�Desktop Profile Management</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part�III.�Advanced Configuration"><link rel="prev" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies"><link rel="next" href="pam.html" title="Chapter�28.�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�27.�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" title="Chapter�27.�Desktop Profile Management"><div class="titlepage"><div><div><h2 class="title"><a name="ProfileMgmt"></a>Chapter�27.�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><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><p class="pubdate">April 3 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="ProfileMgmt.html#id424037">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id424080">Roaming Profiles</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id424128">Samba Configuration for Profile Handling</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id424698">Windows Client Profile Configuration Information</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id425966">User Profile Hive Cleanup Service</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id425996">Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id426086">Profile Migration from Windows NT4/200x Server to Samba</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id426418">Mandatory Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id426546">Creating and Managing Group Profiles</a></span></dt><dt><span class="sect1"><a href="ProfileMgmt.html#id426613">Default Profile for Windows Users</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id426639">MS Windows 9x/Me</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id426778">MS Windows NT4 Workstation</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id427303">MS Windows 200x/XP</a></span></dt></dl></dd><dt><span class="sect1"><a href="ProfileMgmt.html#id427765">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="ProfileMgmt.html#id427775">Configuring Roaming Profiles for a Few Users or Groups</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id427829">Cannot Use Roaming Profiles</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id427978">Changing the Default Profile</a></span></dt><dt><span class="sect2"><a href="ProfileMgmt.html#id428131">Debugging Roaming Profiles and NT4-style Domain Policies</a></span></dt></dl></dd></dl></div><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id424037"></a>Features and Benefits</h2></div></div></div><p>
2
<a class="indexterm" name="id424045"></a>
3
3
Roaming profiles are feared by some, hated by a few, loved by many, and a godsend for
6
<a class="indexterm" name="id424072"></a>
6
<a class="indexterm" name="id424056"></a>
7
7
Roaming profiles allow an administrator to make available a consistent user desktop
8
8
as the user moves from one machine to another. This chapter provides much information
9
9
regarding how to configure and manage roaming profiles.
11
<a class="indexterm" name="id424084"></a>
11
<a class="indexterm" name="id424068"></a>
12
12
While roaming profiles might sound like nirvana to some, they are a real and tangible
13
13
problem to others. In particular, users of mobile computing tools, where often there may not
14
14
be a sustained network connection, are often better served by purely local profiles.
15
15
This chapter provides information to help the Samba administrator deal with those
17
</p></div><div class="sect1" title="Roaming Profiles"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id424096"></a>Roaming Profiles</h2></div></div></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
17
</p></div><div class="sect1" title="Roaming Profiles"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id424080"></a>Roaming Profiles</h2></div></div></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
18
18
Roaming profiles support is different for Windows 9x/Me and Windows NT4/200x.
20
20
Before discussing how to configure roaming profiles, it is useful to see how
21
21
Windows 9x/Me and Windows NT4/200x clients implement these features.
23
<a class="indexterm" name="id424116"></a>
23
<a class="indexterm" name="id424099"></a>
24
24
Windows 9x/Me clients send a NetUserGetInfo request to the server to get the user's
25
25
profiles location. However, the response does not have room for a separate
26
26
profiles location field, only the user's home share. This means that Windows 9x/Me
27
27
profiles are restricted to being stored in the user's home directory.
29
<a class="indexterm" name="id424129"></a>
30
<a class="indexterm" name="id424136"></a>
29
<a class="indexterm" name="id424112"></a>
30
<a class="indexterm" name="id424119"></a>
31
31
Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields
32
32
including a separate field for the location of the user's profiles.
33
</p><div class="sect2" title="Samba Configuration for Profile Handling"><div class="titlepage"><div><div><h3 class="title"><a name="id424145"></a>Samba Configuration for Profile Handling</h3></div></div></div><p>
33
</p><div class="sect2" title="Samba Configuration for Profile Handling"><div class="titlepage"><div><div><h3 class="title"><a name="id424128"></a>Samba Configuration for Profile Handling</h3></div></div></div><p>
34
34
This section documents how to configure Samba for MS Windows client profile support.
35
</p><div class="sect3" title="NT4/200x User Profiles"><div class="titlepage"><div><div><h4 class="title"><a name="id424154"></a>NT4/200x User Profiles</h4></div></div></div><p>
35
</p><div class="sect3" title="NT4/200x User Profiles"><div class="titlepage"><div><div><h4 class="title"><a name="id424138"></a>NT4/200x User Profiles</h4></div></div></div><p>
36
36
For example, to support Windows NT4/200x clients, set the following in the [global] section of the <code class="filename">smb.conf</code> file:
37
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424176"></a><em class="parameter"><code>logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</code></em></td></tr></table><p>
37
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424159"></a><em class="parameter"><code>logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath</code></em></td></tr></table><p>
38
38
This is typically implemented like:
39
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424196"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr></table><p>
39
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424179"></a><em class="parameter"><code>logon path = \\%L\Profiles\%U</code></em></td></tr></table><p>
40
40
where <span class="quote">“<span class="quote">%L</span>”</span> translates to the name of the Samba server and <span class="quote">“<span class="quote">%U</span>”</span> translates to the username.
42
42
The default for this option is <code class="filename">\\%N\%U\profile</code>, namely, <code class="filename">\\sambaserver\username\profile</code>.
45
45
browseable. Please refer to the man page for <code class="filename">smb.conf</code> regarding the different
46
46
semantics of <span class="quote">“<span class="quote">%L</span>”</span> and <span class="quote">“<span class="quote">%N</span>”</span>, as well as <span class="quote">“<span class="quote">%U</span>”</span> and <span class="quote">“<span class="quote">%u</span>”</span>.
47
47
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
48
<a class="indexterm" name="id424263"></a>
49
<a class="indexterm" name="id424269"></a>
48
<a class="indexterm" name="id424246"></a>
49
<a class="indexterm" name="id424253"></a>
50
50
MS Windows NT/200x clients at times do not disconnect a connection to a server between logons. It is recommended
51
51
to not use the <em class="parameter"><code>homes</code></em> metaservice name as part of the profile share path.
52
</p></div></div><div class="sect3" title="Windows 9x/Me User Profiles"><div class="titlepage"><div><div><h4 class="title"><a name="id424286"></a>Windows 9x/Me User Profiles</h4></div></div></div><p>
53
<a class="indexterm" name="id424294"></a>
54
<a class="indexterm" name="id424300"></a>
52
</p></div></div><div class="sect3" title="Windows 9x/Me User Profiles"><div class="titlepage"><div><div><h4 class="title"><a name="id424269"></a>Windows 9x/Me User Profiles</h4></div></div></div><p>
53
<a class="indexterm" name="id424277"></a>
54
<a class="indexterm" name="id424284"></a>
55
55
To support Windows 9x/Me clients, you must use the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>
56
56
parameter. Samba has been fixed so <strong class="userinput"><code>net use /home</code></strong> now works as well and it, too, relies
57
57
on the <em class="parameter"><code>logon home</code></em> parameter.
59
<a class="indexterm" name="id424335"></a>
60
<a class="indexterm" name="id424342"></a>
61
<a class="indexterm" name="id424348"></a>
59
<a class="indexterm" name="id424318"></a>
60
<a class="indexterm" name="id424325"></a>
61
<a class="indexterm" name="id424332"></a>
62
62
By using the <em class="parameter"><code>logon home</code></em> parameter, you are restricted to putting Windows 9x/Me profiles
63
63
in the user's home directory. But wait! There is a trick you can use. If you set the following in the
64
64
<em class="parameter"><code>[global]</code></em> section of your <code class="filename">smb.conf</code> file:
65
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424380"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr></table><p>
65
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424364"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr></table><p>
66
66
then your Windows 9x/Me clients will dutifully put their clients in a subdirectory
67
67
of your home directory called <code class="filename">.profiles</code> (making them hidden).
69
<a class="indexterm" name="id424402"></a>
69
<a class="indexterm" name="id424385"></a>
70
70
Not only that, but <strong class="userinput"><code>net use /home</code></strong> will also work because of a feature in
71
71
Windows 9x/Me. It removes any directory stuff off the end of the home directory area
72
72
and only uses the server and share portion. That is, it looks like you
73
73
specified <code class="filename">\\%L\%U</code> for <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>.
74
</p></div><div class="sect3" title="Mixed Windows Windows 9x/Me and NT4/200x User Profiles"><div class="titlepage"><div><div><h4 class="title"><a name="id424435"></a>Mixed Windows Windows 9x/Me and NT4/200x User Profiles</h4></div></div></div><p>
74
</p></div><div class="sect3" title="Mixed Windows Windows 9x/Me and NT4/200x User Profiles"><div class="titlepage"><div><div><h4 class="title"><a name="id424419"></a>Mixed Windows Windows 9x/Me and NT4/200x User Profiles</h4></div></div></div><p>
75
75
You can support profiles for Windows 9x and Windows NT clients by setting both the
76
76
<a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> and <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> parameters. For example,
77
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424473"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr><tr><td><a class="indexterm" name="id424484"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr></table><p>
78
<a class="indexterm" name="id424498"></a>
77
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id424456"></a><em class="parameter"><code>logon home = \\%L\%U\.profiles</code></em></td></tr><tr><td><a class="indexterm" name="id424468"></a><em class="parameter"><code>logon path = \\%L\profiles\%U</code></em></td></tr></table><p>
78
<a class="indexterm" name="id424481"></a>
79
79
Windows 9x/Me and NT4 and later profiles should not be stored in the same location because
80
80
Windows NT4 and later will experience problems with mixed profile environments.
81
</p></div><div class="sect3" title="Disabling Roaming Profile Support"><div class="titlepage"><div><div><h4 class="title"><a name="id424509"></a>Disabling Roaming Profile Support</h4></div></div></div><p>
82
<a class="indexterm" name="id424516"></a>
81
</p></div><div class="sect3" title="Disabling Roaming Profile Support"><div class="titlepage"><div><div><h4 class="title"><a name="id424492"></a>Disabling Roaming Profile Support</h4></div></div></div><p>
82
<a class="indexterm" name="id424500"></a>
83
83
The question often asked is, <span class="quote">“<span class="quote">How may I enforce use of local profiles?</span>”</span> or
84
84
<span class="quote">“<span class="quote">How do I disable roaming profiles?</span>”</span>
86
<a class="indexterm" name="id424535"></a>
86
<a class="indexterm" name="id424518"></a>
87
87
There are three ways of doing this:
88
</p><a class="indexterm" name="id424543"></a><div class="variablelist"><dl><dt><span class="term">In <code class="filename">smb.conf</code></span></dt><dd><p>
88
</p><a class="indexterm" name="id424526"></a><div class="variablelist"><dl><dt><span class="term">In <code class="filename">smb.conf</code></span></dt><dd><p>
89
89
Affect the following settings and ALL clients will be forced to use a local profile:
90
90
<a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home = </a> and <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path = </a>
92
92
The arguments to these parameters must be left blank. It is necessary to include the <code class="constant">=</code> sign
93
93
to specifically assign the empty value.
94
94
</p></dd><dt><span class="term">MS Windows Registry:</span></dt><dd><p>
95
<a class="indexterm" name="id424608"></a>
96
<a class="indexterm" name="id424615"></a>
95
<a class="indexterm" name="id424592"></a>
96
<a class="indexterm" name="id424598"></a>
97
97
Use the Microsoft Management Console (MMC) <code class="literal">gpedit.msc</code> to instruct your MS Windows XP
98
98
machine to use only a local profile. This, of course, modifies registry settings. The full
99
99
path to the option is:
116
116
Consult the MS Windows registry guide for your particular MS Windows version for more information
117
117
about which registry keys to change to enforce use of only local user profiles.
118
118
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
119
<a class="indexterm" name="id424702"></a>
119
<a class="indexterm" name="id424686"></a>
120
120
The specifics of how to convert a local profile to a roaming profile, or a roaming profile
121
121
to a local one, vary according to the version of MS Windows you are running. Consult the Microsoft MS
122
122
Windows Resource Kit for your version of Windows for specific information.
123
</p></div></div></div><div class="sect2" title="Windows Client Profile Configuration Information"><div class="titlepage"><div><div><h3 class="title"><a name="id424715"></a>Windows Client Profile Configuration Information</h3></div></div></div><div class="sect3" title="Windows 9x/Me Profile Setup"><div class="titlepage"><div><div><h4 class="title"><a name="id424721"></a>Windows 9x/Me Profile Setup</h4></div></div></div><p>
123
</p></div></div></div><div class="sect2" title="Windows Client Profile Configuration Information"><div class="titlepage"><div><div><h3 class="title"><a name="id424698"></a>Windows Client Profile Configuration Information</h3></div></div></div><div class="sect3" title="Windows 9x/Me Profile Setup"><div class="titlepage"><div><div><h4 class="title"><a name="id424704"></a>Windows 9x/Me Profile Setup</h4></div></div></div><p>
124
124
When a user first logs in on Windows 9x, the file user.DAT is created, as are folders <code class="filename">Start
125
125
Menu</code>, <code class="filename">Desktop</code>, <code class="filename">Programs</code>, and
126
126
<code class="filename">Nethood</code>. These directories and their contents will be merged with the local versions
144
144
ensure that the Primary Logon is <span class="guilabel">Client for Microsoft Networks</span>. Press
145
145
<span class="guibutton">OK</span>, and this time allow the computer to reboot.
146
146
</p></li></ol></div><p>
147
<a class="indexterm" name="id424926"></a>
148
<a class="indexterm" name="id424933"></a>
149
<a class="indexterm" name="id424940"></a>
150
<a class="indexterm" name="id424947"></a>
147
<a class="indexterm" name="id424910"></a>
148
<a class="indexterm" name="id424916"></a>
149
<a class="indexterm" name="id424923"></a>
150
<a class="indexterm" name="id424930"></a>
151
151
Under Windows 9x/Me, profiles are downloaded from the Primary Logon. If you have the Primary Logon
152
152
as <span class="quote">“<span class="quote">Client for Novell Networks</span>”</span>, then the profiles and logon script will be downloaded from
153
153
your Novell server. If you have the Primary Logon as <span class="quote">“<span class="quote">Windows Logon</span>”</span>, then the profiles will
154
154
be loaded from the local machine a bit against the concept of roaming profiles, it would seem!
156
<a class="indexterm" name="id424970"></a>
156
<a class="indexterm" name="id424954"></a>
157
157
You will now find that the Microsoft Networks Login box contains <code class="constant">[user, password, domain]</code> instead
158
158
of just <code class="constant">[user, password]</code>. Type in the Samba server's domain name (or any other domain known to exist,
159
159
but bear in mind that the user will be authenticated against this domain and profiles downloaded from it
168
168
the Samba server and verify that the <code class="filename">Desktop</code>, <code class="filename">Start Menu</code>,
169
169
<code class="filename">Programs</code>, and <code class="filename">Nethood</code> folders have been created.
171
<a class="indexterm" name="id425051"></a>
172
<a class="indexterm" name="id425058"></a>
173
<a class="indexterm" name="id425065"></a>
171
<a class="indexterm" name="id425035"></a>
172
<a class="indexterm" name="id425042"></a>
173
<a class="indexterm" name="id425048"></a>
174
174
These folders will be cached locally on the client and updated when the user logs off (if
175
175
you haven't made them read-only by then). You will find that if the user creates further folders or
176
176
shortcuts, the client will merge the profile contents downloaded with the contents of the profile
177
177
directory already on the local client, taking the newest folders and shortcut from each set.
179
<a class="indexterm" name="id425078"></a>
180
<a class="indexterm" name="id425085"></a>
181
<a class="indexterm" name="id425092"></a>
182
<a class="indexterm" name="id425099"></a>
179
<a class="indexterm" name="id425062"></a>
180
<a class="indexterm" name="id425068"></a>
181
<a class="indexterm" name="id425075"></a>
182
<a class="indexterm" name="id425082"></a>
183
183
If you have made the folders/files read-only on the Samba server, then you will get errors from
184
184
the Windows 9x/Me machine on logon and logout as it attempts to merge the local and remote profile.
185
185
Basically, if you have any errors reported by the Windows 9x/Me machine, check the UNIX file permissions
186
186
and ownership rights on the profile directory contents, on the Samba server.
188
<a class="indexterm" name="id425112"></a>
189
<a class="indexterm" name="id425119"></a>
190
<a class="indexterm" name="id425126"></a>
191
<a class="indexterm" name="id425133"></a>
192
<a class="indexterm" name="id425139"></a>
188
<a class="indexterm" name="id425095"></a>
189
<a class="indexterm" name="id425102"></a>
190
<a class="indexterm" name="id425109"></a>
191
<a class="indexterm" name="id425116"></a>
192
<a class="indexterm" name="id425123"></a>
193
193
If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below.
194
194
When this user next logs in, the user will be told that he/she is logging in <span class="quote">“<span class="quote">for the first
195
195
time</span>”</span>.
224
224
in their profile directory, as well as the local <span class="quote">“<span class="quote">desktop,</span>”</span> <span class="quote">“<span class="quote">nethood,</span>”</span>
225
225
<span class="quote">“<span class="quote">start menu,</span>”</span> and <span class="quote">“<span class="quote">programs</span>”</span> folders.
227
<a class="indexterm" name="id425316"></a>
228
<a class="indexterm" name="id425323"></a>
229
<a class="indexterm" name="id425330"></a>
230
<a class="indexterm" name="id425337"></a>
227
<a class="indexterm" name="id425300"></a>
228
<a class="indexterm" name="id425306"></a>
229
<a class="indexterm" name="id425313"></a>
230
<a class="indexterm" name="id425320"></a>
231
231
If all else fails, increase Samba's debug log levels to between 3 and 10, and/or run a packet
232
232
sniffer program such as ethereal or <code class="literal">netmon.exe</code>, and look for error messages.
234
<a class="indexterm" name="id425354"></a>
235
<a class="indexterm" name="id425361"></a>
234
<a class="indexterm" name="id425337"></a>
235
<a class="indexterm" name="id425344"></a>
236
236
If you have access to an Windows NT4/200x server, then first set up roaming profiles and/or
237
237
netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces
238
238
provided with Windows NT4/200x server, and see what the differences are with the equivalent Samba trace.
239
</p></div><div class="sect3" title="Windows NT4 Workstation"><div class="titlepage"><div><div><h4 class="title"><a name="id425372"></a>Windows NT4 Workstation</h4></div></div></div><p>
239
</p></div><div class="sect3" title="Windows NT4 Workstation"><div class="titlepage"><div><div><h4 class="title"><a name="id425356"></a>Windows NT4 Workstation</h4></div></div></div><p>
240
240
When a user first logs in to a Windows NT workstation, the profile NTuser.DAT is created. The profile
241
241
location can be now specified through the <a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> parameter.
244
244
This should be set to <code class="filename">H:</code> or any other drive, and should be used in conjunction with
245
245
the new <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> parameter.
247
<a class="indexterm" name="id425429"></a>
248
<a class="indexterm" name="id425435"></a>
247
<a class="indexterm" name="id425412"></a>
248
<a class="indexterm" name="id425419"></a>
249
249
The entry for the NT4 profile is a directory, not a file. The NT help on profiles mentions that a
250
250
directory is also created with a .PDS extension. The user, while logging in, must have write permission
251
251
to create the full profile path (and the folder with the .PDS extension for those situations where it
252
252
might be created).
254
<a class="indexterm" name="id425448"></a>
254
<a class="indexterm" name="id425432"></a>
255
255
In the profile directory, Windows NT4 creates more folders than Windows 9x/Me. It creates
256
256
<code class="filename">Application Data</code> and others, as well as <code class="filename">Desktop</code>,
257
257
<code class="filename">Nethood</code>, <code class="filename">Start Menu,</code> and <code class="filename">Programs</code>.
258
258
The profile itself is stored in a file <code class="filename">NTuser.DAT</code>. Nothing appears to be stored
259
259
in the .PDS directory, and its purpose is currently unknown.
261
<a class="indexterm" name="id425496"></a>
262
<a class="indexterm" name="id425502"></a>
261
<a class="indexterm" name="id425479"></a>
262
<a class="indexterm" name="id425486"></a>
263
263
You can use the <span class="application">System Control Panel</span> to copy a local profile onto
264
264
a Samba server (see NT help on profiles; it is also capable of firing up the correct location in the
265
265
<span class="application">System Control Panel</span> for you). The NT help file also mentions that renaming
296
296
</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>On the XP workstation, log in with an administrative account.</p></li><li class="step" title="Step 2"><p>Click on <span class="guimenu">Start</span> -> <span class="guimenuitem">Run</span>.</p></li><li class="step" title="Step 3"><p>Type <code class="literal">mmc</code>.</p></li><li class="step" title="Step 4"><p>Click on <span class="guibutton">OK</span>.</p></li><li class="step" title="Step 5"><p>A Microsoft Management Console should appear.</p></li><li class="step" title="Step 6"><p>Click on <span class="guimenu">File</span> -> <span class="guimenuitem">Add/Remove Snap-in</span> -> <span class="guimenuitem">Add</span>.</p></li><li class="step" title="Step 7"><p>Double-click on <span class="guiicon">Group Policy</span>.</p></li><li class="step" title="Step 8"><p>Click on <span class="guibutton">Finish</span> -> <span class="guibutton">Close</span>.</p></li><li class="step" title="Step 9"><p>Click on <span class="guibutton">OK</span>.</p></li><li class="step" title="Step 10"><p>In the <span class="quote">“<span class="quote">Console Root</span>”</span> window expand <span class="guiicon">Local Computer Policy</span> ->
297
297
<span class="guiicon">Computer Configuration</span> -> <span class="guiicon">Administrative Templates</span> ->
298
298
<span class="guiicon">System</span> -> <span class="guiicon">User Profiles</span>.</p></li><li class="step" title="Step 11"><p>Double-click on <span class="guilabel">Do not check for user ownership of Roaming Profile Folders</span>.</p></li><li class="step" title="Step 12"><p>Select <span class="guilabel">Enabled</span>.</p></li><li class="step" title="Step 13"><p>Click on <span class="guibutton">OK</span>.</p></li><li class="step" title="Step 14"><p>Close the whole console. You do not need to save the settings (this refers to the
299
console settings rather than the policies you have changed).</p></li><li class="step" title="Step 15"><p>Reboot.</p></li></ol></div></div></div></div><div class="sect2" title="User Profile Hive Cleanup Service"><div class="titlepage"><div><div><h3 class="title"><a name="id425983"></a>User Profile Hive Cleanup Service</h3></div></div></div><p>
299
console settings rather than the policies you have changed).</p></li><li class="step" title="Step 15"><p>Reboot.</p></li></ol></div></div></div></div><div class="sect2" title="User Profile Hive Cleanup Service"><div class="titlepage"><div><div><h3 class="title"><a name="id425966"></a>User Profile Hive Cleanup Service</h3></div></div></div><p>
300
300
There are certain situations that cause a cached local copy of roaming profile not to be deleted on exit, even if
301
301
the policy to force such deletion is set. To deal with that situation, a special service was created. The application
302
302
<code class="literal">UPHClean</code> (User Profile Hive Cleanup) can be installed as a service on Windows NT4/2000/XP Professional
303
303
and Windows 2003.
305
305
The UPHClean software package can be downloaded from the User Profile Hive Cleanup
306
Service<sup>[<a name="id426004" href="#ftn.id426004" class="footnote">7</a>]</sup>
306
Service<sup>[<a name="id425987" href="#ftn.id425987" class="footnote">7</a>]</sup>
308
</p></div><div class="sect2" title="Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations"><div class="titlepage"><div><div><h3 class="title"><a name="id426012"></a>Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</h3></div></div></div><p>
309
<a class="indexterm" name="id426020"></a>
310
<a class="indexterm" name="id426027"></a>
308
</p></div><div class="sect2" title="Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations"><div class="titlepage"><div><div><h3 class="title"><a name="id425996"></a>Sharing Profiles between Windows 9x/Me and NT4/200x/XP Workstations</h3></div></div></div><p>
309
<a class="indexterm" name="id426004"></a>
310
<a class="indexterm" name="id426011"></a>
311
311
Sharing of desktop profiles between Windows versions is not recommended. Desktop profiles are an
312
312
evolving phenomenon, and profiles for later versions of MS Windows clients add features that may interfere
313
313
with earlier versions of MS Windows clients. Probably the more salient reason to not mix profiles is
319
319
location for the profiles. The <code class="filename">smb.conf</code> parameters that need to be common are
320
320
<a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> and <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a>.
322
<a class="indexterm" name="id426080"></a>
323
<a class="indexterm" name="id426086"></a>
322
<a class="indexterm" name="id426058"></a>
323
<a class="indexterm" name="id426064"></a>
324
324
If you have this set up correctly, you will find separate <code class="filename">user.DAT</code> and
325
325
<code class="filename">NTuser.DAT</code> files in the same profile directory.
326
</p></div><div class="sect2" title="Profile Migration from Windows NT4/200x Server to Samba"><div class="titlepage"><div><div><h3 class="title"><a name="id426108"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div></div><p>
327
<a class="indexterm" name="id426116"></a>
326
</p></div><div class="sect2" title="Profile Migration from Windows NT4/200x Server to Samba"><div class="titlepage"><div><div><h3 class="title"><a name="id426086"></a>Profile Migration from Windows NT4/200x Server to Samba</h3></div></div></div><p>
327
<a class="indexterm" name="id426094"></a>
328
328
There is nothing to stop you from specifying any path that you like for the location of users' profiles.
329
329
Therefore, you could specify that the profile be stored on a Samba server or any other SMB server,
330
330
as long as that SMB server supports encrypted passwords.
331
331
</p><div class="sect3" title="Windows NT4 Profile Management Tools"><div class="titlepage"><div><div><h4 class="title"><a name="profilemigrn"></a>Windows NT4 Profile Management Tools</h4></div></div></div><p>
332
<a class="indexterm" name="id426138"></a>
332
<a class="indexterm" name="id426115"></a>
333
333
Unfortunately, the resource kit information is specific to the version of MS Windows NT4/200x. The
334
334
correct resource kit is required for each platform.
335
</p><p>Here is a quick guide:</p><div class="procedure" title="Procedure�27.1.�Profile Migration Procedure"><a name="id426150"></a><p class="title"><b>Procedure�27.1.�Profile Migration Procedure</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> On your NT4 domain controller, right-click on <span class="guiicon">My Computer</span>, then select
335
</p><p>Here is a quick guide:</p><div class="procedure" title="Procedure�27.1.�Profile Migration Procedure"><a name="id426128"></a><p class="title"><b>Procedure�27.1.�Profile Migration Procedure</b></p><ol class="procedure" type="1"><li class="step" title="Step 1"><p> On your NT4 domain controller, right-click on <span class="guiicon">My Computer</span>, then select
336
336
<span class="guilabel">Properties</span>, then the tab labeled <span class="guilabel">User Profiles</span>. </p></li><li class="step" title="Step 2"><p> Select a user profile you want to migrate and click on it. </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>I am using the term <span class="quote">“<span class="quote">migrate</span>”</span> loosely. You can copy a profile to create a group
337
337
profile. You can give the user <em class="parameter"><code>Everyone</code></em> rights to the profile you copy this to. That
338
338
is what you need to do, since your Samba domain is not a member of a trust relationship with your NT4
340
340
<code class="filename">c:\temp\foobar</code></p></li><li class="step" title="Step 5"><p>Click on <span class="guibutton">Change</span> in the <span class="guilabel">Permitted to use</span> box.</p></li><li class="step" title="Step 6"><p>Click on the group <span class="quote">“<span class="quote">Everyone</span>”</span>, click on <span class="guibutton">OK</span>. This
341
341
closes the <span class="quote">“<span class="quote">choose user</span>”</span> box.</p></li><li class="step" title="Step 7"><p>Now click on <span class="guibutton">OK</span>.</p></li></ol></div><p>
342
342
Follow these steps for every profile you need to migrate.
343
</p></div><div class="sect3" title="Side Bar Notes"><div class="titlepage"><div><div><h4 class="title"><a name="id426291"></a>Side Bar Notes</h4></div></div></div><p>
344
<a class="indexterm" name="id426298"></a>
345
<a class="indexterm" name="id426305"></a>
343
</p></div><div class="sect3" title="Side Bar Notes"><div class="titlepage"><div><div><h4 class="title"><a name="id426269"></a>Side Bar Notes</h4></div></div></div><p>
344
<a class="indexterm" name="id426277"></a>
345
<a class="indexterm" name="id426283"></a>
346
346
You should obtain the SID of your NT4 domain. You can use the <code class="literal">net rpc info</code> to do this.
347
347
See <a class="link" href="NetCommand.html" title="Chapter�13.�Remote and Local Management: The Net Command">The Net Command Chapter</a>, <a class="link" href="NetCommand.html#netmisc1" title="Other Miscellaneous Operations">Other Miscellaneous Operations</a> for more information.
348
</p></div><div class="sect3" title="moveuser.exe"><div class="titlepage"><div><div><h4 class="title"><a name="id426340"></a>moveuser.exe</h4></div></div></div><p>
349
<a class="indexterm" name="id426347"></a>
348
</p></div><div class="sect3" title="moveuser.exe"><div class="titlepage"><div><div><h4 class="title"><a name="id426318"></a>moveuser.exe</h4></div></div></div><p>
349
<a class="indexterm" name="id426326"></a>
350
350
The Windows 200x professional resource kit has <code class="literal">moveuser.exe</code>.
351
351
<code class="literal">moveuser.exe</code> changes the security of a profile from one user to another. This allows the
352
352
account domain to change and/or the username to change.
354
354
This command is like the Samba <code class="literal">profiles</code> tool.
355
</p></div><div class="sect3" title="Get SID"><div class="titlepage"><div><div><h4 class="title"><a name="id426379"></a>Get SID</h4></div></div></div><p>
356
<a class="indexterm" name="id426387"></a>
357
<a class="indexterm" name="id426393"></a>
355
</p></div><div class="sect3" title="Get SID"><div class="titlepage"><div><div><h4 class="title"><a name="id426358"></a>Get SID</h4></div></div></div><p>
356
<a class="indexterm" name="id426365"></a>
357
<a class="indexterm" name="id426372"></a>
358
358
You can identify the SID by using <code class="literal">GetSID.exe</code> from the Windows NT Server 4.0 Resource Kit.
360
360
Windows NT 4.0 stores the local profile information in the registry under the following key:
364
364
on to this computer. (To find the profile information for the user whose locally cached profile you want
365
365
to move, find the SID for the user with the <code class="literal">GetSID.exe</code> utility.) Inside the appropriate user's subkey,
366
366
you will see a string value named <em class="parameter"><code>ProfileImagePath</code></em>.
367
</p></div></div></div><div class="sect1" title="Mandatory Profiles"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id426439"></a>Mandatory Profiles</h2></div></div></div><p>
368
<a class="indexterm" name="id426447"></a>
367
</p></div></div></div><div class="sect1" title="Mandatory Profiles"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id426418"></a>Mandatory Profiles</h2></div></div></div><p>
368
<a class="indexterm" name="id426425"></a>
369
369
A mandatory profile is a profile that the user does not have the ability to overwrite. During the
370
370
user's session, it may be possible to change the desktop environment; however, as the user logs out, all changes
371
371
made will be lost. If it is desired to not allow the user any ability to change the desktop environment,
372
372
then this must be done through policy settings. See <a class="link" href="PolicyMgmt.html" title="Chapter�26.�System and Account Policies">System and Account
374
374
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
375
<a class="indexterm" name="id426468"></a>
376
<a class="indexterm" name="id426475"></a>
377
<a class="indexterm" name="id426482"></a>
375
<a class="indexterm" name="id426447"></a>
376
<a class="indexterm" name="id426453"></a>
377
<a class="indexterm" name="id426460"></a>
378
378
Under NO circumstances should the profile directory (or its contents) be made read-only because this may
379
379
render the profile unusable. Where it is essential to make a profile read-only within the UNIX file system,
380
380
this can be done, but then you absolutely must use the <code class="literal">fake-permissions</code> VFS module to
381
381
instruct MS Windows NT/200x/XP clients that the Profile has write permission for the user. See <a class="link" href="VFS.html#fakeperms" title="fake_perms">fake_perms VFS module</a>.
383
<a class="indexterm" name="id426508"></a>
384
<a class="indexterm" name="id426515"></a>
383
<a class="indexterm" name="id426486"></a>
384
<a class="indexterm" name="id426493"></a>
385
385
For MS Windows NT4/200x/XP, the procedure shown in <a class="link" href="ProfileMgmt.html#profilemigrn" title="Windows NT4 Profile Management Tools">Profile Migration from Windows
386
386
NT4/200x Server to Samba</a> can also be used to create mandatory profiles. To convert a group profile into
387
387
a mandatory profile, simply locate the <code class="filename">NTUser.DAT</code> file in the copied profile and rename
388
388
it to <code class="filename">NTUser.MAN</code>.
390
<a class="indexterm" name="id426546"></a>
390
<a class="indexterm" name="id426524"></a>
391
391
For MS Windows 9x/Me, it is the <code class="filename">User.DAT</code> file that must be renamed to
392
392
<code class="filename">User.MAN</code> to effect a mandatory profile.
393
</p></div><div class="sect1" title="Creating and Managing Group Profiles"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id426567"></a>Creating and Managing Group Profiles</h2></div></div></div><p>
394
<a class="indexterm" name="id426575"></a>
395
<a class="indexterm" name="id426582"></a>
396
<a class="indexterm" name="id426589"></a>
397
<a class="indexterm" name="id426596"></a>
393
</p></div><div class="sect1" title="Creating and Managing Group Profiles"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id426546"></a>Creating and Managing Group Profiles</h2></div></div></div><p>
394
<a class="indexterm" name="id426554"></a>
395
<a class="indexterm" name="id426561"></a>
396
<a class="indexterm" name="id426567"></a>
397
<a class="indexterm" name="id426574"></a>
398
398
Most organizations are arranged into departments. There is a nice benefit in this fact, since usually
399
399
most users in a department require the same desktop applications and the same desktop layout. MS
400
400
Windows NT4/200x/XP will allow the use of group profiles. A group profile is a profile that is created
401
401
first using a template (example) user. Then using the profile migration tool (see above), the profile is
402
402
assigned access rights for the user group that needs to be given access to the group profile.
404
<a class="indexterm" name="id426610"></a>
404
<a class="indexterm" name="id426593"></a>
405
405
The next step is rather important. Instead of assigning a group profile to users (Using User Manager)
406
406
on a <span class="quote">“<span class="quote">per-user</span>”</span> basis, the group itself is assigned the now modified profile.
407
407
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
408
408
Be careful with group profiles. If the user who is a member of a group also has a personal
409
409
profile, then the result will be a fusion (merge) of the two.
410
</p></div></div><div class="sect1" title="Default Profile for Windows Users"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id426630"></a>Default Profile for Windows Users</h2></div></div></div><p>
411
<a class="indexterm" name="id426638"></a>
412
<a class="indexterm" name="id426644"></a>
410
</p></div></div><div class="sect1" title="Default Profile for Windows Users"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id426613"></a>Default Profile for Windows Users</h2></div></div></div><p>
411
<a class="indexterm" name="id426620"></a>
412
<a class="indexterm" name="id426627"></a>
413
413
MS Windows 9x/Me and NT4/200x/XP will use a default profile for any user for whom a profile
414
414
does not already exist. Armed with a knowledge of where the default profile is located on the Windows
415
415
workstation, and knowing which registry keys affect the path from which the default profile is created,
416
416
it is possible to modify the default profile to one that has been optimized for the site. This has
417
417
significant administrative advantages.
418
</p><div class="sect2" title="MS Windows 9x/Me"><div class="titlepage"><div><div><h3 class="title"><a name="id426656"></a>MS Windows 9x/Me</h3></div></div></div><p>
419
<a class="indexterm" name="id426664"></a>
420
<a class="indexterm" name="id426671"></a>
418
</p><div class="sect2" title="MS Windows 9x/Me"><div class="titlepage"><div><div><h3 class="title"><a name="id426639"></a>MS Windows 9x/Me</h3></div></div></div><p>
419
<a class="indexterm" name="id426647"></a>
420
<a class="indexterm" name="id426653"></a>
421
421
To enable default per-use profiles in Windows 9x/Me, you can either use the <span class="application">Windows
422
422
98 System Policy Editor</span> or change the registry directly.
427
427
select <span class="guilabel">User Profiles</span>, and click on the enable box. Remember to save the registry
430
<a class="indexterm" name="id426728"></a>
430
<a class="indexterm" name="id426711"></a>
431
431
To modify the registry directly, launch the <span class="application">Registry Editor</span>
432
432
(<code class="literal">regedit.exe</code>) and select the hive <code class="filename">HKEY_LOCAL_MACHINE\Network\Logon</code>.
433
433
Now add a DWORD type key with the name <span class="quote">“<span class="quote">User Profiles.</span>”</span> To enable user profiles to set the value
434
434
to 1; to disable user profiles set it to 0.
435
</p><div class="sect3" title="User Profile Handling with Windows 9x/Me"><div class="titlepage"><div><div><h4 class="title"><a name="id426759"></a>User Profile Handling with Windows 9x/Me</h4></div></div></div><p>
435
</p><div class="sect3" title="User Profile Handling with Windows 9x/Me"><div class="titlepage"><div><div><h4 class="title"><a name="id426742"></a>User Profile Handling with Windows 9x/Me</h4></div></div></div><p>
436
436
When a user logs on to a Windows 9x/Me machine, the local profile path,
437
437
<code class="filename">HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList</code>, is checked
438
438
for an existing entry for that user.
474
474
location. </p></li><li class="step" title="Step 2"><p> If the user account has a profile path, but at its location a profile does not
475
475
exist, then a new profile is created in the <code class="filename">%SystemRoot%\Profiles\%USERNAME%</code>
476
476
directory from reading the <code class="filename">Default User</code> profile. </p></li><li class="step" title="Step 3"><p>
477
<a class="indexterm" name="id426929"></a>
478
<a class="indexterm" name="id426936"></a>
477
479
<a class="indexterm" name="id426943"></a>
478
480
<a class="indexterm" name="id426950"></a>
479
<a class="indexterm" name="id426957"></a>
480
<a class="indexterm" name="id426964"></a>
481
<a class="indexterm" name="id426971"></a>
481
<a class="indexterm" name="id426956"></a>
482
482
If the NETLOGON share on the authenticating server (logon server) contains
483
483
a policy file (<code class="filename">NTConfig.POL</code>), then its contents are applied to the
484
484
<code class="filename">NTUser.DAT</code>, which is applied to the <code class="filename">HKEY_CURRENT_USER</code>
531
531
The default entries are shown in <a class="link" href="ProfileMgmt.html#regkeys" title="Table�27.2.�Defaults of Profile Settings Registry Keys">Defaults of Profile Settings Registry Keys</a>.
532
</p><div class="table"><a name="regkeys"></a><p class="title"><b>Table�27.2.�Defaults of Profile Settings Registry Keys</b></p><div class="table-contents"><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><br class="table-break"></div><div class="sect2" title="MS Windows 200x/XP"><div class="titlepage"><div><div><h3 class="title"><a name="id427317"></a>MS Windows 200x/XP</h3></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
533
<a class="indexterm" name="id427326"></a>
534
<a class="indexterm" name="id427333"></a>
535
<a class="indexterm" name="id427339"></a>
536
<a class="indexterm" name="id427346"></a>
532
</p><div class="table"><a name="regkeys"></a><p class="title"><b>Table�27.2.�Defaults of Profile Settings Registry Keys</b></p><div class="table-contents"><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><br class="table-break"></div><div class="sect2" title="MS Windows 200x/XP"><div class="titlepage"><div><div><h3 class="title"><a name="id427303"></a>MS Windows 200x/XP</h3></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
533
<a class="indexterm" name="id427312"></a>
534
<a class="indexterm" name="id427318"></a>
535
<a class="indexterm" name="id427325"></a>
536
<a class="indexterm" name="id427332"></a>
537
537
MS Windows XP Home Edition does use default per-user profiles, but cannot participate
538
538
in domain security, cannot log onto an NT/ADS-style domain, and thus can obtain the profile only
539
539
from itself. While there are benefits in doing this, the beauty of those MS Windows clients that
540
540
can participate in domain logon processes is that they allow the administrator to create a global default
541
541
profile and enforce it through the use of Group Policy Objects (GPOs).
543
<a class="indexterm" name="id427360"></a>
543
<a class="indexterm" name="id427346"></a>
544
544
When a new user first logs onto an MS Windows 200x/XP machine, the default profile is obtained from
545
545
<code class="filename">C:\Documents and Settings\Default User</code>. The administrator can modify or change the
546
546
contents of this location, and MS Windows 200x/XP will gladly use it. This is far from the optimum arrangement,
547
547
since it will involve copying a new default profile to every MS Windows 200x/XP client workstation.
549
<a class="indexterm" name="id427379"></a>
549
<a class="indexterm" name="id427365"></a>
550
550
When MS Windows 200x/XP participates in a domain security context, and if the default user profile is not
551
551
found, then the client will search for a default profile in the NETLOGON share of the authenticating server.
552
552
In MS Windows parlance, it is <code class="filename">%LOGONSERVER%\NETLOGON\Default User,</code>
589
589
(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>.
590
590
A roaming profile is cached locally unless the following registry key is created:
592
<a class="indexterm" name="id427757"></a>
592
<a class="indexterm" name="id427743"></a>
593
593
</p><p> </p><pre class="programlisting"> HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\
594
594
winlogon\"DeleteRoamingCache"=dword:00000001</pre><p>
595
595
In this case, the local cache copy is deleted on logout.
596
</p></div></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id427779"></a>Common Errors</h2></div></div></div><p>
596
</p></div></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id427765"></a>Common Errors</h2></div></div></div><p>
597
597
The following are some typical errors, problems, and questions that have been asked on the Samba mailing lists.
598
</p><div class="sect2" title="Configuring Roaming Profiles for a Few Users or Groups"><div class="titlepage"><div><div><h3 class="title"><a name="id427789"></a>Configuring Roaming Profiles for a Few Users or Groups</h3></div></div></div><p>
598
</p><div class="sect2" title="Configuring Roaming Profiles for a Few Users or Groups"><div class="titlepage"><div><div><h3 class="title"><a name="id427775"></a>Configuring Roaming Profiles for a Few Users or Groups</h3></div></div></div><p>
599
599
With Samba-2.2.x, the choice you have is to enable or disable roaming profiles support. It is a
600
600
global-only setting. The default is to have roaming profiles, and the default path will locate them in
601
601
the user's home directory.
625
625
changed as well as good discipline make 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
626
626
removes the need for a PST file. </p><p>Local profiles mean: </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>If each machine is used by many users, then much local disk storage is needed
627
627
for local profiles.</p></li><li class="listitem"><p>Every workstation the user logs into has
628
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 class="itemizedlist" type="disc"><li class="listitem"><p>The network administrator can control the desktop environment of all users.</p></li><li class="listitem"><p>Use of mandatory profiles drastically reduces network management overheads.</p></li><li class="listitem"><p>In the long run, users will experience fewer problems.</p></li></ul></div></div><div class="sect2" title="Changing the Default Profile"><div class="titlepage"><div><div><h3 class="title"><a name="id427992"></a>Changing the Default Profile</h3></div></div></div><p><span class="quote">“<span class="quote">When the client logs onto the domain controller, it searches
628
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 class="itemizedlist" type="disc"><li class="listitem"><p>The network administrator can control the desktop environment of all users.</p></li><li class="listitem"><p>Use of mandatory profiles drastically reduces network management overheads.</p></li><li class="listitem"><p>In the long run, users will experience fewer problems.</p></li></ul></div></div><div class="sect2" title="Changing the Default Profile"><div class="titlepage"><div><div><h3 class="title"><a name="id427978"></a>Changing the Default Profile</h3></div></div></div><p><span class="quote">“<span class="quote">When the client logs onto the domain controller, it searches
629
629
for a profile to download. Where do I put this default profile?</span>”</span></p><p>
630
<a class="indexterm" name="id428005"></a>
630
<a class="indexterm" name="id427991"></a>
631
631
First, the Samba server needs to be configured as a domain controller. This can be done by
632
setting in <code class="filename">smb.conf</code>: </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id428025"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id428036"></a><em class="parameter"><code>os level = 32 (or more)</code></em></td></tr><tr><td><a class="indexterm" name="id428048"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr></table><p> There must be a <em class="parameter"><code>[netlogon]</code></em> share that is world readable. It is
632
setting in <code class="filename">smb.conf</code>: </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id428011"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id428022"></a><em class="parameter"><code>os level = 32 (or more)</code></em></td></tr><tr><td><a class="indexterm" name="id428034"></a><em class="parameter"><code>domain logons = Yes</code></em></td></tr></table><p> There must be a <em class="parameter"><code>[netlogon]</code></em> share that is world readable. It is
633
633
a good idea to add a logon script to preset printer and drive connections. There is also a facility
634
634
for automatically synchronizing the workstation time clock with that of the logon server (another good
635
635
thing to do). </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> To invoke autodeletion of roaming profiles from the local workstation cache (disk storage), use
636
636
the <span class="application">Group Policy Editor</span> to create a file called <code class="filename">NTConfig.POL</code>
637
637
with the appropriate entries. This file needs to be located in the <em class="parameter"><code>netlogon</code></em>
638
638
share root directory.</p></div><p> Windows clients need to be members of the domain. Workgroup machines do not use network logons,
639
so they do not interoperate with domain profiles. </p><p> For roaming profiles, add to <code class="filename">smb.conf</code>: </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id428114"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td># Default logon drive is Z:</td></tr><tr><td><a class="indexterm" name="id428129"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td># This requires a PROFILES share that is world writable.</td></tr></table></div><div class="sect2" title="Debugging Roaming Profiles and NT4-style Domain Policies"><div class="titlepage"><div><div><h3 class="title"><a name="id428146"></a>Debugging Roaming Profiles and NT4-style Domain Policies</h3></div></div></div><p>
639
so they do not interoperate with domain profiles. </p><p> For roaming profiles, add to <code class="filename">smb.conf</code>: </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id428100"></a><em class="parameter"><code>logon path = \\%N\profiles\%U</code></em></td></tr><tr><td># Default logon drive is Z:</td></tr><tr><td><a class="indexterm" name="id428115"></a><em class="parameter"><code>logon drive = H:</code></em></td></tr><tr><td># This requires a PROFILES share that is world writable.</td></tr></table></div><div class="sect2" title="Debugging Roaming Profiles and NT4-style Domain Policies"><div class="titlepage"><div><div><h3 class="title"><a name="id428131"></a>Debugging Roaming Profiles and NT4-style Domain Policies</h3></div></div></div><p>
640
640
Roaming profiles and domain policies are implemented via <code class="literal">USERENV.DLL</code>.
641
641
Microsoft Knowledge Base articles <a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;221833" target="_top">221833</a> and
642
642
<a class="ulink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;154120" target="_top">154120</a>
643
643
describe how to instruct that DLL to debug the login process.
644
</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id426004" href="#id426004" class="para">7</a>] </sup>http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en</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�26.�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�28.�PAM-Based Distributed Authentication</td></tr></table></div></body></html>
644
</p></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id425987" href="#id425987" class="para">7</a>] </sup>http://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en</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�26.�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�28.�PAM-Based Distributed Authentication</td></tr></table></div></body></html>
added
removed
docs/htmldocs/Samba3-HOWTO/ProfileMgmt.html
