Hello list, I sent this about two weeks ago, but I didn't get an
answer... so I'm pushing my luck. :-)
QUESTION#1: What EXACLTLY causes the HOMEDRIVE, HOMEPATH, and
HOMESHARE variables? Something passed from Samab to the client, or
some thing the client does?
QUESTION#2: How/what/where/why is there a difference in the results
of click on "Command Prompt"?
My Setup...
I'm running SuSE 9.0 Pro (2.4.21-192-default) and samba-2.2.8a-107.
I have a XP laptop client.
When I first setup my Samba PDC, I had this smb.conf:
-----------------------------------------
[global]
workgroup = NO-CATS
netbios name = MUTT
server string = Samba PDC running %v
encrypt passwords = Yes
update encrypted = Yes
passwd program = /usr/bin/passwd %u
unix password sync = Yes
log file = /var/log/samba/log.%m
time server = Yes
socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY
logon script = logon.bat
logon path = \\%L\%U\.msprofile
logon drive = H:
logon home = \\%L\%U\.win_profile\%m
domain logons = Yes
os level = 255
preferred master = Yes
domain master = Yes
wins support = Yes
hosts allow = 127.0.0.1 192.168.1.0/255.255.255.0
[netlogon]
path = /home/samba/netlogon
browseable = No
[profiles]
path = /home/samba/nt_profiles
read only = No
create mask = 0600
directory mask = 0700
browseable = No
[homes]
comment = %U's HOME directory
valid users = %S
read only = No
browseable = No
-----------------------------------------
Later, I changed 'logon path' to \\%L\profiles\%U\%m
When 'logon path' is \\%L\%U\.msprofile and I click on "Command
Prompt", I get a command window that says: H:\
When 'logon path' is \\%L\profiles\%U\%m" and I I click on
"Command
Prompt", I get a command window that says: C:\Documents and
Settings\flichlock
I have compared the XP client "set" variables, and I see just three
differences:
< HOMEDRIVE=H:
< HOMEPATH=\
< HOMESHARE=\\mutt\flinchlock
---> HOMEDRIVE=C:
> HOMEPATH=\Documents and Settings\flinchlock