What's with all of the user shares. If you want to share home directories, use the built in [homes] share as opposed to having individual shares.
# Slightly modified version
comment = Home Directory for %U
browseable = no
writeable = yes
valid users = %S
create mode = 0660
directory mode = 0770
As for the profile stuff, how do you go about setting it up. I can't remember at the top of my head and I just blew away my 2k server. I blew it up to play with email. You will need to open up "active directory users and computer" and set up the appropriate values for the profile path. Do you have something like \\<Samba_Server_Name>\%Username%? I just noticed that you didn't explicitly name your samba server. It is a good idea to put the value for netbios name in there.
What is the value you have set it Active Directory for each user.
I have a question of my own and it relates to samba and profiles. Sorry if I am monopolizing this thread, but it is slightly related so here goes:
My samba server is the DC for a domain and I am doing profiles. It works just fine but there are a couple of issues.
First of all, the relevant part of my smb.conf file looks like:
logon path = \\Madison\Profile\%m
comment = Profile Directory
path = %H/NT-Profile
read only = No
create mask = 0660
security mask = 0660
directory mask = 2770
directory security mask = 2770
browseable = No
volume = "Profile Directory"
I have it set up so that the Profile share on the server points to a subfolder of the user's home directory as opposed to creating a 2nd directory structure for profiles. The problem is that the NT-Profile folder is not always there so I tried using the preexec option to create the folder. I want to set up a script to check whether the folder already exists. The script's name is create-profile and the username should be passed as a parameter so the preexec for the profile share will look like:
preexec = /etc/samba/scripts/create-profile %u
The script is a plain old bash script, or at least it was. I deleted the meat of the script that was supposed to do the file checking. Anyway the script now looks like
At an earlier stage it created the directory but something didn't go right. If I logged in, it created a folder called "~sid" in the /etc/samba/scripts directory. The only way I got it to work was by slightly modifying the script and sending it the %H macro (The user's home directory.)
To make a long story short, is there a way to expand ~sid in a bash script or do I have to send the script the %H?
Shouldn't the above result in /home/sid displayed to the screen?