summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/logon/logonpath.xml
blob: ab87c77bb9b99aa7136c07c9c8beac3f7623143c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
<samba:parameter name="logon path"
                 context="G"
				 type="string"
                 advanced="1" developer="1"
                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
	<para>This parameter specifies the home directory 
	where roaming profiles (NTuser.dat etc files for Windows NT) are 
	stored.  Contrary to previous versions of these manual pages, it has 
	nothing to do with Win 9X roaming profiles.  To find out how to 
	handle roaming profiles for Win 9X system, see the <link linkend="LOGONHOME">
	<parameter moreinfo="none">logon home</parameter></link> parameter.</para>

	<para>This option takes the standard substitutions, allowing you 
	to have separate logon scripts for each user or machine.  It also 
	specifies the directory from which the &quot;Application Data&quot;, 
	(<filename moreinfo="none">desktop</filename>, <filename moreinfo="none">start menu</filename>,
	<filename moreinfo="none">network neighborhood</filename>, <filename moreinfo="none">programs</filename> 
	and other folders, and their contents, are loaded and displayed on 
	your Windows NT client.</para>

	<para>The share and the path must be readable by the user for 
	the preferences and directories to be loaded onto the Windows NT
	client. The share must be writeable when the user logs in for the first
	time, in order that the Windows NT client can create the NTuser.dat
	and other directories.</para>

	<para>Thereafter, the directories and any of the contents can, 
	if required, be made read-only.  It is not advisable that the 
	NTuser.dat file be made read-only - rename it to NTuser.man to 
	achieve the desired effect (a <emphasis>MAN</emphasis>datory 
	profile). </para>

	<para>Windows clients can sometimes maintain a connection to 
	the [homes] share, even though there is no user logged in.  
	Therefore, it is vital that the logon path does not include a 
	reference to the homes share (i.e. setting this parameter to
	\%N\%U\profile_path will cause problems).</para>

	<para>This option takes the standard substitutions, allowing 
	you to have separate logon scripts for each user or machine.</para>

	<warning>
        <para>
        Do not quote the value. Setting this as <quote>\\%N\profile\%U</quote>
		will break profile handling. Where the tdbsam or ldapsam passdb backend
		is used, at the time the user account is created the value configured
		for this parameter is written to the passdb backend and that value will
		over-ride the parameter value present in the smb.conf file. Any error
		present in the passdb backend account record must be editted using the
		appropriate tool (pdbedit on the command-line, or any other locally
		provided system tool.
		</para>
	</warning>

	<para>Note that this option is only useful if Samba is set up 
	as a logon server.</para>

	<para>
	An example of use is:
<screen>
logon path = \\PROFILESERVER\PROFILE\%U
</screen>
	</para>
</description>
<value type="default">\\%N\%U\profile</value>
</samba:parameter>